mcp-graphql-enhancedSAFE
A schema-first GraphQL MCP server that avoids the 1MB introspection limit via typeNames/typeDepth scoping — built for federated topologies.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://glama.ai/mcp/servers/@letoribo/mcp-graphql-enhanced) [](https://glama.ai/mcp/servers/letoribo/mcp-graphql-enhanced)[](https://smithery.ai/servers/letoribo/mcp-graphql-enhanced)[](https://www.npmjs.com/package/@letoribo/mcp-graphql-enhanced)[](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.letoribo%2Fmcp-graphql-enhanced/versions/4.15.3)[](https://trust.redthreadsec.com/v/mcp/io.github.letoribo/mcp-graphql-enhanced)
An enhanced MCP (Model Context Protocol) server for GraphQL that fixes real-world interoperability issues between LLMs and GraphQL APIs.
Drop-in replacement for mcp-graphql — with dynamic headers, robust variables parsing, and zero breaking changes.🎯 What is mcp-graphql-enhanced?
mcp-graphql-enhanced is a high-performance, federated GraphQL gateway designed to act as a workhorse for LLM agents. It bridges the gap between massive, complex GraphQL ecosystems and the context-limited environment of AI assistants. Unlike standard "all-or-nothing" introspection tools that crash under the weight of large schemas (like GitHub's or enterprise-grade Neo4j graphs), this server provides surgical control over how your agent perceives and interacts with your data.
💡 Why do you need it?
If you have ever seen theTool result is too largewhile trying to introspect your AP
f13141780a5dOBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add mcp-graphql-enhanced -- npx -y @letoribo/[email protected]
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- declared (5 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (4)
readFileSync(join(__dirname, "../../package.json"), "utf-8")
"ENDPOINT": "http://DESKTOP-NAME.local:2311/graphql,http://127.0.0.1:4000/graphql"
@modelcontextprotocol/sdk, graphql, @graphql-tools/schema, @types/node, prettier, ts-node, tsx
Gates applied: no_behavioural_pass.
f13141780a5dfull audit observations/trust-audit/mcp-server/letoribo__mcp-graphql-enhanced.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | f13141780a5d | SAFE | B | 89 | first audit |
Questions
What is the @letoribo/mcp-graphql-enhanced MCP server?
A schema-first GraphQL MCP server that avoids the 1MB introspection limit via typeNames/typeDepth scoping — built for federated topologies.
Is @letoribo/mcp-graphql-enhanced safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does @letoribo/mcp-graphql-enhanced need?
No credential environment variables were found in its source, so it appears to need none.
How does @letoribo/mcp-graphql-enhanced run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @letoribo/mcp-graphql-enhanced at 4.15.4.
How current is this page?
The grade is for one exact copy of the source (f13141780a5d), read on 2026-10-12. The repository is watched and re-audited when it changes.