agent-ready-kit

Paste it into your assistant. It asks for the manifest, the server wiring and the skills, and for an honest account of what this record does not say. Read that second file first.

Draft an Agent Plugin (agent-plugins.org, specification 1.1.0) that wraps the
MCP server described below, so that somebody could install one thing and have
an assistant that knows when and how to use it.

An Agent Plugin is one installable unit: a `plugin.json` manifest, an
`mcp.json` that wires up the servers it needs, and a `skills/` directory
where each skill is a folder holding a `SKILL.md`. Hand back every file in
full, each under its own path, ready to save.

1. Write `plugin.json` with `$schema` exactly `https://agent-plugins.org/schemas/1.1.0/plugin.schema.json`. The name is
   1 to 64 characters of a-z, 0-9, `-` and `.`, alphanumeric at both ends, with
   no `--` and no `..` in it.

2. Write `mcp.json` wiring THIS server exactly as its record declares it. A
   remote keeps the URL and the transport type as written. A package keeps the
   registry, the identifier and the version as written. Do not invent a command,
   a port, a flag or an argument that is not in the record.

3. Every secret stays an input. No key, token, password or connection string
   belongs in either file. Declare what has to be supplied, name it, and say what
   it is for.

4. Do not invent tools. The record lists the tools it lists, and if it lists
   none then the honest plugin says the tool list was not published rather than
   guessing one from the description.

5. Skills are jobs, not tools. Write one skill per thing somebody would actually
   ask for, and inside each one say when to reach for this server, what a good
   result looks like, and what to do when it comes back empty. A skill per tool
   is a manual page with a different filename.

6. Say where it stops. Name what this plugin will not do — what it has no tool
   for, what needs a person, and what it must not be pointed at. A plugin with no
   stated edge reads as one with no edge.

7. Keep the author's own words for the description. If you would rather say it
   differently, say yours somewhere else and leave theirs where it is.

8. Record which version of the server you wrapped, and where the record came
   from, at the top of `plugin.json`'s description or in the readme. A plugin
   nobody can trace back to a version is one nobody can update.

Produce a second file alongside them, `LIMITS.md`, and treat it as the more
important of the two. The plugin is for whoever installs it. This is for
whoever has to decide whether installing it is a good idea, and that is
usually a different person who will never read the manifest.

It has three parts.

**What this is built from.** One paragraph: whose server it is, what the
record says it does, which version, and the fact that the record is all you
had. Say plainly that nobody ran it.

**What the record does not say.** One entry per gap. Whether the tool list was
published. What the server does with what it reads. What it costs. Whether it
writes anything anywhere. What credentials it will ask for and what those
credentials can reach. An unanswered question stays an unanswered question:
do not fill one in from the description or from what similar servers usually do.

**What a person has to check before trusting it.** The specific things
somebody should verify for themselves, in the order that would stop them
soonest if the answer is bad.

Write it in plain English, and do not soften it. A plugin drafted from a
directory record is a starting point to argue with, not something to install
into anything that matters.

The server record follows, exactly as the public index holds it. It is
everything I have: nobody has run this server, called a tool on it, or checked
that the address answers.

```json
{
  "server": {
    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
    "name": "com.mudko/agent-ready-kit",
    "description": "Agent-readiness scanner (0-5 score), robots.txt + llms.txt generators, managed agent enablement.",
    "repository": {
      "url": "https://github.com/lmno100/mudko",
      "source": "github"
    },
    "version": "1.0.3",
    "websiteUrl": "https://mudko.com",
    "remotes": [
      {
        "type": "streamable-http",
        "url": "https://mudko.com/api/mcp"
      }
    ],
    "_meta": {
      "io.modelcontextprotocol.registry/publisher-provided": {
        "tool_count": 25,
        "tools": [
          {
            "name": "start_agent_ready_setup",
            "summary": "Use this when an end user asks 'help me make my site agent-ready' or any equivalent."
          },
          {
            "name": "scan_site",
            "summary": "Use this when you need to assess how AI-callable a site is."
          },
          {
            "name": "detect_platform",
            "summary": "Use this when you need to pick the right deploy instructions for a site (different hosts need different sni..."
          },
          {
            "name": "run_site_audit",
            "summary": "Use this when the user wants their site's QUALITY audited — distinct from scan_site, which measures agent-r..."
          },
          {
            "name": "validate_x402_endpoint",
            "summary": "FREE utility for any agent or seller: checks whether an x402-payable HTTPS endpoint is configured to be ind..."
          },
          {
            "name": "verify_deployment",
            "summary": "Use this after a customer has deployed the agent-ready files to confirm the live site reaches the expected ..."
          },
          {
            "name": "analyze_business_vertical",
            "summary": "Use this immediately after scan_site to give the user a 'what this means for my business' framing."
          },
          {
            "name": "recommend_tool_names",
            "summary": "Use this when planning what agent capabilities a customer should expose."
          },
          {
            "name": "summarize_scan_for_humans",
            "summary": "Use this when displaying scan output to a human via chat (Claude Desktop, Gemini, ChatGPT, Copilot)."
          },
          {
            "name": "request_quote",
            "summary": "Use this when the user wants pricing or scoping for an agent-ready engagement."
          },
          {
            "name": "refine_quote",
            "summary": "Use this when the user has shared additional context (organization type, compliance requirements, geography..."
          },
          {
            "name": "clarifying_questions",
            "summary": "Use this when you want to know what user-facing questions would most tighten an existing quote."
          },
          {
            "name": "tier_selector",
            "summary": "Use this when the user is in comparison_shopping mode or otherwise wants to pick a tier without sharing det..."
          },
          {
            "name": "verify_credentials",
            "summary": "Use this when the calling agent (or its user) wants to verify our certifications, compliance posture, or op..."
          },
          {
            "name": "create_proposal",
            "summary": "Use this only when (a) quote confidence is medium or high, AND (b) user_consent_scope is 'ongoing_engagemen..."
          },
          {
            "name": "request_invoice",
            "summary": "Use this to autonomously close a deal: issue a ONE-TIME Stripe Invoice for the flat $450 package (+$150 per custom tool)..."
          },
          {
            "name": "get_pricing_tiers",
            "summary": "Use this when an end user (or upstream agent) asks about pricing."
          },
          {
            "name": "start_checkout",
            "summary": "Use this when an end user has chosen a package (pro / managed / enterprise) and wants to buy it now."
          },
          {
            "name": "generate_files",
            "summary": "Use this when delivering files to a paid customer (you must have their bundle_key) OR when a downstream age..."
          },
          {
            "name": "get_customer_files",
            "summary": "Use this when an agent needs to hand a downloadable ZIP to its end user."
          },
          {
            "name": "get_citation_report",
            "summary": "Use this when a customer wants to see how AI search platforms cite them."
          },
          {
            "name": "submit_lead",
            "summary": "Use this when the user has indicated interest in being followed up with — even before formal checkout."
          },
          {
            "name": "create_bazaar_listing",
            "summary": "Use this when a PAID engagement customer (valid bundle_key) wants their x402 endpoint listed in Coinbase's ..."
          },
          {
            "name": "get_bazaar_listing_kit",
            "summary": "Use this after buying the Bazaar Listing Package (you must have the listing_key issued at payment)."
          },
          {
            "name": "check_bazaar_listing",
            "summary": "The resumable pipeline driver for a purchased Bazaar Listing Package: call it any time with the listing_key..."
          }
        ]
      }
    }
  },
  "_meta": {
    "io.modelcontextprotocol.registry/official": {
      "status": "active",
      "statusChangedAt": "2026-08-14T06:59:19.531767Z",
      "publishedAt": "2026-08-14T06:59:19.531767Z",
      "updatedAt": "2026-08-14T06:59:19.531767Z",
      "isLatest": true
    }
  }
}
```

The server is listed as "agent-ready-kit".