meridian (meridianmcp/Meridian) is an MCP server listed on the M8ven Trust Index. It scores 0 out of 100, grade F. It declares 51 tools. No publisher has claimed this listing.

Warning

0/100

meridian

Item: meridian
Rating: 0
Author: M8ven

Persistent memory and task coordination for AI coding agents. Tracks sprint items, logs tasks, manages session handoffs, and surfaces HITL requests so you stay in control across single or parallel Claude Code, Codex, Cursor, and Windsurf sessions.

→ meridianmcp/Meridian · 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

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 push why connect →

Who stands behind it

meridianmcp

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.

⏳ This MCP is queued for scoring. Check back in a few minutes.

// key findings

🚨

Reads files from sensitive locations

Touches: ~/.claude/.credentials.json, ~/.claude/.credentials.json

🔐

You'll be asked for 16 credentials: ANTHROPIC_API_KEY, MERIDIAN_ENCRYPTION_KEY, RESEND_API_KEY, MICROSOFT_CLIENT_SECRET, MERIDIAN_ADMIN_PASSWORD, STRIPE_WEBHOOK_SECRET, STRIPE_API_KEY, GITHUB_MARKETPLACE_WEBHOOK_SECRET, SESSION_SECRET, MERIDIAN_SESSION_SECRET, MERIDIAN_STANDARD_KEY, SITE_PASSWORD, DEMO_PASSWORD, MERIDIAN_API_KEY, BEARER_TOKEN, MERIDIAN_PRO_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.

configMERIDIAN_HOST

configMERIDIAN_PORT

configMERIDIAN_VERSION

configMERIDIAN_GIT_SHA

configMERIDIAN_HOSTED

configMERIDIAN_AUTH_DB

configMERIDIAN_DB_URLState lives in data/meridian.db (SQLite) or a Postgres URL via .

configMERIDIAN_DEMO

🔐 secretANTHROPIC_API_KEY

🔐 secretMERIDIAN_ENCRYPTION_KEY

configMERIDIAN_HUMAN_ID

configMERIDIAN_INTERNAL_EMAILS

configMERIDIAN_ADMIN_EMAILS

configADMIN_EMAIL

configMERIDIAN_WORKER_CMD

configMERIDIAN_ADMIN_NTFY_URL

🔐 secretRESEND_API_KEY

configMERIDIAN_GOAL_MD

configMICROSOFT_CLIENT_ID

🔐 secretMICROSOFT_CLIENT_SECRET

🔐 secretMERIDIAN_ADMIN_PASSWORD

configMAX_CUSTOMERS_PER_PROJECT

configMAX_PROJECTS_STANDARD

configMAX_PROJECTS_PRO

configALERT_THRESHOLD_STANDARD

configALERT_THRESHOLD_PRO

configSTRIPE_PRICE_ID

configSTRIPE_PRO_PRICE_ID

configSTRIPE_OVERAGE_PRICE_ID

configMERIDIAN_BASE_URL

configMERIDIAN_DATA_DIR

configMERIDIAN_DB

configMERIDIAN_MD_ROOT

configSTRIPE_PAYMENT_LINK

🔐 secretSTRIPE_WEBHOOK_SECRET

🔐 secretSTRIPE_API_KEY

🔐 secretGITHUB_MARKETPLACE_WEBHOOK_SECRET

🔐 secretSESSION_SECRET

🔐 secretMERIDIAN_SESSION_SECRET

configMERIDIAN_KEEPALIVE_INTERVAL_S

configMERIDIAN_KEEPALIVE_TTL_S

configMERIDIAN_DEMO_DB_URL

🔐 secretMERIDIAN_STANDARD_KEY

configMERIDIAN_SKIP_DEMO

configMERIDIAN_AUTO_SUMMARY_INTERVAL

🔐 secretSITE_PASSWORD

configMERIDIAN_ENABLE_ERROR_TEST

🔐 secretDEMO_PASSWORD

configSTRIPE_PRO_PAYMENT_LINK

configMERIDIAN_IS_FAILOVER

configMERIDIAN_LAUNCH_OPEN

configMERIDIAN_SERVER_URL

configMERIDIAN_FROM_EMAIL

🔐 secretMERIDIAN_API_KEY

🔐 secretBEARER_TOKEN

configMERIDIAN_URL

configCAPTURE_BASE_URL

configMERIDIAN_BUILD_PROJECT

🔐 secretMERIDIAN_PRO_KEY

configMERIDIAN_PROJECT_ID

configNEON_API_KEY_PRO

configMERIDIAN_CLAUDE_CLI

configMERIDIAN_PROJECT_DB

// 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

51/51 tools missing one or more hints — create_project (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); register_session (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_goal (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +48 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

No access to sensitive paths

Reads sensitive paths: ~/.claude/.credentials.json, ~/.claude/.credentials.json

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

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 5 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/meridianmcp/meridian?variant=verified)](https://m8ven.ai/mcp/meridianmcp/meridian)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: 8132cd9fdefd3c6de24292d74848561bc315f6c0

code hash: df24e2473d1c5a5a1f0bc28dc34a72d07b89f479c9f41adeb07e705afb6fece0

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