Cited checks for one MCP tool or a tools list, plus a called-or-ignored tally. Connect the official Toolcard MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http toolcard https://agentghostedme.com/mcpRun in your terminal, then restart Claude Code.
Toolcard · https://agentghostedme.com/mcp
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “check_tool”: Check one MCP tool name, description, and input schema against Toolcard cited rules. Returns findings. A finding with an answer page include.”
“Use “check_server”: Check every tool in a tools/list result or a server card. Returns per-tool findings plus duplicate-name, overlapping-descriptions, and too-m.”
“Use “report_outcome”: Record whether an agent called or ignored a tool. Stores the name, a SHA-256 of the description, and the result. Does not store the raw desc.”
“Use “outcome_summary”: Return the anonymous tally of called versus ignored reports on this server. Not a representative sample.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Toolcard holds up.
gate scanned 4 tools on Oct 21, 2026 for prompt injection and risky tool definitions — nothing to flag.
Operated by Toolcard (agentghostedme.com) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If Toolcard adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose Toolcard in the gate directory. No sign-in needed.
Toolcard's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
check_tool — Check one MCP tool name, description, and input schema against Toolcard cited rules. Returns findings. A finding with an answer page include
check_server — Check every tool in a tools/list result or a server card. Returns per-tool findings plus duplicate-name, overlapping-descriptions, and too-m
report_outcome — Record whether an agent called or ignored a tool. Stores the name, a SHA-256 of the description, and the result. Does not store the raw desc
outcome_summary — Return the anonymous tally of called versus ignored reports on this server. Not a representative sample.
https://agentghostedme.com/mcpYes — Toolcard operates its own remote MCP server at agentghostedme.com. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick Toolcard in the directory. No account or sign-in is needed. From then on, Toolcard's tools are available in every client you've connected to gate.
No. Toolcard runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect Toolcard in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up Toolcard in: Claude · Claude Code · ChatGPT · Cursor · VS Code