Free · no account · the package name is all we need

Before you give that MCP your token.

You are about to connect an agent to GitHub, a database, a deployment tool. The server will want a credential. Bring the MCP you want to use, not your credentials: this page says what it will ask for, where it sends it, what it actually did when we ran it with a decoy, and what we could not test.

Try one: @supabase/mcp-server-supabase · @modelcontextprotocol/server-github · @notionhq/notion-mcp-server · pypi:mcp-server-fetch

Where the answers come from"It will ask for" and "where it talks to" are read from the code: every environment variable, flag and hard-coded host. "What the honeypot saw" is the run: the server launched with planted decoy credentials and a recording proxy, and relaunched with a decoy in the variable it asked for. "What we could not test" is the gap between the two.

What never happens hereWe never ask for your credential and never need it. When a server needs one, the recommendation gives it to the guard on your machine, which injects it only into requests to the host you bind and refuses the rest. Nothing of yours is uploaded.

Then keep it that wayThe same check runs on every install your agent makes, automatically: npx -y vet-skills hook install. Updates that add a host, a credential or a tool are the next thing we are building; tell us if you want it first.