Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.
Connect Remote server
claude mcp add --transport http mcpcheck https://mcpcheck.netlify.app/mcp
{
"mcpServers": {
"mcpcheck": {
"url": "https://mcpcheck.netlify.app/mcp"
}
}
}
{
"servers": {
"mcpcheck": {
"type": "http",
"url": "https://mcpcheck.netlify.app/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcpcheck.netlify.app/mcp
Tools 2 found in our last check
check_mcp_trustCheck 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 + capabilit…
scan_mcp_serverScan 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.
Details
| Endpoint | https://mcpcheck.netlify.app/mcp (Streamable HTTP) |
| First published | 28 Aug 2026 |
| Last updated | 28 Aug 2026 |
| Registry name | io.github.joeyough/mcpcheck |
More security servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
