Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
One row per game, matched across Kalshi, Polymarket US/Intl and Predict.fun. Mapping only.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
x-api-keyValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http mapping https://api.matchwire.win/mcp --header 'x-api-key: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mapping": {
"url": "https://api.matchwire.win/mcp",
"headers": {
"x-api-key": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"mapping": {
"type": "http",
"url": "https://api.matchwire.win/mcp",
"headers": {
"x-api-key": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
x-api-key secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 6, 2026
The registry name was verified against the domain matchwire.win (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: x-api-key
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 37 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Mapped prediction-market data for Node.js and Python. One client, no dependencies: matchwire.win returns one row per game, matched across Kalshi, Polymarket US, Polymarket International and Predict.fun, with each venue's own market id left intact — the pieces you need to compare a Kalshi API market with its Polymarket API twin without owning a reconciliation job.
Market types are matched too: winners, spreads and handicaps, totals and props. The line is part of the match, so over 45.5 is never confused with over 48.5.
Mapping only — no prices, no order books. Prices come from each venue; this library tells you which market on which venue is the same game.
import { Matchwire } from 'matchwire.win';
const mw = new Matchwire({ apiKey: process.env.MATCHWIRE_API_KEY });
const { rows, seq } = await mw.rows({ sport: 'nfl', venue: ['kalshi', 'poly'] }); const game = rows.find((r) => r.listings.length > 1); console.log(game.name, game.listings.map((l) => ${l.venue}:${l.marketId}));
src/ directory on the global fetch. Nothing installs alongside it.429 is distinguishable from a 401 invalid_key in code, not by string matching.since= for changed rows and tombstones, or the same updates over SSE.https://api.matchwire.win/mcp.npm install matchwire.win # Node.js — zero dependencies
pip install matchwire.win # Python 3.9+ — standard library only
Get a key at [matchwire.win](https://matchwire.win/#pricing) — plans start at $99/month with a 14-day trial on Starter.
Save as quickstart.mjs and run node quickstart.mjs (Needs MATCHWIRE_API_KEY in the environment):
import { Matchwire } from 'matchwire.win';
const mw = new Matchwire({ apiKey: process.env.MATCHWIRE_API_KEY });
const status = await mw.status(); console.log(${status.store.events} games, ${status.store.bound} bound listings);
const { sports } = await mw.sports(); console.log(sports.slice(0, 5).map((s) => ${s.sport} ${s.events}));
const { rows } = await mw.rows({ sport: 'nfl', limit: 3 }); for (const row of rows) { console.log(row.name, row.status, row.listings.map((l) => l.venue).join('+')); }
The repository ships the same thing with formatting and error handling: node examples/quickstart.mjs.
| Method | Endpoint | Returns |
|---|---|---|
status() | GET /api/v1/status | Service and per-venue health, current seq, coverage counts |
sports() | GET /api/v1/sports | Sports with game counts, plus group ids (esports, american-football, …) |
rows(params) | GET /api/v1/rows | One row per game with its per-venue listings |
row(id) | MCP get_row | One game by its mapped id |
stream(params) | GET /api/v1/push | The same updates as Server-Sent Events |
callTool(name, args) | POST /mcp | Any tool the MCP endpoint advertises |
tools() | POST /mcp | The tool list the endpoint advertises |
sport, venue, type, league, status accept a value or a comma list; they combine. since= switches to a delta (changed rows plus tombstones).
venue= kalshi · poly (Polymarket US) · polyintl (Polymarket International) · predictfuntype= winner · total · handicap · map_winner · score · eventstatus= scheduled · live · endedsport= a sport name (baseball, not mlb) or a group id from sports()// Everything that changed since the last call, plus tombstones for pruned games.
let seq = 0; const first = await mw.rows({ sport: 'esports', limit: 5000 }); seq = first.seq;
const delta = await mw.rows({ since: seq }); console.log(delta.rows.length, 'changed', delta.tombstones?.length ?? 0, 'gone');
// Stream instead of polling. for await (const frame of mw.stream({ since: seq })) { console.log(frame.event, frame.data.rows?.length); if (Date.now() - started > 10_000) break; // or AbortController }
Every listing carries the venue's own marketId, a tier (exact, normalized, fuzzy) and a confidence, plus the exact request that reads that market from the venue. Use the mapped row to decide *what* to compare, then read the prices from each venue with the source you already have.
POST https://api.matchwire.win/mcp speaks JSON-RPC 2.0 with your key in the same x-api-key header. Tools: list_sports, find_rows, get_row, get_venue_market, report_issue, service_status. Read-only; every tool result is narrowed by your key's plan exactly like the HTTP API.
import { Matchwire } from 'matchwire.win';
const mw = new Matchwire({ apiKey: process.env.MATCHWIRE_API_KEY });
console.log((await mw.tools()).map((t) => t.name)); const row = await mw.row('ev:nfl:arizona-cardinals:denver-broncos:2026-10-25'); console.log(row.listings.map((l) => l.venue));
Plain text for coding assistants: [matchwire.win/llms.txt](https://matchwire.win/llms.txt) · MCP reference: [matchwire.win/docs/mcp/](https://matchwire.win/docs/mcp/)
import { MatchwireError } from 'matchwire.win';
try { await mw.rows({ sport: 'nope' }); } catch (error) { if (error.isRateLimited) await sleep(error.retryAfterMs); // 429 else if (error.isAuthError) /* key missing or revoked */ ; else if (error.isPlanError) /* outside the plan's sports/venues */ ; else throw error; }
from matchwire import Matchwire
mw = Matchwire(api_key=os.environ["MATCHWIRE_API_KEY"]) rows = mw.rows(sport="nfl", venue=["kalshi", "poly"])["rows"] print(rows0, [l["venue"] for l in rows0])
See python/README.md. Standard library only, Python 3.9+.
MIT. Not affiliated with Kalshi, Polymarket or Predict.fun; venue names are used to say what is mapped.