Synapsor Runner (Synapsor/Synapsor-Runner) is an MCP server listed on the M8ven Trust Index. It scores 18 out of 100, grade F. It declares 10 tools. No publisher has claimed this listing.

F
Warning
18/100

Synapsor Runner

Reviewed Postgres and MySQL business actions for MCP agents, without exposing raw execute_sql.

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

Synapsor

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 →

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
🚨
Hardcoded credentials detected
2 live-looking API keys in source: 2 OpenAI API key
🚨
Known vulnerabilities in dependencies: 1 critical, 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 14 credentials: ANTHROPIC_API_KEY, OPENAI_API_KEY, SYNAPSOR_API_KEY, SYNAPSOR_CLOUD_ACCESS_TOKEN, SYNAPSOR_RUNNER_HTTP_TOKEN, SYNAPSOR_RUNNER_TOKEN, SYNAPSOR_SESSION_JWT_SECRET, SYNAPSOR_TEST_CONFIGURED_HTTP_TOKEN, SYNAPSOR_TEST_EVENT_WEBHOOK_TOKEN, SYNAPSOR_TEST_HANDLER_SIGNING_SECRET, SYNAPSOR_TEST_HANDLER_TOKEN, SYNAPSOR_TEST_MCP_AUDIT_TOKEN, SYNAPSOR_TEST_OVERRIDE_HTTP_TOKEN, SYNAPSOR_TEST_RUNNER_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes10 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

execute_sql

Execute arbitrary SQL against the application database.

run_query

Run any query and return database rows.

approve_refund

Approve and issue a customer refund immediately.

update_customer

Update a customer record directly.

delete_order

Delete an order from the database.

query_database

Query arbitrary tables and columns from the database.

billing.inspect_invoice

Inspect one invoice within trusted tenant scope and return reviewed evidence fields.

billing.propose_late_fee_waiver

Create a review-required proposal to waive one invoice late fee; source DB remains unchanged.

billing.update_invoice

Update an invoice directly.

billing.get_invoice

Get one invoice.

// known CVEs in dependencies1 critical1 high1 medium1 low

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

criticalvitest@3.2.0GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

highmysql2@3.11.0GHSA-3f6p-5ww8-9rcr

MySQL2: Auth Plugin Downgrade to mysql_clear_password Leaks Plaintext Credentials

mediumajv@8.17.1GHSA-2g4f-4pwh-qvx6

ajv has ReDoS when using `$data` option

lowmysql2@3.11.0GHSA-rgwj-5xj2-c3m3

MySQL2: Unbounded zlib inflate in compressed MySQL protocol handler allows decompression-bomb DoS

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.
🔐 secretANTHROPIC_API_KEY
configAPP_POSTGRES_READ_URL
configAPP_POSTGRES_WRITE_URL
configBILLING_HANDLER_URL
configDOCKER_HOST
configNO_COLOR
🔐 secretOPENAI_API_KEY
🔐 secretSYNAPSOR_API_KEY
🔐 secretSYNAPSOR_CLOUD_ACCESS_TOKEN
configSYNAPSOR_CLOUD_BASE_URL
configSYNAPSOR_CLOUD_WORKSPACE
configSYNAPSOR_CONTROL_PLANE_URL
configSYNAPSOR_DATABASE_URL
configSYNAPSOR_DRY_RUN
configSYNAPSOR_LOCAL_STORE
configSYNAPSOR_LOG_LEVEL
configSYNAPSOR_MCP_CONFIG
configSYNAPSOR_OPERATOR_ID
configSYNAPSOR_POLL_INTERVAL_MS
configSYNAPSOR_PRINCIPAL
configSYNAPSOR_PROJECT_ID
configSYNAPSOR_RUNNER_COMMAND_NAME
configSYNAPSOR_RUNNER_CONFIG
🔐 secretSYNAPSOR_RUNNER_HTTP_TOKEN
configSYNAPSOR_RUNNER_ID
🔐 secretSYNAPSOR_RUNNER_TOKEN
configSYNAPSOR_SESSION_JWKS_URL
🔐 secretSYNAPSOR_SESSION_JWT_SECRET
configSYNAPSOR_SOURCE_ID
configSYNAPSOR_STATE_DIR
configSYNAPSOR_TENANT_ID
configSYNAPSOR_TEST_CLOUD_BASE_URL
🔐 secretSYNAPSOR_TEST_CONFIGURED_HTTP_TOKEN
🔐 secretSYNAPSOR_TEST_EVENT_WEBHOOK_TOKEN
🔐 secretSYNAPSOR_TEST_HANDLER_SIGNING_SECRET
🔐 secretSYNAPSOR_TEST_HANDLER_TOKEN
configSYNAPSOR_TEST_HANDLER_URL
configSYNAPSOR_TEST_LEDGER_URL
🔐 secretSYNAPSOR_TEST_MCP_AUDIT_TOKEN
🔐 secretSYNAPSOR_TEST_OVERRIDE_HTTP_TOKEN
configSYNAPSOR_TEST_REQUIRED_READ_URL
🔐 secretSYNAPSOR_TEST_RUNNER_TOKEN
configSYNAPSOR_WORKSPACE_ID
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// quality suggestions

No hardcoded API keys

2 live-looking API keys in source: 2 OpenAI API key

Move secrets to environment variables (process.env.X) or your secret manager.

Tool test coverage

7/10 tools referenced in tests (70%)

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

No eval / new Function

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

Replace eval / Function with explicit parsing or safer alternatives.

Production dependencies are patched

0 critical, 1 high severity in production deps — mysql2@3.11.0 (high), mysql2@3.11.0 (low)

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

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

1/12 production deps stale: pdf-lib@2022-05-12 (4.3y)

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/synapsor/synapsor-runner?variant=verified)](https://m8ven.ai/mcp/synapsor/synapsor-runner)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: ce3b5fdc2501e390fcaf5a8df45f2d576a37c6df
code hash: 208c25363b054d636f8e2a210d4481c3d99a34a694fad60d0557b3f9ad861c4a
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