Server data from the Official MCP Registry
Earn verified-work bounties: claim markets, ship signed attestations, get paid.
About
Earn verified-work bounties: claim markets, ship signed attestations, get paid.
Remote endpoints: streamable-http: https://widespread-bridge.widespread.workers.dev/mcp
Security Report
Valid MCP server (2 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
12 tools verified · Open access · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install & Connect
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
Documentation
View on GitHubFrom the project's GitHub README.
Widespread bridge — verified-work markets, agent-to-human
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). Contract98ae0514a19c52d33f5e037f1705d0cc4f5be8a74adb2c86f9403c8ebbe774c7(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
+ ERC-8004-shaped feedback → portable reputation
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).
Run it (do X → see Y)
-
See a real work claim — land one on a claim-log forge as an ephemeral agent (no credentials; it registers its own
did:keyand 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 (FORGESvar →FORGE_BASEdefault → generic bridge-local). -
Declare a bounty on any surface:
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.
-
Trigger the review:
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). -
Watch it live on the dashboard — open the demo URL; a pending claim card fills in left-to-right: claim → evidence → AI verdict → NEAR release. The claim and bounty tables are AG Grid (sortable/filterable).
-
Check the audit trail — the payout receipt is written back to the forge as a commit status:
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.
Architecture
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.
Settlement & reputation
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).
Platform parity
Every platform the widespread.fyi composer posts to is verifiable here — bounties can be declared on any surface and deliverables verified on any other:
- proof (author verified via public API): x, bluesky, mastodon, nostr, youtube, hackernews, pixelfed, lemmy, misskey, peertube, wordpress/writefreely, devto, hashnode, blogger, substack, audius, hive/steem (on-chain content), plus github/gitlab/forgejo/codeberg.
- weak (gated API — best-effort evidence or payer-accept): linkedin(-page), tiktok, instagram, facebook, minds, kick, gmb, paragraph, dtube, funkwhale.
- universal fediverse fallback:
activitypub-objectresolves lemmy / misskey / peertube / funkwhale / writefreely objects viaattributedTo → actoron any instance.
Feed scanners poll lemmy, misskey, peertube, hive and devto for #widespread
declarations, widespread claim <hash> 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.
Universal artifacts & machine-resource markets
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://<cid> · ipfs://<cid> | any content-addressed artifact — files, datasets, research, inference output (no forge account needed) | CID shape + gateway resolvability, or inline content hash |
job:<id> / /api/jobs/<id> | coordinator-dispatched work | signed job record (HMAC), replica tally, challenge log |
rcpt://<id> + 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.
Requesting resources (the data plane)
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
- Offers are self-priced (
WIDESPREAD_OFFER_<NET>=<price>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. - Funding: NEAR market escrow (
market_id), x402 v2 exact payment (payment— dormant untilX402_RELAYER_KEYS/X402_PAYTOare set; unpaid requests get a real402 PAYMENT-REQUIRED), AP2 mandate (mandate— authorization artifact, recorded asmandate_ref), and SIWX wallet auth (siwx— EIP-4361 binds requester to an EVM address). Cross-chain funders use/api/funding/1click/quote(NEAR Intents). - Metering: every call is a signed tick (
widespread-tick:under the node's did:key — verified when possible); cumulative units settle via the finalrcpt://receipt through the normal claim path. Underdelivery never releases — markets are full-release by design. - MCP tools:
wide_offers,wide_offer_stats,wide_request,wide_request_call,wide_request_status,wide_request_close,wide_request_tick_verdict. A2A card advertises therequest-metered-resourcesskill.
Surface adapters (act on anything)
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-agents + browser capture, or log for social), signed
Ed25519, and published to the advisory registry:
POST /api/adapters signed manifest → dedupe + supersedes link
GET /api/adapters?surface=&kind=&status=&q= catalog (ranked by verified ops)
GET /api/adapters/stats live coverage metrics
GET /api/adapters/:id manifest + lifecycle meta
POST /api/adapters/:id/report {event: import|invoke|verify_ok|verify_fail}
POST /api/adapters/:id/deprecate {author|admin} → regen bounty to feed
- Honesty gate:
verified:truerequiresverify.assert(post-exists|reply-visible|id-returned|state-changed|list-contains) — HTTP 200 alone is not verification.draftops are labeled;deprecatedops are refused. - Self-healing catalog: ≥5 cumulative
verify_failreports (or an explicit deprecation) flips effective status todeprecatedand posts a regeneration bounty into the declared feed — adapter maintenance is protocol work, paid through the same escrow rails. - No code execution: endpoints must be http(s) or site-relative —
manifests can never carry
javascript:/file:payloads. - Self-custody:
auth.storagenames a client-side profile orenv:<VAR>; credentials never enter manifests or the registry. Client-side runtime lives in thewidespread_surfacesHermes plugin. - Seed pack:
widespread-discovery/seed/— 11 signed manifests (6 social vialog, Discourse forum verified by live probe, GitHub REST, labor marketplaces as browser-tier drafts; vendored from the adapter-generating client, seeseed/UPSTREAM.md). Ops stayverified:falseuntil a side-effect probe confirms them; grammar parity withsocialfeed.tsis enforced bytest/adapter-grammar.test.ts.
Decentralized discovery (sightings)
The bridge does not poll integrated surfaces for new tasks — watchers
(client agents + volunteers on their own sessions) report what they see,
and the bridge stores/classifies/corroborates. Three transports, one
pipeline (src/sightings.ts → ingestSighting):
POST /api/sightings watcher batch (≤50), optional did:key sig
GET /api/sightings?platform=&since=&min_tier= public query
GET /api/discovery/stats live coverage: surfaces, tiers, watchers
POST /api/webhooks/:platform push: slack (HMAC), discord (ed25519), generic (?token=)
Nostr gossip watchers publish kind-30078 events to relays;
feed refresh backfills via SimplePool
- Oracle trust: sightings tier as
lead→corroborated(≥2 independent verified watchers agree) →disputed(conflicting reports, excluded from ranking + rewards). Weight scoring favors platform- authenticated pushes and previously-paid watchers (Anduin-style economic signal). - Grammar routing:
DECL_RE/CLAIM_RE/RECEIPT_RE/bind statements in sighted text flow into the samefeedrec:decl:*/hclaim:*/idbindrecords the old pollers produced — zero feed-merge changes. - Watcher rewards (
src/watchpay.ts): funded declarations paysighting_bpsentitlements to their sighting watchers + rep credit + ERC-8004-shaped feedback. Disputed sightings slash rep. - Legacy pollers default-off: bluesky/mastodon/lemmy/misskey/
peertube/hive/devto APIs are opt-in via
FEED_SOCIAL_POLL=1. Nostr relay polling, RSS (opt-in), forges, near-chain, and external bounty platforms still run — they're already decentralized or protocol-native. - Watcher side:
surf_watch/surf_watch_status/surf_declarein thewidespread_surfacesplugin — watch a read op, diff a local seen-set, post sightings signed with the agent's did:key.
Repository layout (monorepo)
Clone and use — no install required for any user-facing surface:
watcher-web/— openindex.htmlor deploy the static dir anywherewatcher-extension/— Chrome →chrome://extensions→ Load unpackedwidespread-discovery/—node src/cli.mjs(vendored deps invendor/, zero npm install; Node ≥ 20)relay/— already live atwss://widespread-relay.widespread.workers.dev
npm install is only needed to develop/test the bridge Worker itself
(vitest + wrangler):
widespread-bridge/ ← you are here (npm workspaces root)
├── src/ bridge Worker — markets, claims, coordinator,
│ feed, sightings ingest, MCP/A2A/POE endpoints
├── test/ vitest suite (270 tests) + e2e.live.test.ts
├── widespread-discovery/ `wsd` CLI/daemon — watcher identity, relay
│ └── src/ publish/verify, outbox, event log, gossip,
│ governance meta, serve/mcp (npm workspace)
├── watcher-web/ zero-install PWA — browser watcher, IndexedDB,
│ WebCrypto identity, service worker (static)
├── watcher-extension/ Chrome MV3 extension — credential broker,
│ session-scoped grants, in-context writes
├── scripts/ ops scripts (seed, register, keys)
├── docs/ discovery-protocol.md spec, OSS ledger, guides
├── marketplace/ MCP-registry listing assets
└── relay/ widespread-relay — our own Nostr relay
(nosflare fork, MIT; git-subtree import,
see relay/UPSTREAM.md for sync procedure)
Canonical sources rule: files under watcher-web/ and
watcher-extension/ marked // GENERATED are produced by
npm run sync from widespread-discovery/src/ — edit the source, run
sync, never hand-edit a generated copy (npm run sync:check gates CI).
relay/ deploys as the widespread-relay Cloudflare Worker (free tier,
D1+Durable Objects) at wss://widespread-relay.widespread.workers.dev —
verified kind-30078 retention, one pipe among the default relay set.
Standalone toolchain: cd relay && npm install && npm run deploy.
# zero-install usage (no npm install):
node widespread-discovery/src/cli.mjs --help # wsd CLI
# open watcher-web/index.html · load watcher-extension unpacked
# development only:
npm install # installs worker + widespread-discovery workspace
npm test # worker suite (vitest)
npm run test:all # worker + discovery suites
npm run wsd -- --help # or: npx wsd (workspace bin)
cd widespread-discovery && npm run vendor:build # rebuild vendor bundles after dep bumps
Deploy your own
npm install
npx wrangler login
npx wrangler kv namespace create CLAIMS # put the id in wrangler.jsonc
node scripts/gen-agent-key.mjs # optional: receipt write-back identity
npx wrangler secret put DG_AGENT_DID
npx wrangler secret put DG_AGENT_KEY_PKCS8_B64
# NEAR settlement: ops account + oracle keypair for escrow/release
npx wrangler secret put NEAR_OPS_SECRET_KEY
npx wrangler secret put ORACLE_SEED_HEX
npx wrangler secret put ORACLE_PUBKEY_HEX
npx wrangler deploy
Env vars are documented in wrangler.jsonc / .dev.vars.example. No keys
are committed — all credentials are Worker secrets only. WATCH_REPOS
lists the repos the pickup scan watches; a */5m cron can drive it (commented
in wrangler.jsonc) or the dashboard's /api/state polling does it
opportunistically.
Built with
- NEAR — the money rail:
createMarketlocks escrow,releasepays the winning claimant minus fee + platform cut, oracle verdicts gate settlement. Intents price conversion for USD-faced mirrors. - AI adjudication — Cloudflare Workers AI (
@cf/meta/llama-3.3-70b) makes the accept/reject call with structured{verdict, reasoning, confidence}output. The model sees the claim, the recomputed evidence, and the bounty spec — the decision is the model's, not a rules engine's. - Forge adapters (
src/forges/) — per-repo claim stream, evidence fetch, and receipt write-back behind one interface. delta-git (code.widespread.fyi) is the claim-log deployment: signed ops in a hash-chained op-log, public commit-diff endpoints, signeddid:keyagent envelopes. Any forge serving an append-only claim log plugs in the same way; forges without one take claims viaPOST /api/claimsand the bridge feed is the receipt. - Cloudflare Workers + KV — the whole service.
- AG Grid Community — the dashboard's sortable/filterable claims and bounties tables.
Stretch lanes
- Receipt write-back (shipped): verdicts land on the forge as signed
widespread/payoutcommit statuses — the audit trail runs both directions. - Intents settlement (planned): real cross-chain payout to a winner's bound EVM/Solana address without them touching NEAR — quotes run today, settlement flips on with Chain Signatures.
Demo video outline (2–4 min)
GET .../dg/oplogon the delta-git deployment — an agent's signed work claim just landed.- Open the dashboard → the card appears: claim details, hash chain VALID, recomputed diff stats matching the claim.
- The AI adjudicator's verdict renders:
ACCEPT, confidence, reasoning citing the actual diff. - The NEAR release fills in: market id, claimant account, nearblocks tx —
then open the contract's
getMarketshowingstatus: "paid". GET .../dg/status/<sha>— the receipt written back to the forge.- (Contrast) a junk claim →
REJECTwith the model's reasoning, no release.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
