wi-graphql-mcp-server (philip-hayden/wi-graphql-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 30 out of 100, grade F. It declares 26 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
F
Warning
30/100

wi-graphql-mcp-server

An MCP server implementing the Wildlife Insights GraphQL API, providing natural language tools for wildlife management and species identification.

→ philip-hayden/wi-graphql-mcp-server· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

philip-hayden

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Tool descriptions don’t match what handlers do
13 tools describe read intent but their handlers mutate — discoverObservations (line 470: wi.exec(DISCOVER_OBSERVATIONS_QUERY, variables, "DiscoverObservations", bearerToken)); getProjects (line 499: wi.exec(GET_PROJECTS_QUERY, variables, "GetProjects", bearerToken)); getDeployments (line 534: wi.exec(GET_DEPLOYMENTS_QUERY, variables, "GetDeployments", bearerToken))
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: WI_BEARER_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.20.2GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.20.2GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.20.2GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAPI_BASE_URL
configAPI_RETRIES
configAPI_TIMEOUT
configGRACEFUL_SHUTDOWN_TIMEOUT
configLOG_FORMAT
configLOG_LEVEL
🔐 secretWI_BEARER_TOKEN
configWI_GRAPHQL_ENDPOINT
configWI_TIMEOUT_MS
configWI_USER_AGENT
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

26/26 tools missing one or more hints — auth.setToken (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); auth.refreshToken (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); discoverObservations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +23 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Descriptions match behaviour

13 tools describe read intent but their handlers mutate — discoverObservations (line 470: wi.exec(DISCOVER_OBSERVATIONS_QUERY, variables, "DiscoverObservations", bearerToken)); getProjects (line 499: wi.exec(GET_PROJECTS_QUERY, variables, "GetProjects", bearerToken)); getDeployments (line 534: wi.exec(GET_DEPLOYMENTS_QUERY, variables, "GetDeployments", bearerToken))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool test coverage

Only 0/26 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.20.2 (high), @modelcontextprotocol/sdk@1.20.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Tool description accuracy

13 tools have description/behavior mismatches: discoverObservations: description implies read-only but handler writes/deletes/executes; getProjects: description implies read-only but handler writes/deletes/executes; getDeployments: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/philip-hayden/wi-graphql-mcp-server?variant=verified)](https://m8ven.ai/mcp/philip-hayden/wi-graphql-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 01c37ef5c0f174d016614644d8743b9031776c77
code hash: 52b0feb5e95f0c991cb39ae561acba76daf1a5e6533d77f8f3b05cb6f5d50201
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client