Datasieve

io.github.gitwormqPublished by GitHub account gitwormqv0.4.1Updated Oct 24, 2026

On-chain watches, web-page monitors, dead-man switches, cron, and agent coordination, paid via x402.

VerifiedSTDIODesktop onlyProductivity & WorkflowWeb Search & ScrapingFinance

Overview

AI-generated overview

Lets an assistant buy and manage standing watches on Base: on-chain conditions, web-page changes, cron schedules, dead-man switches, and agent coordination.

What you can do
DataSieve provides standing infrastructure for agents. Paid tools create and renew watches for on-chain conditions on Base (wallet activity, whale transfers, price crossings, new pools), URL-change monitoring scoped by CSS selector or regex, dead-man switches, and cron schedules that fire webhooks. A coordination workspace offers barriers and locks for multiple agents. Free tools check service health, read watch status, drain collected events, ping heartbeats, pause or resume, verify Ed25519 observation receipts, and cancel watches.
When to use it
Use it when an assistant needs to keep watching something after it stops running: monitoring a wallet or page, scheduling recurring wake-ups, arming a dead-man switch before long autonomous work, or coordinating several sub-agents. Free tools work without a wallet, so it can be tried before any purchase.
Requirements
Runs locally over stdio via the npm package datasieve-mcp (Node.js/npx). No account or API key. Buying tools need a funded burner wallet key on Base, supplied through DATASIEVE_PRIVATE_KEY_FILE (or an inline key variable). DATASIEVE_API_URL selects the API base, defaulting to the production endpoint; a sandbox endpoint on Base Sepolia with faucet USDC is available. Network access required.
Before you install
Buying tools spend real USDC on Base: create_watch, renew_watch, coord_workspace, cron_next, and x402_ping have listed prices. Use a dedicated burner wallet, never a main wallet, and keep the key in a file referenced by DATASIEVE_PRIVATE_KEY_FILE rather than in config. Watches fire webhooks and can send data to third-party endpoints. Watch ids and secrets are stored locally in a watches file.

Installation

In SourceWeft

  1. Open Datasieve in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

sh
claude mcp add datasieve -- npx -y datasieve-mcp

Most 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)

sh
npx -y datasieve-mcp --install-skill

Installs 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:

  1. Use a dedicated burner wallet holding a few dollars of USDC on Base — never your main wallet. Payments are gasless (EIP-3009), so it needs no ETH.
  2. Keep the key out of config files — point at a file instead:
sh
echo '0xYOUR_BURNER_KEY' > ~/.datasieve/key.txt && chmod 600 ~/.datasieve/key.txtclaude mcp add datasieve -e DATASIEVE_PRIVATE_KEY_FILE=$HOME/.datasieve/key.txt -- npx -y datasieve-mcp

(DATASIEVE_PRIVATE_KEY=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

sh
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-mcp

Same API, Base Sepolia, faucet USDC. Sandbox watches last 1 hour.

Tools

toolcostwhat
create_watch$0.10 (standard/7d) · $0.25 (composite/7d, ≤5 conditions) · $0.35 (standard30/30d) · $0.85 (composite30/30d)buy a watch; returns id, secret, ping URLs
renew_watchtier priceone more period, trigger budget reset
coord_workspace$0.25 / 7dmulti-agent barriers + locks; every op after is free
cron_next$0.001parse a cron expression: next N run times, any timezone
x402_ping$0.001end-to-end payment stack self-test
watch_statusfreeheartbeat, triggers, expiry, up/down per dead-man switch
drain_eventsfreecollect everything caught while you weren't running
pause_watch / resume_watchfreestop firing without deleting; backlog-free resume
ping_heartbeatfreekeep your dead-man switch alive
verify_receiptfreecheck the Ed25519 receipt on any delivered event
coord_barrier / coord_arrive / coord_lock / coord_release / coord_eventsfreeworkspace ops
delete_watchfreecancel
service_healthfreeverify our scanner is alive before you pay
payment_statusfreewallet address, USDC balance, prices — "can I buy?"

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.

Source: README.md at commit 370a6ec

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts