mcp-toolbelt
REMOTE · PAPACASPER.COM · SCANNED SEP 25
29 pay-per-call DNS, SEO, SSL, security, and dev tools for AI agents. x402, no API key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 29 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2680 tokens (~92/item across 29 items; 29 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cors_policy_check" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the mcp-toolbelt server?
mcp-toolbelt is a hosted endpoint at https://papacasper.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · papacasper.com
claude mcp add --transport http com-papacasper-mcp-toolbelt 'https://papacasper.com/mcp'
{
"mcpServers": {
"com-papacasper-mcp-toolbelt": {
"url": "https://papacasper.com/mcp"
}
}
} {
"servers": {
"com-papacasper-mcp-toolbelt": {
"type": "http",
"url": "https://papacasper.com/mcp"
}
}
} [mcp_servers.com-papacasper-mcp-toolbelt] url = "https://papacasper.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-papacasper-mcp-toolbelt": {
"type": "remote",
"url": "https://papacasper.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-papacasper-mcp-toolbelt --url 'https://papacasper.com/mcp' --transport streamable-http
mcp_servers:
com-papacasper-mcp-toolbelt:
url: "https://papacasper.com/mcp" {
"McpServers": {
"com-papacasper-mcp-toolbelt": {
"Transport": "http",
"Url": "https://papacasper.com/mcp"
}
}
} assistant mcp add com-papacasper-mcp-toolbelt -t streamable-http -u 'https://papacasper.com/mcp'
{
"mcpServers": {
"com-papacasper-mcp-toolbelt": {
"type": "http",
"url": "https://papacasper.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://papacasper.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=papacasper.com | CN=YE2,O=Let's Encrypt,C=US | 4 Aug 2026 | 2 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5988ece061c19478defb45107af5b1af852 |
| SANs: *.papacasper.com, papacasper.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of papacasper.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| papacasper.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://papacasper.com/mcp | Verified | 200 | |
| http (plaintext) | http://papacasper.com/mcp | HTTPS enforced | 301 | https://papacasper.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ai_crawler_policy_check ~118
Check a site's robots.txt for explicit directives targeting known AI crawlers (GPTBot, ClaudeBot, CCBot, PerplexityBot, Google-Extended, Bytespider, Amazonbot, and others used for LLM training or AI search/answer products), and check for an llms.txt file. Useful for publishers deciding whether their content policy toward AI crawlers matches their intent, or for auditing a competitor's stance.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Any URL on the site to check (origin is derived from it) |
No output schema declared.
No examples provided.
broken_link_check ~134
Crawl a site starting from a URL (same-origin pages only, bounded by maxPages) and check every linked URL for broken status codes. Returns broken links with the page(s) they were found on. Note: some external sites (e.g. social platforms) block automated HEAD/GET requests and may show up as false positives.
| Name | Type | Req | Description |
|---|---|---|---|
| checkExternal | boolean | – | Also check links pointing off-site (default true; crawling never follows off-site links) |
| maxPages | number | – | Max same-origin pages to crawl (default 20, capped at 50) |
| url | string | yes | Starting URL to crawl |
No output schema declared.
No examples provided.
check_open_ports ~104
TCP-connect scan a host for open ports. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname or IP to scan (no scheme) |
| ports | array | – | Specific ports to check. Defaults to a common-ports list. Max 100 ports per call. |
No output schema declared.
No examples provided.
check_robots_sitemap ~53
Check whether a site has a valid robots.txt and sitemap.xml, and return their raw contents (truncated).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Any URL on the site to check (origin is derived from it) |
No output schema declared.
No examples provided.
cors_policy_check ~59
Send a probe request with a foreign Origin header to a URL and report its CORS response headers. Flags wildcard-origin + credentials combinations and arbitrary-origin reflection, both common CORS misconfigurations.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to probe |
No output schema declared.
No examples provided.
dns_propagation_check ~105
Query a DNS record for a domain against several major public resolvers (Google, Cloudflare, Quad9, OpenDNS) in parallel and compare the answers. Flags mismatches, which usually mean propagation is still in progress after a DNS change.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Bare domain to query, e.g. example.com |
| recordType | string | – | Record type: A, AAAA, MX, TXT, NS, or CNAME (default A) |
No output schema declared.
No examples provided.
domain_availability_check ~128
Check whether a domain is registered, plus scan common typo-squat variants (adjacent-key substitution, letter omission/doubling, transposition) across popular TLDs (.com, .net, .org, .io, .co, .ai, .app, .dev) for brand-protection or domain-flipping research. WHOIS-based; capped at 40 variants checked per call for latency.
| Name | Type | Req | Description |
|---|---|---|---|
| checkSquats | boolean | – | Also scan typo-squat variants (default true) |
| domain | string | yes | Bare domain to check, e.g. example.com |
No output schema declared.
No examples provided.
domain_health_check ~67
Check a domain's registration expiry (via WHOIS) and DNS health: nameservers, A/AAAA, MX, SPF, and DMARC records. Flags common misconfigurations.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Bare domain to check, e.g. example.com (no scheme/path) |
No output schema declared.
No examples provided.
domain_report ~116
Bundle: runs seo_audit, domain_health_check (WHOIS + DNS: nameservers, A/AAAA, MX, SPF, DMARC), and email_deliverability_check (DKIM, SPF lookup-count, DMARC strength, DNSBL) against a domain in one call, one charge. Cheaper than calling the three tools separately. Each sub-check reports independently, so a failure in one doesn't void the others.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Bare domain to report on, e.g. example.com (no scheme/path) |
No output schema declared.
No examples provided.
email_address_validate ~92
Validate a single email address: RFC syntax check, MX record lookup on the domain, disposable/temporary-email-provider detection, and role-account detection (info@, admin@, etc.). Per-address check — different from email_deliverability_check, which audits a whole domain's sending reputation (SPF/DKIM/DMARC/PTR/DNSBL).
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to validate |
No output schema declared.
No examples provided.
email_deliverability_check ~151
Deep-dive email deliverability check for a domain: MX records + reverse-DNS (PTR) on each MX host, common DKIM selector probing, SPF lookup-count (RFC 7208 caps at 10), DMARC policy strength, and DNSBL blacklist lookups (Spamhaus Zen, SpamCop, Barracuda) on MX IPs. Note: public-resolver DNSBL queries are frequently rate-limited or blocked by Spamhaus, so a `listed: null` result means "unknown", not "clean" — treat null results as inconclusive, not as a clean bill of health.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Bare domain to check, e.g. example.com |
No output schema declared.
No examples provided.
favicon_manifest_check ~62
Check a site for favicon, apple-touch-icon, web app manifest, and theme-color presence — a quick completeness check for browser/OS chrome and PWA metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Any URL on the site to check (origin is derived from it) |
No output schema declared.
No examples provided.
github_repo_health_check ~77
Check a GitHub repository's health signals: stars, forks, open issues, license, archived/disabled status, and days since last push. Flags likely-abandoned or unlicensed repos. Useful before depending on a repo.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | Repository owner (user or org) |
| repo | string | yes | Repository name |
No output schema declared.
No examples provided.
ip_geolocation_asn_lookup ~78
Resolve a hostname to its IPv4 addresses and look up each one's ASN, network prefix, country code, and network owner via Team Cymru's DNS-based WHOIS service (no API key). Country-level only — not city/street geolocation.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname or bare IPv4 address to look up |
No output schema declared.
No examples provided.
json_ld_schema_validator ~95
Fetch a URL, extract every JSON-LD (<script type="application/ld+json">) block, and validate basic structure — @context/@type presence plus required fields for common schema.org types (Article, Product, Organization, WebSite, LocalBusiness, BreadcrumbList, FAQPage). Reports per-block errors rather than failing the whole call on one bad block.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to check |
No output schema declared.
No examples provided.
package_vulnerability_check ~125
Look up a package (optionally pinned to a version) against OSV.dev's aggregated vulnerability database (GitHub Advisories, PyPA, RustSec, Go vuln DB, etc.) for known CVEs/advisories. Supports npm, PyPI, crates.io, RubyGems, Go, Maven, NuGet, and Packagist ecosystems. Useful before adding a dependency.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem |
| name | string | yes | Package name |
| version | string | – | Optional exact version to check; omit to check the package generally |
No output schema declared.
No examples provided.
page_performance_check ~57
Fetch a URL and measure time-to-first-byte, total fetch time, and response size. Flags missing compression, missing Cache-Control, oversized payloads, and slow TTFB.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to measure |
No output schema declared.
No examples provided.
pagespeed_insights ~113
Run Google's real PageSpeed Insights (Lighthouse + Chrome UX Report) against a URL: performance score, Core Web Vitals (LCP, CLS, INP/TBT), and real-user field data where available. Authoritative version of a local timing check — hits Google's own infrastructure. Works without an API key at low volume; set GOOGLE_PAGESPEED_API_KEY server-side for higher throughput.
| Name | Type | Req | Description |
|---|---|---|---|
| strategy | string | – | Device strategy (default mobile) |
| url | string | yes | The URL to test |
No output schema declared.
No examples provided.
redirect_chain_check ~57
Follow a URL through every HTTP redirect hop and report the full chain, final destination, and issues like redirect loops, too many hops, or HTTPS-to-HTTP downgrades.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The starting URL to trace |
No output schema declared.
No examples provided.
safe_browsing_check ~64
Check a URL against Google Safe Browsing's malware/phishing/unwanted-software/PUA blocklists. Requires GOOGLE_SAFE_BROWSING_API_KEY to be configured server-side (free Google Cloud API key).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to check |
No output schema declared.
No examples provided.
security_headers_audit ~72
Fetch a URL and audit its response for security-relevant HTTP headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy). Flags missing/misconfigured headers with a score.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to audit |
No output schema declared.
No examples provided.
seo_audit ~96
Fetch a URL and run an SEO audit: title/meta description length, canonical tag, Open Graph + Twitter Card tags, html lang attribute, viewport meta, heading structure, image alt-text coverage, internal/external link counts and generic-anchor-text detection, robots meta (noindex/nofollow), structured data (JSON-LD) presence, and robots.txt/sitemap.xml presence.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to audit |
No output schema declared.
No examples provided.
sitemap_url_validator ~87
Parse a site's sitemap.xml (following one level of sitemap-index nesting) and check the HTTP status of every listed URL. Concurrency-limited, capped at 200 URLs checked per call. Reports broken/redirecting URLs found in the sitemap.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the sitemap.xml to validate (or any page URL — /sitemap.xml on that origin is used) |
No output schema declared.
No examples provided.
ssl_cert_check ~70
Connect to a host over TLS and report its certificate's expiry date, days remaining, issuer, and subject.
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | yes | Hostname to check, e.g. papacasper.com (no scheme/path) |
| port | number | – | TLS port to connect to (default 443) |
No output schema declared.
No examples provided.
ssl_labs_grade ~110
Full SSL Labs-style TLS assessment: overall letter grade, protocol support (TLS 1.0-1.3), cipher strength, certificate chain issues, and known vulnerabilities (Heartbleed, POODLE, etc.) for each endpoint. Slower than ssl_cert_check (can take up to ~90s on a cold cache; SSL Labs caches results for 24h server-side).
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | yes | Hostname to assess, e.g. example.com (no scheme/path) |
No output schema declared.
No examples provided.
structured_data_extract ~178
Fetch a URL and extract structured data deterministically: JSON-LD blocks, OpenGraph/meta tags, and optional caller-supplied CSS-selector fields (e.g. { price: '.product-price', title: 'h1' }). No LLM involved — pure HTML parsing via CSS selectors, so results are exact matches only, not summarized or inferred.
| Name | Type | Req | Description |
|---|---|---|---|
| attr | string | – | Optional HTML attribute to extract instead of text content (e.g. 'href', 'src', 'content'). Applies to all selector fields in this call. |
| selectors | object | – | Optional map of field name -> CSS selector (e.g. { price: '.product-price', headline: 'h1' }). Each field returns an array of matched, whitespace-normalized text values in document order. |
| url | string | yes | The URL to extract from |
No output schema declared.
No examples provided.
tech_stack_fingerprint ~74
Fetch a URL and fingerprint its likely tech stack from response headers (server, x-powered-by, x-generator) and HTML markers (generator meta tag, framework/CMS-specific script or class patterns). Best-effort — not exhaustive, no additional paths are probed.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to fingerprint |
No output schema declared.
No examples provided.
url_to_markdown ~51
Fetch a URL and return its main text content as clean, readable plain text/markdown-ish output. Strips scripts, styles, and HTML tags.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to fetch |
No output schema declared.
No examples provided.
websocket_endpoint_check ~87
Test a WebSocket endpoint (ws:// or wss://): attempts the handshake, reports success/failure, time-to-open in ms, and close code/reason. Useful for verifying a WebSocket server is reachable and completes its upgrade handshake before you wire real traffic to it.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | WebSocket URL to test, e.g. wss://example.com/socket |
No output schema declared.
No examples provided.
What is the mcp-toolbelt server?
mcp-toolbelt is listed in the public MCP registry as com.papacasper/mcp-toolbelt. 29 pay-per-call DNS, SEO, SSL, security, and dev tools for AI agents. x402, no API key. This page covers its hosted endpoint (https://papacasper.com/mcp).
Is the mcp-toolbelt server safe to use?
mcp-toolbelt scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the mcp-toolbelt server expose?
mcp-toolbelt exposes 29 tools: url_to_markdown, security_headers_audit, redirect_chain_check, page_performance_check, cors_policy_check, and 24 more. Their descriptions and schemas cost roughly 2,680 tokens of context every time the server is loaded.
Does the mcp-toolbelt server require authentication?
No. We connected to mcp-toolbelt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the mcp-toolbelt server still maintained?
mcp-toolbelt is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.