Local MCP capabilities provider for Expo
Nothing to run from here
Agent Ready Kit 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.
26
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Agent-readiness scanner (0-5 score), robots.txt + llms.txt generators, managed agent enablement.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http agent-ready-kit-mcp https://mudko.com/api/mcp
# 2 — ask your agent for something these tools do
# start_agent_ready_setup, scan_site, detect_platform and 23 more
Agent Ready Kit costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MCAll 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 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. Its publisher asks you to sign in with OAuth: run /mcp in Claude Code and pick this server, and it opens a browser for that once.
claude mcp add --scope user --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 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 — the only sign-in is its publisher’s own, with OAuth.
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
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The user's website URL (with or without https://) |
| agent_name | string | no | Name of the calling agent (for analytics; optional) |
| user_consent_scope | string | no | What the user authorized this agent to do. Honored downstream. |
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/
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Page URL to audit (required). |
| bundle_key | string | no | Customer bundle key — unlocks the full findings list. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | HTTPS URL of the x402 endpoint to validate (probed exactly as given — try the bare URL your discovery doc advertises). |
| method | string | no | HTTP method to probe with (default GET). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | — |
| expectedLevel | number | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Site URL. We fetch the page to detect the vertical. |
| user_provided_vertical_id | string | no | Optional. If the user has already told you their business category (e.g. 'digital_agency', 'healthcare_practice'), pass it here to skip auto-detection. Must match a known vertical id. |
| business_type | string | no | Optional free-text of what the user says they are (e.g. 'pediatric dentist'). Resolved against the schema.org/GBP taxonomy → canonical schema_type, default actions, analytics, value band (returned as |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Site URL — we'll scrape and detect vertical. |
| vertical_id | string | no | Optional pre-known vertical id (skip auto-detect). |
| business_type | string | no | What the customer says they are (e.g. 'pediatric dentist', 'roofing contractor'). Resolved against the schema.org/GBP taxonomy for the canonical schema_type + the standard action set + per-genre analy |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Site URL — we'll scan + detect vertical. |
| include_vertical | boolean | no | Include vertical context block (default true). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service_request | object | yes | — |
| buyer_context | object | no | — |
| constraints | object | no | — |
| calling_agent | object | no | — |
| business_type | string | no | What the customer says they are (e.g. 'pediatric dentist'). Resolved against the taxonomy to anchor the quote on the genre's value band and attach lift/adoption stats for negotiation. |
| display_currency | string | no | Optional ISO 4217 currency for displayed prices. Defaults to USD; canonical pricing is always USD. |
| accept_language | string | no | Optional Accept-Language header value. Used to default display_currency when no explicit override is given. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | — |
| additional_context | object | no | — |
| additional_constraints | object | no | — |
| display_currency | string | no | Optional ISO 4217 currency for displayed prices. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | — |
| max_questions | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service_request | object | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| compliance_filter | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | — |
| user_consent_scope | string | yes | — |
| selected_tier | string | no | — |
| checkout_protocol | string | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | no | PREFERRED. The id of a quote the buyer accepted (from request_quote). We bill the agreed figure from it. |
| amount_usd | number | no | Explicit buyer-confirmed one-time amount in USD, when there's no quote_id. Bounded by the payment provider, not a business cap. |
| tier | string | no | Optional package label for the invoice/metadata. Defaults to the flat $450 package. |
| currency | string | no | Bill the invoice in this currency (default USD). Presentment only — the amount is agreed in USD and converted at our posted rate; the $450 USD floor applies pre-FX. |
| promo_code | string | no | Promotion code, if the buyer has one. Invalid codes are ignored silently. |
| string | yes | Email to bill (required). | |
| domain | string | yes | Customer's primary domain (required). |
| contact_name | string | no | Full name of the buyer / decision-maker. OPTIONAL — helps onboarding; never block the close on it. |
| contact_phone | string | no | Phone number (E.164 format preferred). OPTIONAL — pass it only if the buyer volunteers it. |
| preferred_contact_channel | string | no | How the user wants the specialist to reach out. Defaults to 'email'. |
| best_consult_time | string | no | Free-form hint like 'weekday afternoons ET' or 'after May 10'. Optional but useful. |
| urgency | string | no | Self-reported timeline urgency. Optional. |
| company_name | string | no | Optional company / billing name. |
| timezone | string | no | IANA timezone like 'America/New_York'. Optional but improves consult booking. |
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
No parameter schema on file.
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
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tier | string | no | The package (defaults to the flat $450 kit). |
| string | yes | End user's email (the invoice is sent here) | |
| domain | string | yes | Domain they want made agent-ready |
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_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| siteName | string | yes | — |
| domain | string | yes | Domain only, no protocol |
| description | string | yes | — |
| phone | string | no | — |
| category | string | no | — |
| primaryToolName | string | no | Primary MCP tool name (snake_case, optional) |
| primaryToolDescription | string | no | — |
| bundle_key | string | no | Customer bundle key issued after payment. Without it, only the 2 free starter files are returned. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| siteName | string | no | — |
| domain | string | yes | Domain only, no protocol |
| description | string | no | — |
| phone | string | no | — |
| category | string | no | — |
| primaryToolName | string | no | — |
| primaryToolDescription | string | no | — |
| delivery | string | no | Paid only. Which delivery artifact to package: 'files' = drop-in web-root files (default, any host); 'cloudflare' = a Cloudflare edge Worker (domain on Cloudflare → Level 5, zero origin files); 'wordp |
| bundle_key | string | no | Customer bundle key issued after payment. Without it, only the 2 free starter files are packaged. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_domain | string | yes | The brand's primary domain (no protocol). |
| bundle_key | string | no | Customer bundle key issued after payment. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | Email (required). | |
| domain | string | no | Customer's primary domain. Strongly recommended. |
| source | string | yes | — |
| agent_name | string | no | Name of the calling agent (for analytics). |
| contact_name | string | no | Full name of the person — strongly recommended for human follow-up. |
| contact_phone | string | no | Phone number (E.164 format preferred). |
| preferred_contact_channel | string | no | How to reach the user. Defaults to 'email'. |
| best_consult_time | string | no | Free-form like 'weekday afternoons ET'. Optional but useful. |
| timezone | string | no | IANA timezone like 'America/New_York'. Optional. |
| budget_signal | string | no | Free-form budget hint the user shared (e.g. 'around $500/mo', 'under $5k setup', 'looking for cheapest option'). Drives tailored re-engagement offers. |
| notes | string | no | Free-form context the agent wants the specialist to read. |
| blocker | string | no | CLOSE_OR_HANDOFF: when this is a HANDOFF (you couldn't close), state WHY in one line — e.g. 'needs custom booking integration', 'wants to review with partner', 'price-sensitive, budget unclear'. Lets |
| close_recommendation | string | no | CLOSE_OR_HANDOFF: your one-line recommendation for how the specialist should close this lead — the angle, the tier, the objection to address. |
| custom_tool_specs | array | no | CLOSE_OR_HANDOFF: structured specs for any custom tools the customer needs (booking, quote engine, search, etc.), captured so nothing is lost before the build. One object per tool. |
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:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bundle_key | string | yes | Engagement bundle key (required — this tool is the engagement freebie). |
| string | yes | Customer email — the listing_key is bound to it (required). | |
| resource_url | string | no | HTTPS URL of the endpoint to list (optional). |
| pay_to | string | no | Receiving wallet (0x… on Base) the endpoint pays to (optional). |
| price_usd | number | no | Endpoint price per call in USD (optional). |
| stack | string | no | Server stack — picks the generated kit variant (optional). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listing_key | string | yes | lk_… key issued when the package was purchased (required). |
| resource_url | string | no | HTTPS URL agents will pay — also what the Bazaar crawls. |
| pay_to | string | no | Receiving wallet (0x… EVM address on Base). |
| price_usd | number | no | Price per call in USD. |
| stack | string | no | — |
| service_name | string | no | Bazaar service name (<=32 ASCII chars; defaults to the endpoint host). |
| service_description | string | no | Rich search-prompt-style description — feeds Bazaar ranking. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listing_key | string | yes | lk_… key issued when the package was purchased (required). |
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 Agent Ready Kit 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: —
—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 an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
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.0.3.
1.0.3
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 Agent Ready Kit 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.