Home / MCP registry index / io.github.joeyough/mcpcheck

io.github.joeyough/mcpcheck

io.github.joeyough/mcpcheck in the official MCP registry. Endpoint https://mcpcheck.netlify.app/mcp. Source: github.com/joeyough/mcpcheck.

The registry describes it as: Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http mcpcheck https://mcpcheck.netlify.app/mcp

{
  "mcpServers": {
    "mcpcheck": {
      "url": "https://mcpcheck.netlify.app/mcp"
    }
  }
}

code --add-mcp '{"name":"mcpcheck","type":"http","url":"https://mcpcheck.netlify.app/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

check_mcp_trust scan_mcp_server

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-joeyough-mcpcheck/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-joeyough-mcpcheck)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Security MCP servers