Categories › AI & Agents › Multi-agent, orchestration & workflows
Agent-readiness scanner (0-5 score), robots.txt + llms.txt generators, managed agent enablement.
Remote server: your requests and data go to mudko.com. Claude Code: claude mcp add --transport http agent-ready-kit https://mudko.com/api/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
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 analyscan_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 livendetect_platform — Use this when you need to pick the right deploy instructions for a site (different hosts need different snippets — .htaccess for cPanel vs nrun_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/dvalidate_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 x402verify_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, reportsanalyze_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 (autrecommend_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 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 crequest_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, tighrefine_quote — Use this when the user has shared additional context (organization type, compliance requirements, geography) after an initial request_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 pricetier_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 wiverify_credentials — Use this when the calling agent (or its user) wants to verify our certifications, compliance posture, or operational record before sharing bcreate_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 arequest_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 theget_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 aglist_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 vstart_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 pgenerate_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 fget_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 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 brasubmit_lead — Use this when the user has indicated interest in being followed up with — even before formal checkout. Capture is non-binding. **REQUIRED COcreate_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 INCLget_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 gencheck_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 Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.