MCP Observatory

Independent safety audit of the MCP server ecosystem · by PulseFeed

Thousands of MCP servers ship with almost no vetting — and a bad one can run arbitrary code on your machine or exfiltrate data. Before you connect your AI agent to an MCP server, check it. We audit maintenance, install-script risk, provenance, abandonment and liveness.

5096servers audited
4403safe
267caution
421avoid

Verdicts

safe
4403
caution
267
avoid
421
unknown
5

npm servers get deep signals; remote servers get liveness + HTTPS only (can't fully verify a black-box remote).

Top safety flags

downloads_unknown
2099
no_repo
557
install_script
410
unpopular
164
abandoned
155
no_license
79
heavy_deps
33
unreachable
11

install_script = arbitrary code on npm i; abandoned = stale; unreachable = dead remote.

Top trusted MCP servers

ServerTypenpm dl/wkTrust
@modelcontextprotocol/sdknpm64,994,424100
ainpm31,177,103100
@ai-sdk/mcpnpm5,178,734100
@storybook/mcpnpm2,324,360100
@storybook/addon-mcpnpm2,528,261100
mcporternpm450,946100
@assistant-ui/reactnpm2,034,635100
mcp-handlernpm1,387,856100
@copilotkit/aimocknpm486,080100
fallownpm1,422,346100
mcp-remotenpm663,737100
@langchain/mcp-adaptersnpm287,805100
add-mcpnpm201,186100
evenpm1,326,613100
@modelcontextprotocol/servernpm11,702,082100
Check any MCP server: GET /mcp/verify?package=<npm-name> — free. Returns a safety verdict, score and flags (install scripts, abandonment, provenance, license, repo).
📊 Read the State of MCP Security report — how much of the ecosystem runs arbitrary code on install, updated daily. Building on MCP and want an API + CI check? Get early access →

Methodology: PulseFeed discovers servers from the official MCP registry, audits each via npm metadata (install scripts, provenance, license, downloads, freshness) and liveness for remotes. Same independent-audit approach as our x402 trust oracle. Machine-readable: /mcp.json. Updated daily.