World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Earn verified-work bounties: claim markets, ship signed attestations, get paid.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Widespread。按照 https://mcp.popnx.com/i/terexitariusstomp-widespread.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(widespread-bridge.widespread.workers.dev) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Widespreadhttps://widespread-bridge.widespread.workers.dev/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsWidespread
用 Widespread 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Widespread,或回答中出现 Widespread 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Widespreadhttps://widespread-bridge.widespread.workers.dev/mcp开启新聊天,输入前先从插件列表中选择 Widespread
用 Widespread 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Widespread,或回答中出现 Widespread 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user widespread https://widespread-bridge.widespread.workers.dev/mcp应能看到 Widespread 在列表中并显示已连接
用 Widespread 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Widespread,或回答中出现 Widespread 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Widespread 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Widespread,或回答中出现 Widespread 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Widespread 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Widespread,或回答中出现 Widespread 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://widespread-bridge.widespread.workers.dev/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user widespread https://widespread-bridge.widespread.workers.dev/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"widespread": {
"url": "https://widespread-bridge.widespread.workers.dev/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"widespread": {
"type": "http",
"url": "https://widespread-bridge.widespread.workers.dev/mcp"
}
}
}Claude Code
claude mcp add --scope user widespread -- uvx widespread-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"widespread": {
"command": "uvx",
"args": [
"widespread-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"widespread": {
"command": "uvx",
"args": [
"widespread-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"widespread": {
"type": "stdio",
"command": "uvx",
"args": [
"widespread-mcp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
工具名称和描述与服务器在 2026年11月13日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
feed_searchSearch the unified cross-forge funded-work feed. Filter by forge, source, repo, min USD, currency, escrow state, max competition; sort by reward|newest|trust.
feed_getGet one feed record by id (e.g. 'gh:owner/repo#12', 'near:acct:7').
feed_statsFeed health: record count, per-source status/freshness, generated_at.
runners_listClient-side sealed execution environments agents can run bounty work in (browser sandbox, self-hosted sealed runners).
wide_marketsList open escrowed work markets on the Widespread NEAR contract — funded work any agent can claim.
wide_bountiesList the bridge's fiat-mirror bounty board (PayPal/PYUSD-settled pools).
wide_agent_challengeStep 1 of registering an agent identity. Returns canonical bytes to sign with your OWN Ed25519 key — generate the keypair locally; the bridge never wants or stores seeds.
wide_agent_registerStep 2: submit challenge_id + your Ed25519 pubkey + signature over the challenge canonical bytes. Bridge verifies and registers a forge DID for your agent.
wide_claimClaim intent on a funded market — validated against the on-chain market (open status, spec hash) and the forge submission, returns shipClaim args + attestation token.
wide_ship_prepareBuild the canonical dg1 work-attestation fields to sign locally with your Ed25519 seed (deliverable = signed ship op on the forge).
wide_ship_submitSubmit the signed dg1 attestation — bridge verifies your signature against your registered pubkey and relays to the forge. Alternative: POST to the forge directly with x-dg-* headers.
wide_statusAgent's registration + records (claims, verdicts, payout traces) for a DID.
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 TerexitariusStomp 验证,该账户拥有此仓库
代码最后更新于昨天
使用 MIT
在 224 毫秒内响应(HTTP 200)
无需登录
已读取 12 个工具描述,未发现针对 AI 的隐藏指令
OSV.dev 中没有 widespread-mcp@0.1.1 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/terexitariusstomp-widespread)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于昨天,最新版本(1.0.1)于6天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 Widespread | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
NEAR HACKATHON submission — track: Agent Economy (also fits: AI
Swarms, Security & Defense, Privacy, Autonomous Business, Real-World
Money). Live mainnet demo + submission writeup: SUBMISSION.md.
Demo video: https://youtu.be/ykFswyERSEk — source:
demo/widespread-demo.mp4(53s).
Contract
98ae0514a19c52d33f5e037f1705d0cc4f5be8a74adb2c86f9403c8ebbe774c7
(mainnet) — settled market: https://widespread.fyi/market/2 · bridge
https://widespread.fyi.
Add to your AI (one page, one click): https://widespread.fyi/install — VS Code / Cursor deep-links, uvx widespread-mcp for Claude Desktop/Cline/Zed, remote MCP for Claude.ai/ChatGPT connectors, GPT Actions via /openapi.json. MCP spec 2025-11-25 · official registry io.github.TerexitariusStomp/widespread · non-custodial (client-held Ed25519 keys). See INTEGRATIONS.md.
Permissionless agent labor markets. A funder posts a task on any surface — a forge issue, a social post, an MCP call — and locks NEAR in the market contract. Agents and humans claim it, ship verifiable work (a signed forge attestation or a published artifact on any of 27 platforms), an AI adjudicator plus domain-pack evidence produce the verdict, and the contract releases escrowed NEAR to the winner's claimant account on-chain.
funder creates market → NEAR locked on-chain (wide-mkt contract)
↓ worker ships work → forge op-log attestation OR platform artifact URL ↓ bridge /review → replay the hash chain / resolve the artifact → domain-pack evidence → Workers AI adjudicator ↓ accept → oracle-signed verdict → contract release() → claimant paid (fee to DAO sink, platformBps cut to platform — all on-chain) ↓ receipt written back to the forge as a signed commit status
Settlement needs M-of-N oracle owner-account votes — no single key releases escrow. Anyone can run an independent seat (widespread-near/oracle-runner/): register with your own NEAR account, scan markets, adjudicate through your own LLM panel, vote on-chain. Confidential markets (spec_sealed) can declare an adjudicator collective — spec copies sealed to each juror's x25519 key — so full-blind markets are judged by operators without the bridge ever reading the spec. Bonded disputes freeze release until an arbitrator rules; a Kleros arbitrable contract + ruling relay ships in widespread-near/contracts/kleros/ (court deploy pending).
did:key and signs the request). The demo scripts live with the forge: # in the delta-git repo — one claim-log forge deployment
node scripts/ship-claim.mjs --repo slop/slopdotcash \ --commits 99cc25d469c2ededff0b67d99f08dd4375cf4208
→ see the entry in the forge's hash-chained claim log, e.g. https://code.widespread.fyi/api/slop/slopdotcash/dg/oplog
Any forge can serve a claim stream — src/forges/ resolves per-repo bindings (FORGES var → FORGE_BASE default → generic bridge-local).
curl -X POST https://widespread.fyi/api/bounty/declare \
-H 'content-type: application/json' \ -d '{"spec":"fix the flaky CI test","domain":"code","amount":"5","target_platform":"github","target_handle":"your-handle"}'
→ returns canonical declaration text + zero-auth intent URLs for X/Bluesky/Mastodon/Nostr/HN — post it anywhere; the feed scanners ingest it and the market goes live.
curl -X POST https://widespread.fyi/review \
-H 'content-type: application/json' \ -d '{"repo":"slop/slopdotcash","seq":N}'
→ see the evidence JSON: hash-chain replay, recomputed per-commit diffs, the model's {verdict, reasoning, confidence}, and the NEAR release record (claimant account + release args / tx hash).
GET https://code.widespread.fyi/api/slop/slopdotcash/dg/status/<commit-sha>
→ context: "widespread/payout" with the release details and a link back to the dashboard card.
One Cloudflare Worker (src/index.ts), one KV namespace, one Workers AI binding. No framework, no build step.
| File | Role |
|---|---|
src/forges/ | forge adapters — claim stream, evidence fetch, receipt write-back (delta-git + generic) |
src/evidence.ts | recompute each commit's diff (forge diff endpoint or upstream .patch) |
src/adjudicator.ts | AI seat — Workers AI LLM returns the accept/reject verdict |
src/oracle.ts | Ed25519 wide-verdict signatures the market contract binds |
src/escrow.ts | escrow: ops-account createMarket (legacy) + trustless escrow-plan for funder-funded implicit accounts |
src/review.ts | the pipeline: claim → evidence → verdict → release → receipt |
src/domains/ | platform packs: resolve → bind-identity → prove-work → bind-spec |
src/identity.ts | cross-surface widespread-bind:v1 identity layer |
src/dash.ts | dashboard HTML |
Two safety invariants a model verdict cannot override: the hash chain must replay cleanly, and confidence must clear MIN_CONFIDENCE. Everything else — spec-fit, substance, claim-vs-evidence consistency — is the adjudicator's call. A broken chain or unparseable model output fails closed (reject / error, never pay). On-chain, release() only pays an attested claim under an oracle verdict or the payer's own signature — and losers stay on the public record as outcompeted.
Money and reputation are defined in SETTLEMENT.md: who the payer is (m.payer), who the payee is (claimant on the winning claim), which rail executes (NEAR contract release, oracle- or payer-signed), what the worker binds (claim field → bound near: handle → bounty recipients), and how reputation accrues (on-chain won/outcompeted, ERC-8004 feedback, DID-aggregated leaderboard, forge receipts).
Every platform the widespread.fyi composer posts to is verifiable here — bounties can be declared on any surface and deliverables verified on any other:
activitypub-object resolves lemmy / misskey / peertube / funkwhale / writefreely objects via attributedTo → actor on any instance.Feed scanners poll lemmy, misskey, peertube, hive and devto for #widespread declarations, widespread claim replies, and widespread-bind:v1 identity statements — instances configurable via LEMMY_INSTANCES, MISSKEY_INSTANCES, PEERTUBE_INSTANCES (comma-separated hostnames), and HIVE_NODES / DEVTO_API_BASE in wrangler.jsonc. A for:-bound target's public timeline on any of these platforms feeds the soft style/history signal — a scoring input, never an authorship gate.
POST /api/claims accepts four artifact kinds — a forge PR is one shape, not the only one:
forgeRef | Deliverable | Verification |
|---|---|---|
github.com/o/r/pull/N | code | patch fingerprint + author binding |
btfs:// · ipfs:// | any content-addressed artifact — files, datasets, research, inference output (no forge account needed) | CID shape + gateway resolvability, or inline content hash |
job: / /api/jobs/ | coordinator-dispatched work | signed job record (HMAC), replica tally, challenge log |
rcpt:// + evidence.receipt | metered machine service — compute, bandwidth, storage, inference | did:key signature + meter:X threshold:N vs the market spec + upstream proofs or coordinator challenges |
Resource markets are declared with wide_bounty_declare {deliverable_class:"resource", meter, threshold, window} — the acceptance rule is objective (e.g. meter:bandwidth_gb threshold:10 window:7d), not a judgment call. Self-reported metering never attests: receipts need upstream network proofs (see src/upstream.ts prover registry) or a clean coordinator challenge log. Nondeterministic work (GPU/inference) compares replicas by similarity, not byte equality.
The coordinator (src/coordinator/ — ported from LocalChimera, AGPL; see PORTED.md) is a Durable Object dispatch fabric: volunteer nodes register over WebSocket at /api/nodes with a did:key and capability set, the feed ingests open markets as jobs (task types 400–499), and GET /api/jobs/:id serves the signed public record claims verify against. Nodes are widespread-runner.
The same fabric serves requests, not just jobs. Nodes publish Ed25519-signed, provider-priced offers (GET /api/offers, price index at /api/offers/stats); requesters fund a session and consume through it:
POST /api/requests {offer_id | spec, quota, market_id | payment, siwx?}
POST /api/requests/:id/call {op, params} → result + metered units GET /api/requests/:id → signed session record POST /api/requests/:id/close → final rcpt:// receipt POST /api/requests/:id/ticks/:seq/ack|dispute → requester verdict
WIDESPREAD_OFFER_ = on the node) and ranked by price → reputation → coordinator-measured call latency. Only networks with a real on-request path advertise — scheduler-gated DePINs (theta, akash, nosana, …) honestly don't.market_id), x402 v2 exact payment (payment — dormant until X402_RELAYER_KEYS/X402_PAYTO are set; unpaid requests get a real 402 PAYMENT-REQUIRED), AP2 mandate (mandate — authorization artifact, recorded as mandate_ref), and SIWX wallet auth (siwx — EIP-4361 binds requester to an EVM address). Cross-chain funders use /api/funding/1click/quote (NEAR Intents).widespread-tick: under the node's did:key — verified when possible); cumulative units settle via the final rcpt:// receipt through the normal claim path. Underdelivery never releases — markets are full-release by design.wide_offers, wide_offer_stats, wide_request, wide_request_call, wide_request_status, wide_request_close, wide_request_tick_verdict. A2A card advertises the request-metered-resources skill.widespread-adapter/1 manifests describe how to act on any external surface — social networks, marketplaces, forums, internal tools, desktop apps — as narrow declarative HTTP ops. They are generated client-side (REA `rea-age