mcpbeat Sign in

Toolcard MCP Server

by agentghostedme Your server? Claim it
answering

Toolcard is answering right now. Last checked 8 min ago. It exposes 4 tools.

Cited checks for one MCP tool or a tools list, plus a called-or-ignored tally.

Uptime history 23 days of history
23 days agonow
100.0%
Uptime 24h
92 of 92 checks
4
Tools
read from the server
195 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Toolcard every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add toolcard --transport http https://agentghostedme.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://agentghostedme.com/mcp
~/.codex/config.toml
[mcp_servers.toolcard]
url = "https://agentghostedme.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "toolcard": {
      "url": "https://agentghostedme.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "toolcard": {
      "type": "http",
      "url": "https://agentghostedme.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

outcome
outcome_summary
Return the anonymous tally of called versus ignored reports on this server. Not a representative sample.
report
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 description.
server
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-many-tools. Those three omit resource. Does not store the tools.
tool
check_tool
Check one MCP tool name, description, and input schema against Toolcard cited rules. Returns findings. A finding with an answer page includes resource, a toolcard://answers URI to pass to resources/read. Does not store the tool.

Endpoints

URLTransportStateLatencyChecked
https://agentghostedme.com/mcp streamable-http answering 162 ms 8 min ago

Alternatives to Toolcard

same job, measured the same way
F
forai.tools — let your agent find the right tool
by forai

Lets your agent find the right MCP server, tool or service for a task, in one call. Ads labelled.

1 tools answering
Guardr
by guardr

Hosted MCP for website health monitoring. Tools: check_site, list_sites, get_site.

answering
Total Parks
by com-totalparks

Read-only MCP tools for Total Parks-listed Australian holiday parks, caravan parks, and campgrounds.

11 tools answering
D
Dr.Deploy
by dr-deploy

MCP tools for drdeploy: scan deployed sites, list, get findings, check status.

35 installs/wk local only
Callmcp
by callmcp

One MCP tool contract for telephony — any call provider, hosted, local, or BYOK.

118 installs/wk local only
mcp-armor
by studiomeyer

Security sidecar for MCP servers: 11 read-only control-plane tools for prompt-injection checks.

local only
AgentSecurityLens MCP Security Trust Check
by professor2k8

MCP security trust-check for agents before installing MCPs, Skills or tools.

106 installs/wk local only
J-Dawgs AI Tool Store & Human Hands — Catalog MCP
by joshuajdawg0350

Read-only catalog of the J-Dawgs AI Tool Store (100+ agent tools) plus Human Hands for AIs.

902 installs/wk local only

Toolcard — questions

Answers built from our own checks of this server.

What can Toolcard do?
It exposes 4 tools, read directly from the server on our last check. Among them: check_server, check_tool, outcome_summary, report_outcome. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Toolcard working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 195 ms. The bar chart above shows every period we have measured.
How do I connect Toolcard?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Toolcard need an API key?
No. Toolcard completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Toolcard?
It answers our handshake in 195 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.