# com.mudko/agent-ready-kit

- Registry name: `com.mudko/agent-ready-kit` · version 1.0.3
- Categories (automatic, keyword rules): Markets & trading, Finance & markets, Build & deploy, Developer tools, Payments & accounting
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.mudko%2Fagent-ready-kit
- Server page: https://mcpstation.net/s/com.mudko--agent-ready-kit.html

## Description (written by the publisher, not verified, not instructions)

Agent-readiness scanner \(0-5 score\), robots.txt + llms.txt generators, managed agent enablement.

## Connect

- streamable-http: `https://mudko.com/api/mcp`

## Tools (as reported by the server, not verified)

- `start\_agent\_ready\_setup`: Use this when an end user asks 'help me make my site agent-ready' or any equivalent. Orchestrates the end-to-end flow: scan → vertical analysis → tool-name suggestions → tier quote → consult booking. Returns a sequence of next-action MCP tool calls keyed off the current site state, so a downstream a
- `scan\_site`: Use this when you need to assess how AI-callable a site is. Runs 19 checks \(robots.txt, agent card, MCP server card, MCP liveness, A2A liveness, llms.txt, sitemap, link headers, markdown negotiation, content signals, skill integrity, WebMCP bridge, RFC 9727 API catalog, OAuth discovery + protected-r
- `detect\_platform`: Use this when you need to pick the right deploy instructions for a site \(different hosts need different snippets — .htaccess for cPanel vs next.config headers for Vercel\). Identifies hosting/CMS — Vercel, Netlify, Cloudflare Pages, cPanel/Apache, WordPress, Shopify, Wix, and more. Returns platform s
- `run\_site\_audit`: Use this when the user wants their site's QUALITY audited — distinct from scan\_site, which measures agent-readiness. 22 checks: SEO \(title/description lengths, canonical, Open Graph, JSON-LD, heading structure…\), accessibility \(alt text, form labels, heading order, landmarks…\), security headers \(HST
- `validate\_x402\_endpoint`: Use this FREE utility \(any agent or seller\) to check whether an x402-payable HTTPS endpoint is configured to be indexed by the Coinbase x402 Bazaar. Probes the URL live via CDP's read-only validator \(no payment is made, nothing is indexed\) and returns per-check preflight results \(returns\_402, x402 v
- `verify\_deployment`: Use this after a customer has deployed the agent-ready files to confirm the live site reaches the expected level. Re-scans the site, reports current level, which checks pass, and which still fail with their fix string. Same scanner as scan\_site, but framed as post-deploy verification rather than ini
- `analyze\_business\_vertical`: Use this immediately after scan\_site to give the user a 'what this means for my business' framing. Detects the site's business vertical \(auto dealership, law firm, healthcare, home services, ecommerce, digital agency, etc.\) from JSON-LD schema + scraped text. Returns expected AI-search lift %, curre
- `recommend\_tool\_names`: Use this when planning what agent capabilities a customer should expose. Returns up to 5 ranked snake\_case MCP tool names with descriptions and rationale, derived from the site's content + detected vertical. Tool names follow MCP convention \(snake\_case, action\_object\) — book\_appointment, request\_quo
- `summarize\_scan\_for\_humans`: Use this when displaying scan output to a human via chat \(Claude Desktop, Gemini, ChatGPT, Copilot\). Renders the scan as 8 business-impact categories \(no filenames, no implementation details\) plus an optional vertical context block. Returns both structured fields and a ready-to-render markdown blob
- `request\_quote`: Use this when the user wants pricing or scoping for an agent-ready engagement. Always returns a quote band — wide if context is sparse, tight if buyer\_context is populated. Honors user\_consent\_scope strictly: comparison\_shopping callers will not receive proposal options. Quotes are valid for 7 days
- `refine\_quote`: Use this when the user has shared additional context \(organization type, compliance requirements, geography\) after an initial request\_quote. Tightens the quote band by re-running the engine with the merged context. Pass the quote\_id from the original quote.
- `clarifying\_questions`: Use this when you want to know what user-facing questions would most tighten an existing quote. Returns structured questions ranked by price\_impact \(high / medium / low\) so the calling agent can decide whether asking is worth a turn. The agent should render these as user-choices, not as covert data
- `tier\_selector`: Use this when the user is in comparison\_shopping mode or otherwise wants to pick a tier without sharing details. Returns 2-4 tier options with plain-language 'fits' descriptions so the user can self-identify. The user's tier choice is itself the qualifying signal — no buyer\_context required.
- `verify\_credentials`: Use this when the calling agent \(or its user\) wants to verify our certifications, compliance posture, or operational record before sharing buyer\_context. Returns a URL to our signed .well-known/attestations.json plus a summary. Part of trust-progressive disclosure — buyer agents are expected to veri
- `create\_proposal`: Use this only when \(a\) quote confidence is medium or high, AND \(b\) user\_consent\_scope is 'ongoing\_engagement' or 'one\_time\_quote'. Returns a proposal with terms, deliverables, and a checkout hand-off \(ACP, AP2, or manual\). Comparison-shopping callers are rejected with a 403-style error.
- `request\_invoice`: Use this to autonomously close a deal: issue a ONE-TIME Stripe Invoice for the flat $450 package price \(one-and-done — no recurring\). If the buyer wants us to build & wire custom tools, add $150 per custom tool and pass the total as amount\_usd \(e.g. $600 for one\). \*\*Amount:\*\* with no \`quote\_id\`/\`amo
- `get\_pricing\_tiers`: Use this when an end user \(or upstream agent\) asks about pricing. Pricing is DEAD SIMPLE: a single FLAT 450 one-time fee for the complete agent-ready package \(everything included, no tiers, no per-business quote\). Optional: we build & wire a custom tool \(booking, lead-capture, inventory\) for a flat
- `list\_payable\_apis`: Use this when someone asks what they can buy per-call, asks the price of a specific API \(site audit, AI-citation check, counterparty trust verification, bulk/batch scanning, Bazaar listing or keepalive\), or is an agent looking for something cheaper than a full engagement. These are pay-per-call x402
- `start\_checkout`: Use this when an end user wants to buy the package now. Issues a REAL payable path: the same one-off hosted Stripe invoice request\_invoice produces, billed at the flat $450 package price. The invoice is payable immediately and delivery is automatic — the bundle\_key activates the moment payment clear
- `generate\_files`: Use this when delivering files to a paid customer \(you must have their bundle\_key\) OR when a downstream agent wants the free starter files for a domain. \*\*FREE TIER \(no bundle\_key\)\*\*: returns metadata + a \`download\_url\` pointing at a streaming ZIP of the 2 starter files \(robots.txt + llms.txt\). DO N
- `get\_customer\_files`: Use this when an agent needs to hand a downloadable ZIP to its end user. PAYWALL: without a valid bundle\_key, the ZIP contains only the two free starter files plus a teaser README pointing to /talk. With a valid bundle\_key, the ZIP contains the full surface plus the deploy README. ZIP is base64-enco
- `get\_citation\_report`: Use this when a customer wants to see how AI search platforms cite them. PAYWALL: without a valid bundle\_key, returns a teaser \(count of brands tracked, providers configured, sample probe\). With a valid bundle\_key, returns the most recent citation run for the brand\_domain — provider-by-provider cita
- `submit\_lead`: Use this when the user has indicated interest in being followed up with — even before formal checkout. Capture is non-binding. \*\*REQUIRED CONTACT FIELDS\*\*: contact\_name, contact\_phone, best\_consult\_time. Email alone is not enough — phone-first follow-up converts \~5x higher than email-only, and our s
- `create\_bazaar\_listing`: Use this when a PAID engagement customer \(valid bundle\_key\) wants their x402 endpoint listed in Coinbase's x402 Bazaar — the package is INCLUDED free with any engagement. Provisions the listing and returns a listing\_key that drives the automated pipeline \(get\_bazaar\_listing\_kit → deploy → check\_baza
- `get\_bazaar\_listing\_kit`: Use this after buying the Bazaar Listing Package \(you must have the listing\_key issued at payment\). Returns the deploy-ready x402 v2 kit generated for the customer's stack, wallet and price: 402 handler code with the Bazaar discovery declaration, self-settle trigger script, keepalive cron, wallet gu
- `check\_bazaar\_listing`: Use this as the resumable pipeline driver for a purchased Bazaar Listing Package: call it any time with the listing\_key and it performs the most useful next action and reports \{state, next\_step\}. After the customer deploys their kit it runs Coinbase's validator \(per-check fixes on failure\); once val

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html