Run402 MCP Server

run402-mcp npm v4.70.9 Source verified

Published by kychee-com — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for Run402 — AI-native Postgres databases with REST API, auth, storage, and row-level security. Pay with x402 USDC micropayments.

Trust grade
A
90/100
Last scanned get badge →
Trust
A · 90/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Critical
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 90/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 10 = 90. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−10 capability blast radius (critical) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 6

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: assets_get → list_secrets → delete_mailbox_webhook. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow assets_get → list_secrets → delete_mailbox_webhook

high Reads a sensitive credential path or dumps the environment (sdk/dist/node/files.js)MTC-SRC-006

In the server's implementation (`sdk/dist/node/files.js:16`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: env", ".envrc", ".npmrc", ".pnpmrc", ".yarnrc", ".netrc", ".pypirc", "id_dsa", "id_ecdsa

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server sdk/dist/node/files.js

high Reads a sensitive credential path or dumps the environment (sdk/dist/node/gitvault-snapshot.js)MTC-SRC-006

In the server's implementation (`sdk/dist/node/gitvault-snapshot.js:697`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: "*.keystore", "id_rsa*", "id_ed25519*", "id_ecdsa*", ".npmrc", ".netrc", ".pypirc", ".g

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server sdk/dist/node/gitvault-snapshot.js

high Shell/command execution in server code (sdk/dist/node/actions-node.js)MTC-SRC-002

In the server's implementation (`sdk/dist/node/actions-node.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execFile } from "node:child_process"; import { lstat, mkdir, mkdtemp, readFile, rename, rm, writeFile, } from "node:fs

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server sdk/dist/node/actions-node.js

high Shell/command execution in server code (sdk/dist/node/gitvault-restore.js)MTC-SRC-002

In the server's implementation (`sdk/dist/node/gitvault-restore.js:27`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execFile } from "node:child_process"; import { mkdtempSync, existsSync, readFileSync, appendFileSync, mkdirSync } from

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server sdk/dist/node/gitvault-restore.js

high Shell/command execution in server code (sdk/dist/node/gitvault-snapshot.js)MTC-SRC-002

In the server's implementation (`sdk/dist/node/gitvault-snapshot.js:47`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execFile } from "node:child_process"; import { existsSync, lstatSync, mkdirSync, mkdtempSync, readFileSync, readlinkSy

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server sdk/dist/node/gitvault-snapshot.js

Tools 200

Each tool and what it can reach — statically extracted from the published source.

  • assets_getingests untrusted input
  • browse_appsingests untrusted input
  • delete_mailbox_webhooknetwork egress
  • deploy_diagnose_urlingests untrusted input
  • get_function_runingests untrusted input
  • get_function_run_logsingests untrusted input
  • jobs_download_artifactingests untrusted input
  • list_secretsreads sensitive data
  • preview_project_transferingests untrusted input
  • redrive_mailbox_webhook_deliverynetwork egress
Show 190 more tools ↓
  • register_mailbox_webhooknetwork egress
  • rotate_webhook_secretnetwork egress
  • run_sqlreads sensitive data
  • send_emailnetwork egress
  • set_notification_preferencesnetwork egress
  • update_mailbox_webhooknetwork egress
  • accept_project_transferno sensitive capability
  • ack_room_messageno sensitive capability
  • admin_archive_projectno sensitive capability
  • admin_reactivate_projectno sensitive capability
  • admin_set_lease_perpetualno sensitive capability
  • ai_moderateno sensitive capability
  • ai_translateno sensitive capability
  • ai_usageno sensitive capability
  • allowance_createno sensitive capability
  • allowance_exportno sensitive capability
  • allowance_statusno sensitive capability
  • app_upno sensitive capability
  • apply_exposeno sensitive capability
  • assets_lsno sensitive capability
  • assets_putno sensitive capability
  • assets_rmno sensitive capability
  • assets_signno sensitive capability
  • auth_settingsno sensitive capability
  • billing_historyno sensitive capability
  • cancel_function_runno sensitive capability
  • cancel_project_transferno sensitive capability
  • check_balanceno sensitive capability
  • ci_create_bindingno sensitive capability
  • ci_get_bindingno sensitive capability
  • ci_list_bindingsno sensitive capability
  • ci_revoke_bindingno sensitive capability
  • claim_project_transferno sensitive capability
  • claim_room_resourceno sensitive capability
  • claim_subdomainno sensitive capability
  • contract_callno sensitive capability
  • contract_deployno sensitive capability
  • contract_readno sensitive capability
  • create_auth_userno sensitive capability
  • create_checkoutno sensitive capability
  • create_email_organizationno sensitive capability
  • create_function_runno sensitive capability
  • create_mailboxno sensitive capability
  • create_notification_ruleno sensitive capability
  • create_orgno sensitive capability
  • create_project_branchno sensitive capability
  • create_project_snapshotno sensitive capability
  • delete_functionno sensitive capability
  • delete_mailboxno sensitive capability
  • delete_notification_ruleno sensitive capability
  • delete_passkeyno sensitive capability
  • delete_projectno sensitive capability
  • delete_project_branchno sensitive capability
  • delete_project_snapshotno sensitive capability
  • delete_secretno sensitive capability
  • delete_signerno sensitive capability
  • delete_subdomainno sensitive capability
  • delete_versionno sensitive capability
  • demote_userno sensitive capability
  • deployno sensitive capability
  • deploy_eventsno sensitive capability
  • deploy_functionno sensitive capability
  • deploy_listno sensitive capability
  • deploy_rehearseno sensitive capability
  • deploy_release_activeno sensitive capability
  • deploy_release_diffno sensitive capability
  • deploy_release_getno sensitive capability
  • deploy_resumeno sensitive capability
  • deploy_siteno sensitive capability
  • deploy_site_dirno sensitive capability
  • deploy_verify_edgeno sensitive capability
  • diagnose_public_urlno sensitive capability
  • domains_activateno sensitive capability
  • domains_applyno sensitive capability
  • domains_checkno sensitive capability
  • domains_disconnectno sensitive capability
  • domains_ensureno sensitive capability
  • domains_getno sensitive capability
  • domains_listno sensitive capability
  • domains_repairno sensitive capability
  • domains_test_receiveno sensitive capability
  • drain_signerno sensitive capability
  • errors_listno sensitive capability
  • export_project_archiveno sensitive capability
  • fork_appno sensitive capability
  • functions_rebuildno sensitive capability
  • generate_imageno sensitive capability
  • get_agent_contact_statusno sensitive capability
  • get_appno sensitive capability
  • get_buzz_routeno sensitive capability
  • get_contract_call_statusno sensitive capability
  • get_emailno sensitive capability
  • get_email_rawno sensitive capability
  • get_escalationno sensitive capability
  • get_exposeno sensitive capability
  • get_function_logsno sensitive capability
  • get_mailboxno sensitive capability
  • get_mailbox_webhookno sensitive capability
  • get_notification_preferencesno sensitive capability
  • get_operator_statusno sensitive capability
  • get_orgno sensitive capability
  • get_project_snapshotno sensitive capability
  • get_quoteno sensitive capability
  • get_schemano sensitive capability
  • get_signerno sensitive capability
  • get_usageno sensitive capability
  • import_project_archiveno sensitive capability
  • initno sensitive capability
  • initiate_project_transferno sensitive capability
  • inspect_project_archiveno sensitive capability
  • invite_auth_userno sensitive capability
  • invoke_functionno sensitive capability
  • jobs_cancelno sensitive capability
  • jobs_getno sensitive capability
  • jobs_logsno sensitive capability
  • jobs_purgeno sensitive capability
  • jobs_submitno sensitive capability
  • join_roomno sensitive capability
  • link_wallet_to_organizationno sensitive capability
  • list_buzz_route_deliveriesno sensitive capability
  • list_emailsno sensitive capability
  • list_function_runsno sensitive capability
  • list_functionsno sensitive capability
  • list_incoming_transfersno sensitive capability
  • list_mailbox_webhook_deliveriesno sensitive capability
  • list_mailbox_webhooksno sensitive capability
  • list_mailboxesno sensitive capability
  • list_notification_channelsno sensitive capability
  • list_notification_rulesno sensitive capability
  • list_notificationsno sensitive capability
  • list_outgoing_transfersno sensitive capability
  • list_passkeysno sensitive capability
  • list_project_branchesno sensitive capability
  • list_project_eventsno sensitive capability
  • list_project_snapshotsno sensitive capability
  • list_projectsno sensitive capability
  • list_signersno sensitive capability
  • list_subdomainsno sensitive capability
  • list_tenant_paymentsno sensitive capability
  • list_versionsno sensitive capability
  • passkey_login_optionsno sensitive capability
  • passkey_login_verifyno sensitive capability
  • passkey_register_optionsno sensitive capability
  • passkey_register_verifyno sensitive capability
  • pay_urlno sensitive capability
  • project_getno sensitive capability
  • project_key_cache_exportno sensitive capability
  • project_key_cache_statusno sensitive capability
  • project_useno sensitive capability
  • promote_userno sensitive capability
  • provision_postgres_projectno sensitive capability
  • provision_signerno sensitive capability
  • publish_appno sensitive capability
  • raise_escalationno sensitive capability
  • read_room_messagesno sensitive capability
  • redeem_voucherno sensitive capability
  • redrive_function_runno sensitive capability
  • release_room_claimno sensitive capability
  • rename_orgno sensitive capability
  • rename_projectno sensitive capability
  • renew_project_branchno sensitive capability
  • request_faucetno sensitive capability
  • request_magic_linkno sensitive capability
  • rest_queryno sensitive capability
  • restore_project_snapshotno sensitive capability
  • scaffold_rolesno sensitive capability
  • send_feedbackno sensitive capability
  • send_room_messageno sensitive capability
  • service_healthno sensitive capability
  • service_statusno sensitive capability
  • set_agent_contactno sensitive capability
  • set_auto_rechargeno sensitive capability
  • set_low_balance_alertno sensitive capability
  • set_mailbox_defaultsno sensitive capability
  • set_recovery_addressno sensitive capability
  • set_secretno sensitive capability
  • set_tierno sensitive capability
  • set_user_passwordno sensitive capability
  • start_operator_passkey_enrollmentno sensitive capability
  • statusno sensitive capability
  • test_notificationno sensitive capability
  • tier_statusno sensitive capability
  • update_functionno sensitive capability
  • update_mailboxno sensitive capability
  • update_versionno sensitive capability
  • validate_manifestno sensitive capability
  • verify_agent_contact_emailno sensitive capability
  • verify_magic_linkno sensitive capability
  • verify_project_archiveno sensitive capability
  • wait_for_cdn_freshnessno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 10

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v4.70.9 latest A 90/100 6 1.13.0 2026-09-07
v4.69.8 A 90/100 6 1.13.0 2026-09-05
v4.69.2 A 90/100 6 1.13.0 2026-09-04
v4.65.0 A 90/100 4 1.13.0 2026-09-01
v4.60.0 A 90/100 4 1.13.0 2026-08-31
Show 5 more versions ↓
v4.56.2 A 90/100 4 1.13.0 2026-08-30
v4.49.0 A 90/100 4 1.13.0 2026-08-29
v4.45.1 A 90/100 4 1.13.0 2026-08-28
v4.40.0 A 90/100 4 1.13.0 2026-08-27
v4.31.0 A 90/100 4 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 90/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/run402-mcp/badge.svg)](https://mcptrustchecker.com/registry/run402-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/run402-mcp"><img src="https://mcptrustchecker.com/registry/run402-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/run402-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan run402-mcp --online

Use the free API → How scoring works

More in AI & Agents