graphify-mcp (yasinyaman/graphify-mcp) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 27 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
71/100
1 month ago

graphify-mcp

A Python MCP server that exposes the Graphify knowledge graph as MCP tools, prompts, and resources, enabling AI assistants to explore codebases through a token-budgeted, structural graph during development.

→ yasinyaman/graphify-mcp· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code 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

yasinyaman

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
✅
27 tools verified — handlers match their declared behaviour
22 read-only tools verified — handlers contain no write/delete/exec
✅
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: GRAPHIFY_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configGRAPHIFY_BINgraphify CLI path
configGRAPHIFY_TIMEOUTFor a shared/network deployment, also consider lowering (default
configGRAPHIFY_RESTRICT_PATHSAny HTTP transport force-enables path containment ()
configGRAPHIFY_TRANSPORTstreamable-http GRAPHIFY_HOST=127.0.0.1 GRAPHIFY_PORT=8000 \
configGRAPHIFY_HOSTGRAPHIFY_TRANSPORT=streamable-http =127.0.0.1 GRAPHIFY_PORT=8000 \
configGRAPHIFY_PORTGRAPHIFY_TRANSPORT=streamable-http GRAPHIFY_HOST=127.0.0.1 =8000 \
🔐 secretGRAPHIFY_API_KEYevery request must then send Authorization: Bearer <key>
configGRAPHIFY_TOOLSETlean to expose only the core exploration tools.
configGRAPHIFY_SEMANTIC_BACKEND
configGRAPHIFY_WATCH0 1 → watch the project for structural source changes and re-sync the graph automatically (needs the [watch] extra; cosmetic edits are ignored)
configGRAPHIFY_WATCH_DEBOUNCE2.0 Seconds to coalesce a burst of file events before re-graphing (watch mode)
configGRAPHIFY_PROJECT_DIR/path/to/repo graphify-mcp-server
configGRAPHIFY_OUT_DIRgraphify-out Output folder name
configGRAPHIFY_TOKENIZER_(heuristic)_ tiktoken → exact token counts (needs the [tiktoken] extra); else chars/3.5 estimate
// quality suggestions

All four hints declared on every tool

27/27 tools missing one or more hints — graphify_build (missing: readOnlyHint, idempotentHint, openWorldHint); graphify_query (missing: destructiveHint, idempotentHint, openWorldHint); graphify_path (missing: destructiveHint, idempotentHint, openWorldHint), +24 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.

Tool handlers catch errors

Only 5/27 tool handlers wrap calls in try/catch (19%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 3 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 Score](https://m8ven.ai/badge/mcp/yasinyaman/graphify-mcp)](https://m8ven.ai/mcp/yasinyaman/graphify-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 948c4a995fde7b88e6140d3c4255ef0d3e4655a5
code hash: e9fdbc2572a2162f1f646686c3fcab00ab7fe5d91f97fda34b53809ccc67b40b
verified: 8/7/2026, 2:05:25 AM
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