mcpbeat Sign in

Mcpcheck MCP Server

answering

Mcpcheck is answering right now. Last checked 3 min ago. It exposes 2 tools.

Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 21 days of history · worst day 91%
21 days agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
601 ms
Response time
average over 24h
open, no key
Access
streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add mcpcheck --transport http https://mcpcheck.netlify.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcpcheck": {
      "url": "https://mcpcheck.netlify.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcpcheck]
url = "https://mcpcheck.netlify.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcpcheck": {
      "url": "https://mcpcheck.netlify.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcpcheck": {
      "url": "https://mcpcheck.netlify.app/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

mcp
check_mcp_trust
Check if an MCP server is safe to install: returns a trust score (0-100, grade A-F). Accepts a registry name (io.github.x/y), a GitHub repo (owner/repo), or a remote MCP URL. For remote servers it live-connects and analyzes the actual exposed tools for tool-poisoning + capabilities, and checks the backing repo (maintenance, license, security policy, auth). Call BEFORE installing or recommending any MCP server.
scan
scan_mcp_server
Scan and inspect an MCP server for security issues before connecting it: live tool-poisoning analysis, exposed-tool inventory + capabilities, TLS, and repo trust signals. Same engine as check_mcp_trust. Accepts a registry name, GitHub repo, or remote MCP URL.

Endpoints

URLTransportStateLatencyChecked
https://mcpcheck.netlify.app/mcp streamable-http answering 401 ms 3 min ago

Alternatives to Mcpcheck

same job, measured the same way
Mcpshield
by mcpshield-dev

Security scanner for MCP servers - detects tool poisoning and injection

42 installs/wk local only
AgentSecurityLens MCP Security Trust Check
by professor2k8

MCP security trust-check for agents before installing MCPs, Skills or tools.

74 installs/wk local only
Mcpgrade
by mcpgrade

Security grades (A-F) for MCP servers. Check one before you install or trust it. mcpgrade.dev

44 installs/wk local only
Mund — MCP Security Scanner
by tyox-all

Scan for prompt injection, secrets, PII, and vet MCP servers before installation

48 installs/wk local only
Veragent
by lixiaowww

Check the trust/security score of MCP servers, agents, skills & CLIs before you install them.

61 installs/wk local only
AIShield Security Scanner
by lm203688

Scans MCP servers for tool poisoning, prompt injection and supply chain risks.

46 installs/wk 9 tools local only
C
MCP Safeguard
by cognivators

MCP server security scanner: detects prompt injection, credential leaks, SSRF, tool poisoning.

125 installs/wk local only
Wass MCP
by tb0hdan

MCP server for web application security scanning

local only

Mcpcheck — questions

Answers built from our own checks of this server.

What can Mcpcheck do?
It exposes 2 tools, read directly from the server on our last check. Among them: check_mcp_trust, scan_mcp_server. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Mcpcheck working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 601 ms. The bar chart above shows every period we have measured.
Is Mcpcheck still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Mcpcheck?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Mcpcheck need an API key?
No. Mcpcheck completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Mcpcheck?
It answers our handshake in 601 ms on average, which is faster than 21% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.