Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
One row per game, matched across Kalshi, Polymarket US/Intl and Predict.fun. Mapping only.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
x-api-key标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http mapping https://api.matchwire.win/mcp --header 'x-api-key: your-value'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"mapping": {
"url": "https://api.matchwire.win/mcp",
"headers": {
"x-api-key": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"mapping": {
"type": "http",
"url": "https://api.matchwire.win/mcp",
"headers": {
"x-api-key": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
x-api-key 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 matchwire.win 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:x-api-key
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.1.0)于37天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.