Datasieve MCP server
io.github.gitwormq/datasieve·v0.4.1On-chain watches, web-page monitors, dead-man switches, cron, and agent coordination, paid via x402.
0 stars46 downloads/wk
Reviews
Write oneNobody has reviewed Datasieve yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Datasieve tools (19, 3 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
coord_arriveReport that this part is done. Pass the arriveUrl from coord_barrier plus a part name and
coord_barrierBARRIER: "wake me when all N of my sub-agents finish." Returns an arriveUrl — hand it to
coord_eventsCollect barrier releases/partials that happened while nothing of yours was running.
coord_lockLOCK: "only one agent does this irreversible thing." Returns a leaseId, or 409 with who
coord_releasecoord_workspacewrite actionBuy a coordination workspace ($0.25 / 7 days, 1000 ops) — the only x402 seller of
create_watchwrite actionBuy a standing watch from DataSieve (…). standard = $0.10/7d, 1 condition, 50 triggers;
cron_nextNext N run times for a cron expression in any IANA timezone, plus seconds-until-next.
delete_watchwrite actiondrain_eventsCollect everything the watch caught — works with zero infrastructure (the mailbox pattern).
pause_watchStop a watch firing (chain, web, heartbeat, schedule) without deleting it. The expiry
payment_statusCheck whether a buying key is configured and whether it can afford a watch. Reports the
ping_heartbeatKeep a dead-man switch alive. Pass the pingUrl from create_watch (or a watchId whose ping
renew_watchExtends the watch one more period (7 days, or 30 on the *30 tiers) at its tier price and
resume_watchBacklog-free resume: heartbeat deadlines restart from now and schedules jump to their next
service_healthScanner cursor lag vs chain head — verify the watcher is alive before you buy.
verify_receiptEvery DataSieve event carries receipt {alg, keyId, statement, sig} — an Ed25519 attestation
watch_statusState, heartbeat lastCheckedAt, triggersUsed/cap, expiry, delivery stats, and for dead-man
x402_pingThe cheapest possible real x402 purchase: proves this wallet + client can pay a production
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan4 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 76 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Datasieve compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 80% of 4,460 AI and agents servers
- Tools
- 19
- the typical AI and agents server has 6
- Tools that change things
- 16%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 46
- more than 38% of 1,538 AI and agents servers with a package
What its tools let an agent do: 15 read · 1 create · 2 change · 1 delete
Install Datasieve in Claude Code, Cursor or VS Code
Runs npx -y datasieve-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add datasieve -- npx -y datasieve-mcp
What the publisher says
From the Datasieve repository's README, as published. We do not edit it. Read it on GitHub
datasieve-mcp
MCP server for DataSieve — standing infrastructure for AI agents, paid over x402. On-chain conditions on Base (wallet activity, whale transfers, price crossings, new pools), url-change web monitoring (CSS selector / regex scoped), dead-man switches for your own agents (your agent pings a URL; silence fires the alert), cron schedules (fire a webhook every N seconds, at a time, or on a cron expression), and multi-agent coordination (barriers + locks). Every event carries a signed Ed25519 observation receipt. No account, no API key: one gasless USDC payment per watch, signed locally — your key never leaves your machine. Failed calls are never billed.
Setup — no key required to start
claude mcp add datasieve -- npx -y datasieve-mcpMost tools work with no wallet at all — check our scanner's health, read watch status, drain events, ping dead-man switches, pause/resume, verify receipts, cancel watches. Only the buying tools spend money.
The Claude Code skill (recommended)
npx -y datasieve-mcp --install-skillInstalls a skill into ~/.claude/skills/datasieve/ that teaches Claude when to reach for standing infrastructure proactively: arm a dead-man switch before long autonomous work, schedule wake-ups, watch pages and wallets, coordinate sub-agents.
When you want to buy
x402 means paying is a signature, so purchases need a key. Two rules:
never your main wallet. Payments are gasless (EIP-3009), so it needs no ETH.
- Use a dedicated burner wallet holding a few dollars of USDC on Base —
- Keep the key out of config files — point at a file instead:
echo '0xYOUR_BURNER_KEY' > ~/.datasieve/key.txt && chmod 600 ~/.datasieve/key.txt
claude mcp add datasieve -e DATASIEVE_PRIVATE_KEY_FILE=$HOME/.datasieve/key.txt -- npx -y datasieve-mcp(DATASIEVEPRIVATEKEY=0x... inline also works if you prefer.)
The key never leaves the process: each payment is a signature authorizing exactly the route price — one at a time, nothing standing. Run payment_status to see the wallet, its balance, and prices before spending anything.
Rehearse for free
claude mcp add datasieve-sandbox -e DATASIEVE_API_URL=https://staging.datasieve.xyz \
-e DATASIEVE_PRIVATE_KEY_FILE=$HOME/.datasieve/key.txt -- npx -y datasieve-mcpSame API, Base Sepolia, faucet USDC. Sandbox watches last 1 hour.
Tools
Watch ids and secrets are remembered in ~/.datasieve/watches.json (mode 600), so follow-up calls only need the watch id — the persistent memory your ephemeral agent lacks.
Nothing above is checked by us. What we check is on the safety report.
Datasieve: common questions
- Is Datasieve MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Datasieve safety report
- How do I install Datasieve?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Datasieve need an API key?
- No secret keys are declared. It reads 2 settings from the environment.
- Is Datasieve maintained?
- The last commit was 115 days ago (2026-07-12). The latest release is v0.4.1.
- What can I use instead of Datasieve?
- Servers from other publishers that do the same job: Robin: AI-Powered Dark Web OSINT MCP server, Charlotte MCP server and agent-device MCP server.
- How does Datasieve compare with other AI and agents MCP servers?
- safety score 88/100 (higher than 80% of 4,460 AI and agents servers); tools 19 (the typical AI and agents server has 6); tools that change things 16% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Datasieve
Same job from other publishers: the closest match first, then the best rated.
- Robin: AI-Powered Dark Web OSINTDark web OSINT over Tor: search onion engines, scrape pages, report with your own model.not reviewedEstablishedA
- CharlotteRenders web pages into structured, agent-readable representations using headless Chromium.not reviewedEstablishedA
- agent-deviceOpen source device layer for AI agents: control mobile, web, TV, and desktop apps over MCPnot reviewedWidely usedA
- You.com Web Access & AIWeb search, AI agent, and content extraction via You.com APIsnot reviewedEstablishedA
- PDFAgentic RAG over one PDF or a whole folder: hybrid search, selective page reads, tables, OCR.not reviewedEstablishedA