mcp-registry/com.papacasper/mcp-toolbelt · v1.0.0
As of 2026-10-27 16:08 UTC, the Papacasper Toolbelt MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 6 minutes.
29 pay-per-call DNS, SEO, SSL, security, and dev tools for AI agents. x402, no API key.
Point your MCP client at this streamable-http endpoint: https://papacasper.com/mcp
29 of 29 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
In the last 30 days: 6 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.papacasper%2Fmcp-toolbelt/fixes
{
"name": "ai_readiness_audit",
"description": "Score how ready a website is for AI agents and LLM-driven discovery, 0-100 with a letter grade: robots.txt presence, explicit AI-crawler policy (GPTBot, ClaudeBot, CCBot, PerplexityBot, and 8 more), llms.txt presence and structure, structured data (JSON-LD) and Open Graph basics, agent/payment discovery files (/.well-known/x402, /openapi.json), sitemap presence, and title/meta basics. The bundle to run before/after making a site agent-friendly — for raw robots/sitemap contents only, use check_ro",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Any URL on the site to audit (origin is derived from it)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "broken_link_check",
"description": "Find broken links two ways. Default (crawl mode): crawl a site starting from a URL (same-origin pages only, bounded by maxPages) and check every linked URL for broken status codes, returning each broken link with the page(s) it was found on. Sitemap mode (viaSitemap: true): parse the site's sitemap.xml (following one level of sitemap-index nesting) and check the status of every URL listed in it instead. Note: some external sites (e.g. social platforms) block automated HEAD/GET requests and may s",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Starting URL to crawl — or, in sitemap mode, the sitemap.xml URL or any page URL on the site"
},
"maxPages": {
"type": "number",
"description": "Max same-origin pages to crawl in crawl mode (default 20, capped at 50)"
},
"viaSitemap": {
"type": "boolean",
"description": "Check the URLs listed in the site's sitemap.xml instead of crawling pages (default false)"
},
"checkExternal": {
"type": "boolean",
"description": "Crawl mode only: also check links pointing off-site (default true; crawling never follows off-site links)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_open_ports",
"description": "TCP-connect scan a host for open ports, plus network intel on the host's resolved IPs (ASN, network owner, BGP prefix, country — via Team Cymru). Defaults to a list of ~20 common service ports (SSH, HTTP/S, mail, DBs, etc.) if none are given. For checking your own infrastructure's exposure — capped at 100 ports per call.",
"inputSchema": {
"type": "object",
"required": [
"host"
],
"properties": {
"host": {
"type": "string",
"description": "Hostname or IP to scan (no scheme)"
},
"ports": {
"type": "array",
"items": {
"type": "number"
},
"description": "Specific ports to check. Defaults to a common-ports list. Max 100 ports per call."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.papacasper/mcp-toolbelt"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.papacasper/mcp-toolbelt"}) over MCP.
broken_link_check ~322 tokensstructured_data_extract ~315 tokenssmtp_server_check ~220 tokenspackage_vulnerability_check ~206 tokensexposed_files_check ~198 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.papacasper%2Fmcp-toolbelt?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.papacasper%2Fmcp-toolbelt?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.papacasper%2Fmcp-toolbelt.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.papacasper%2Fmcp-toolbelt.svg :target: https://glimind.com/server/mcp-registry%2Fcom.papacasper%2Fmcp-toolbelt?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1b21208a06242681…, first seen 2026-10-21, included at leaf 40021 of 80,231. Version history · verify what your client received.
Compare: most reliable other servers · most reliable web servers · most reliable security servers · most reliable data servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 16:08 UTC, the Papacasper Toolbelt MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 6 minutes.
Papacasper Toolbelt MCP server advertises 29 tools, including ai_readiness_audit, broken_link_check, check_open_ports, check_robots_sitemap, dns_propagation_check.
Point your MCP client at this streamable-http endpoint: https://papacasper.com/mcp
Glimind scanned all 29 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.