Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/apollographql/skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/apollographql/skills/graphos-tools)<a href="https://agentmods.dev/mcp/apollographql/skills/graphos-tools"><img src="https://agentmods.dev/badge/mcp/apollographql/skills/graphos-tools/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/apollographql/skills/graphos-tools"><img src="https://agentmods.dev/badge/mcp/apollographql/skills/graphos-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
graphos-tools scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"graphos-tools": {
"type": "http",
"url": "https://mcp.apollographql.com"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 6 lines scan A 3896593163ed
graphos-tools is an MCP server published in the GitHub repository apollographql/skills (120 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
apollo-mcp-server
MCP server "apollo-mcp-server" as configured in apollographql/apollo-mcp-server. Runs in Docker (ghcr.io/apollographql/apollo-mcp-server:canary-20260112T145439Z-114c866).
mcp-graphql-enhanced
GraphQL gateway for LLMs. Handles huge GitHub GraphQL & @neo4j/graphql schemas without crashing. Runs locally from the @letoribo/mcp-graphql-enhanced npm package. Needs 7 environment variables to run.
ariadne
Fast local MCP server for deterministic cross-service API-chain discovery across REST, GraphQL, Kafka, TypeScript, and FastAPI. Runs locally from the ariadne-mcp Python package.
mcp-graphql-bridge
Bridges any GraphQL API to Claude Code — auto-generates MCP tools via schema introspection. Runs locally from the mcp-graphql-bridge npm package. Needs 7 environment variables to run.
graphql-agent-toolkit
Turn any GraphQL API into AI-agent-ready tools — MCP servers, LangChain tools, and standalone SDKs. Runs locally from the graphql-agent-toolkit npm package.
universal-connector-mcp
A security-first, local-first MCP server that connects any API (OpenAPI/GraphQL/gRPC/SOAP) to AI agents through a single normalized operation model. Runs locally from the universal-connector-mcp Python package. Needs 5 environment variables to run.