Scan an MCP server
Paste the URL of a remote MCP server. We connect the way an agent would, read its tools and instructions, and look for text written to steer the agent. We never call a tool.
The Streamable HTTP endpoint, often ending in /mcp. Don't paste a URL that contains an API key or token: the link to the report includes the URL.
MCP 14 Oct 2026, 12:36 UTC
server.smithery.ai/
We couldn't connect: initialize returned HTTP 404.
Failed: Couldn't connect: initialize returned HTTP 404.
Passed: Served over HTTPS.
Note: If this is an older HTTP+SSE endpoint, the scanner can't read it.
Show your score
Put the badge in your README or docs. It links to the listing and updates as the score changes.
Markdown, for a README:
[](https://toolvet.app/s/saidsef-mcp-github-pr-issue-analyser)HTML, for a website:
<a href="https://toolvet.app/s/saidsef-mcp-github-pr-issue-analyser"><img src="https://toolvet.app/badge/saidsef-mcp-github-pr-issue-analyser.svg" alt="ToolVet trust score" height="20"></a>What this scan covers
One connection, the way an agent sees the server: its tool definitions and instructions. It doesn't call tools or send credentials, and it uses fixed rules, so no findings is not a guarantee. How the grade works. If a finding is wrong, tell us with the link to this scan at [email protected].