openstategraph (zulfeekar/openstategraph) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 44 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
1 day ago

openstategraph

OpenStateGraph — a visual editor for LangGraph

→ zulfeekar/openstategraph· listed on github_code

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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

zulfeekar

Source: github_code

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

GitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
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: OPENSTATEGRAPH_SMTP_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 low

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

lowvitest@4.1.10GHSA-82fw-gwwq-j7x9

Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock

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.
configDEMO_DIR
configDEMO_PORT
configOSG_E2E_BASE_URL
configOPENSTATEGRAPH_MCP_TRANSPORT
configOPENSTATEGRAPH_MCP_ALLOW_RUNS0, because a run costs money), and it will not
configOPENSTATEGRAPH_LOG_LEVELbackend log verbosity — DEBUG/INFO/WARNING/ERROR (default INFO)
configOPENSTATEGRAPH_EDITOR_DIST
configOPENSTATEGRAPH_MERMAID_ASSET
configOPENSTATEGRAPH_WORKFLOWS_ROOT
configOPENSTATEGRAPH_MODEL
configGITHUB_EVENT_PATH
configOPENSTATEGRAPH_BRIDGE_COMMENT_FILE
configGITHUB_OUTPUT
configOPENSTATEGRAPH_SMTP_FROM
configOPENSTATEGRAPH_SMTP_HOST
configOPENSTATEGRAPH_SMTP_PORT
configOPENSTATEGRAPH_SMTP_USER
🔐 secretOPENSTATEGRAPH_SMTP_PASSWORD
configOPENSTATEGRAPH_SMTP_STARTTLS
configXDG_STATE_HOME
// 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

45/45 tools missing one or more hints — example (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_node_vocabulary (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_engineering_rules (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +42 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 test coverage

22/45 tools referenced in tests (49%)

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

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/zulfeekar/openstategraph)](https://m8ven.ai/mcp/zulfeekar/openstategraph)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6a8cea521111f025df287e6d4f1e65fa66c1cde3
code hash: 62f0c83042fe350b47bd16e36150c04c5f924018d4e7ff8966fc9a435f8ca2e9
verified: 9/9/2026, 4:50:39 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