Graph-It-Live (magic5644/Graph-It-Live) is an MCP server listed on the M8ven Trust Index. It scores 38 out of 100, grade F. It declares 49 tools. No publisher has claimed this listing.

F
Warning
38/100

Graph-It-Live

Graph-It-Live VS Code Extension

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

magic5644

Source: github_repo_search

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 →

Install from

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 annotations don’t match behaviour
22 read-only tools perform write/delete/exec — graphitlive_analyze_dependencies (line 76: fs.appendFileSync(DEBUG_LOG_PATH, line)); graphitlive_crawl_dependency_graph (line 76: fs.appendFileSync(DEBUG_LOG_PATH, line)); graphitlive_find_referencing_files (line 76: fs.appendFileSync(DEBUG_LOG_PATH, line))
⚠️
Tool descriptions don’t match what handlers do
6 tools describe read intent but their handlers mutate — graphitlive_analyze_dependencies (line 76: fs.appendFileSync(DEBUG_LOG_PATH, line)); graphitlive_get_symbol_callers (line 76: fs.appendFileSync(DEBUG_LOG_PATH, line)); graphitlive_review_pr (line 76: fs.appendFileSync(DEBUG_LOG_PATH, line))
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 2 credentials: ANTHROPIC_API_KEY, OPENAI_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.
🔐 secretANTHROPIC_API_KEY
configCLI_VERSION
configEXCLUDE_NODE_MODULES
configEXTENSION_PATH
configGRAPH_IT_COPILOT_BIN
configGRAPH_IT_LLM_PROVIDER
configGRAPH_IT_NO_STATS
configMAX_DEPTH
🔐 secretOPENAI_API_KEY
configOPENAI_BASE_URL
configOPENAI_MODEL
configTSCONFIG_PATH
configWORKSPACE_ROOT
// quality suggestions

Tool annotations

27/49 tools have annotations

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

All four hints declared on every tool

22/49 tools missing one or more hints — graph-it-live_find_referencing_files (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); graph-it-live_analyze_dependencies (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); graph-it-live_crawl_dependency_graph (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +19 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 annotations match behaviour

22 read-only tools perform write/delete/exec — graphitlive_analyze_dependencies (line 76: fs.appendFileSync(DEBUG_LOG_PATH, line)); graphitlive_crawl_dependency_graph (line 76: fs.appendFileSync(DEBUG_LOG_PATH, line)); graphitlive_find_referencing_files (line 76: fs.appendFileSync(DEBUG_LOG_PATH, line))

Either remove the readOnlyHint:true annotation, or remove the write/delete call from the tool handler.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — graphitlive_set_workspace deletes at line 47 (fs.unlinkSync(DEBUG_LOG_BACKUP))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

6 tools describe read intent but their handlers mutate — graphitlive_analyze_dependencies (line 76: fs.appendFileSync(DEBUG_LOG_PATH, line)); graphitlive_get_symbol_callers (line 76: fs.appendFileSync(DEBUG_LOG_PATH, line)); graphitlive_review_pr (line 76: fs.appendFileSync(DEBUG_LOG_PATH, line))

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

Dependency freshness

2/19 production deps stale: cytoscape-fcose@2023-01-17 (3.7y), reactflow@2024-06-20 (2.2y)

Tool description accuracy

3 tools have description/behavior mismatches: graphitlive_analyze_dependencies: description implies read-only but handler writes/deletes/executes; graphitlive_review_pr: description implies read-only but handler writes/deletes/executes; graphitlive_graph_context: 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/magic5644/graph-it-live?variant=verified)](https://m8ven.ai/mcp/magic5644/graph-it-live)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: a9fbef75cb19d7caa73ed5fee24c82f9e17fdf31
code hash: 607b1b3aaed66227e9d094c55ab45b8cb99bdd9ea3825c44fd4e19f0669d2e18
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