Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Toolbelt is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
29
tools declared
remote
at its publisher
—
calls last 7d
What it does
29 pay-per-call DNS, SEO, SSL, security, WHOIS, mail, and AI tools for AI agents. x402, no API key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http toolbelt-mcp https://papacasper.com/mcp
# 2 — ask your agent for something these tools do
# url_to_markdown, security_headers_audit, redirect_chain_check and 26 more
Toolbelt costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PAAll 1 server
papacasper1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http toolbelt-mcp https://papacasper.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
29 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Fetch a URL and return its main text content as clean, readable plain text/markdown-ish output. Strips scripts, styles, and HTML tags.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to fetch |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to audit |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The starting URL to trace |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to measure |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to probe |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to extract from |
| selectors | object | no | 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. |
| attr | string | no | Optional HTML attribute to extract instead of text content (e.g. 'href', 'src', 'content'). Applies to all selector fields in this call. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to fingerprint |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Any URL on the site to check (origin is derived from it) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to audit |
Check whether a site has a valid robots.txt and sitemap.xml, and return their raw contents (truncated).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Any URL on the site to check (origin is derived from it) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Starting URL to crawl |
| maxPages | number | no | Max same-origin pages to crawl (default 20, capped at 50) |
| checkExternal | boolean | no | Also check links pointing off-site (default true; crawling never follows off-site links) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Any URL on the site to check (origin is derived from it) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to check |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | URL of the sitemap.xml to validate (or any page URL — /sitemap.xml on that origin is used) |
Check a domain's registration expiry (via WHOIS) and DNS health: nameservers, A/AAAA, MX, SPF, and DMARC records. Flags common misconfigurations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Bare domain to check, e.g. example.com (no scheme/path) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Bare domain to query, e.g. example.com |
| recordType | string | no | Record type: A, AAAA, MX, TXT, NS, or CNAME (default A) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host | string | yes | Hostname or bare IPv4 address to look up |
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", no
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Bare domain to check, e.g. example.com |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Bare domain to check, e.g. example.com |
| checkSquats | boolean | no | Also scan typo-squat variants (default true) |
Connect to a host over TLS and report its certificate's expiry date, days remaining, issuer, and subject.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hostname | string | yes | Hostname to check, e.g. papacasper.com (no scheme/path) |
| port | number | no | TLS port to connect to (default 443) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host | string | yes | Hostname or IP to scan (no scheme) |
| ports | array | no | Specific ports to check. Defaults to a common-ports list. Max 100 ports per call. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | WebSocket URL to test, e.g. wss://example.com/socket |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Bare domain to report on, e.g. example.com (no scheme/path) |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to check |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hostname | string | yes | Hostname to assess, e.g. example.com (no scheme/path) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to test |
| strategy | string | no | Device strategy (default mobile) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem |
| name | string | yes | Package name |
| version | string | no | Optional exact version to check; omit to check the package generally |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | Repository owner (user or org) |
| repo | string | yes | Repository name |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | Email address to validate |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Toolbelt or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.3.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 8 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest64d082ee81c9c6bf48d48f60f017f9acef5d8f8e08d817b3b0cced0b9d969198
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| url_to_markdown | untrusted-input | untrusted-input: keyword "fetch", parameter "url" with "fetch" in the description |
| security_headers_audit | untrusted-input | untrusted-input: keyword "fetch", parameter "url" with "fetch" in the description |
| redirect_chain_check | no tags | |
| page_performance_check | untrusted-input | untrusted-input: keyword "fetch", parameter "url" with "fetch" in the description |
| cors_policy_check | no tags | |
| structured_data_extract | untrusted-input | untrusted-input: keyword "fetch", parameter "url" with "fetch" in the description |
| tech_stack_fingerprint | untrusted-input | untrusted-input: keyword "fetch", parameter "url" with "fetch" in the description |
| ai_crawler_policy_check | no tags | |
| seo_audit | untrusted-input | untrusted-input: keyword "fetch", parameter "url" with "fetch" in the description |
| check_robots_sitemap | no tags | |
| broken_link_check | untrusted-input | untrusted-input: keyword "crawl", parameter "url" with "crawl" in the description |
| favicon_manifest_check | no tags | |
| json_ld_schema_validator | untrusted-input | untrusted-input: keyword "fetch", parameter "url" with "fetch" in the description |
| sitemap_url_validator | no tags | |
| domain_health_check | no tags | |
| dns_propagation_check | no tags | |
| ip_geolocation_asn_lookup | no tags | |
| email_deliverability_check | no tags | |
| domain_availability_check | no tags | |
| ssl_cert_check | no tags | |
| check_open_ports | no tags | |
| websocket_endpoint_check | no tags | |
| domain_report | no tags | |
| safe_browsing_check | no tags | |
| ssl_labs_grade | no tags | |
| pagespeed_insights | no tags | |
| package_vulnerability_check | no tags | |
| github_repo_health_check | no tags | |
| email_address_validate | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest64d082ee81c9c6bf
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.0.
1.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Toolbelt can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.