Agent Ready Kit

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://mudko.com/api/mcp

claude mcp add --transport http agent-ready-kit https://mudko.com/api/mcp

{
  "mcpServers": {
    "agent-ready-kit": {
      "url": "https://mudko.com/api/mcp"
    }
  }
}

{
  "servers": {
    "agent-ready-kit": {
      "type": "http",
      "url": "https://mudko.com/api/mcp"
    }
  }
}

https://mudko.com/api/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 10, 2026. The maker wrote them, not us; we show them as plain text.

• 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 stat

• 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 dis

• 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

• 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…), s

• 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

• 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 verifica

• 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-

• 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_appo

• 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-r

• 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 a

• 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,

• 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_conte

• 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

• 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

• 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:** wit

• 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, in

• 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 a

• 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

• 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.t

• 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

• 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 — provi

• 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 e

• 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 →

• 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, keepa

• 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 o

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain mudko.com (the registry checks domain ownership)

• ✓ Pass

  Still maintained

  Code last changed 4 months ago

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 172 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 26 tool descriptions and found no hidden instructions to the AI

Compared with others in Search & AI memoryi

• More stars than 0% of the other 5866 servers in this category
• Published to the registry more recently than 30% of the other 5866 servers in this category
• Basic checks equal to or better than 100% of the other 5866 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker