pmq (Polymarket CLOB V2)

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": "io.github.crp4222/pmq",
    "description": "Production-proven Polymarket CLOB V2 trading and data. Fail-closed fills; keys stay local.",
    "title": "pmq (Polymarket CLOB V2)",
    "repository": {
      "url": "https://github.com/crp4222/pmq",
      "source": "github"
    },
    "version": "0.7.1",
    "packages": [
      {
        "registryType": "pypi",
        "registryBaseUrl": "https://pypi.org",
        "identifier": "pmquant",
        "version": "0.7.1",
        "runtimeHint": "uvx",
        "transport": {
          "type": "stdio"
        },
        "environmentVariables": [
          {
            "description": "Set to 1 to register the LIVE trading tools (fak_buy, fak_sell, cancel_and_reconcile). Overridden by PMQ_MCP_PAPER=1; with neither set the server is read-only.",
            "name": "PMQ_MCP_LIVE"
          },
          {
            "description": "Set to 1 for paper trading: trading tools simulate displayed top-of-book fills against real books. No keys or exchange orders. Wins over PMQ_MCP_LIVE.",
            "name": "PMQ_MCP_PAPER"
          },
          {
            "description": "Initial paper balance in USD when a new state file is created (default 1000). Only relevant when PMQ_MCP_PAPER=1.",
            "name": "PMQ_MCP_PAPER_USD"
          },
          {
            "description": "Per-order hard cap in USD enforced before any buy, live and paper alike (default 10).",
            "name": "PMQ_MCP_MAX_USD"
          },
          {
            "description": "Durable cumulative BUY budget per UTC day (off when unset). Unknown live results retain the requested reservation through that UTC day.",
            "name": "PMQ_MCP_DAILY_USD"
          },
          {
            "description": "Local durable paper-ledger and daily-budget file. Defaults to $XDG_STATE_HOME/pmq or ~/.local/state/pmq; it contains no key material.",
            "name": "PMQ_MCP_STATE_FILE"
          },
          {
            "description": "EOA private key used only to sign orders locally when trading tools are enabled. Never printed or transmitted. Not needed for the read-only tools.",
            "isSecret": true,
            "name": "POLY_PRIVATE_KEY"
          },
          {
            "description": "Funder wallet address. Required with signature_type > 0 (deposit wallets); also an optional default for public account_portfolio reads.",
            "name": "POLY_FUNDER"
          },
          {
            "description": "Polymarket signature type: 0 EOA, 1 POLY_PROXY, 2 POLY_GNOSIS_SAFE, 3 POLY_1271 (app deposit wallet). Run pmq-doctor if unsure.",
            "name": "POLY_SIG_TYPE"
          },
          {
            "description": "Append-only file of this server's own order ids. Enables order attribution when several senders share one wallet: account totals then count only orders placed through this server. Optional; without it behavior is unchanged.",
            "name": "POLY_ORDER_LOG"
          },
          {
            "description": "Colon-separated registry files of the wallet's other order-senders. Reconciliation claims trades unknown to every registry. Sound only if every sender on the wallet keeps a registry.",
            "name": "POLY_FOREIGN_ORDER_LOGS"
          }
        ]
      }
    ]
  },
  "_meta": {
    "io.modelcontextprotocol.registry/official": {
      "status": "active",
      "statusChangedAt": "2026-07-14T17:04:41.075781Z",
      "publishedAt": "2026-07-14T17:04:41.075781Z",
      "updatedAt": "2026-07-14T17:04:41.075781Z",
      "isLatest": true
    }
  }
}
```

The server is listed as "pmq (Polymarket CLOB V2)".