Accessibility Ai MCP server. Tools: check color contrast, suggest alt text, check heading hierarchy. Built by MEOK AI Labs.
Free
Tools
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 agent can drive the conversation without re-deciding what to do next.
ArgumentsA call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
—
p95 latency
—
call success
—
uptime 90d
0
calls last 7d
What it does
Free 18-check agent-readiness scanner, robots.txt + llms.txt generator, managed agent enablement.
Quickstart
# 1 — install (mcprush login holds a key from your dashboard)
npx mcprush@latest add agent-ready-kit-mcp
# 2 — ask your agent something
> Free 18-check agent-readiness scanner, robots.txt + llms.txt generator, managed agent enablement.
Agent Ready Kit is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
MUAll 1 server
mudko.com1 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 — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add --transport http agent-ready-kit-mcp https://mudko.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
What you approve
26 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.
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 agent can drive the conversation without re-deciding what to do next.
Takes no parameters.
Example callreturns →
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-resource, auth.md, DNS-AID, Web Bot Auth, agentic-commerce), returns a level 0-5 plus per-check pass/
Takes no parameters.
Example callreturns →
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 slug, confidence, and the signals matched so the calling agent can show its reasoning.
Takes no parameters.
Example callreturns →
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 (HSTS, CSP, X-Content-Type-Options…). FREE tier returns the three section scores + the single most criti
Takes no parameters.
Example callreturns →
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 version, bazaar extension, crawlability) plus the simulated accepted/rejected verdict and current ind
Takes no parameters.
Example callreturns →
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 initial assessment.
Takes no parameters.
Example callreturns →
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 %, current competitor adoption %, and a positioning pitch tailored to the vertical. **If `should_ask_user` i
Takes no parameters.
Example callreturns →
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_quote, check_inventory, verify_insurance_acceptance, etc.
Takes no parameters.
Example callreturns →
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 — chat clients that can't render React get the same story as the web UI. COOPERATIVE SAMPLING: the r
Takes no parameters.
Example callreturns →
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 by default; use display_currency to localise the band. **If the user pushes back on price, asks for
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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 collection.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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 verify us before deepening data sharing.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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`/`amount_usd` it bills the flat **$450** package. Pass `amount_usd` only for custom-tool add-ons ($150 ea
Takes no parameters.
Example callreturns →
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 150 each. Separate opt-in add-ons exist (Bazaar listing 99 one-time, keepalive 19/mo, monitoring 199
Takes no parameters.
Example callreturns →
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 endpoints: no signup, no bundle_key, no engagement — the caller pays USDC on Base and gets the resp
Takes no parameters.
Example callreturns →
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 clears (retrievable at thank_you_url). To add custom tools ($150 each), use request_invoice with an expli
Takes no parameters.
Example callreturns →
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 NOT paste raw file contents into chat — the file bodies are NOT in the response. Render the download_
Takes no parameters.
Example callreturns →
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-encoded in the response — agents decode and offer as a download.
Takes no parameters.
Example callreturns →
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 citation rates, average position, competitor mentions, agent-card discovery rate. Citation data is paid
Takes no parameters.
Example callreturns →
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 specialist needs a real time to dial. ASK FOR ALL THREE explicitly. **FALLBACK**: if the user explici
Takes no parameters.
Example callreturns →
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_bazaar_listing). Buyers WITHOUT a bundle_key purchase the standalone $99 Bazaar Listing Package instead:
Takes no parameters.
Example callreturns →
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 guidance, and an ordered DEPLOY-CHECKLIST. Pass resource_url / pay_to / price_usd / stack here to fill
Takes no parameters.
Example callreturns →
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 valid, if the endpoint's price is within our auto-trigger bound (~$1) WE fire the indexing settlement f
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Agent Ready Kit costs nothing to install and nothing to call, 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: $8.42
$16.58 left
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
Pinned to 0.1.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.1.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Agent Ready Kit in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.