English Français العربية

io.github.gitwormq/datasieve

Official registry AI and agents

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package datasieve-mcp
Claude Code 
claude mcp add datasieve -e 'DATASIEVE_PRIVATE_KEY_FILE=<DATASIEVE_PRIVATE_KEY_FILE>' -e 'DATASIEVE_API_URL=<DATASIEVE_API_URL>' -- npx -y datasieve-mcp@0.4.1
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "datasieve": {
            "command": "npx",
            "args": [
                "-y",
                "datasieve-mcp@0.4.1"
            ],
            "env": {
                "DATASIEVE_PRIVATE_KEY_FILE": "<DATASIEVE_PRIVATE_KEY_FILE>",
                "DATASIEVE_API_URL": "<DATASIEVE_API_URL>"
            }
        }
    }
}

Environment variables

  • DATASIEVE_PRIVATE_KEY_FILE Path to a file holding a burner wallet key (0x…) with USDC on Base. Optional — free tools work without it.
  • DATASIEVE_API_URL API base URL. Default https://api.datasieve.xyz; sandbox https://staging.datasieve.xyz (Base Sepolia, faucet USDC).

Documentation

From the project's README on GitHub, refreshed weekly. Links open 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-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.

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

(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
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.

Frequently asked questions

What is io.github.gitwormq/datasieve?

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

How do I install io.github.gitwormq/datasieve?

It runs on your machine. In Claude Code: claude mcp add datasieve -e 'DATASIEVE_PRIVATE_KEY_FILE=<DATASIEVE_PRIVATE_KEY_FILE>' -e 'DATASIEVE_API_URL=<DATASIEVE_API_URL>' -- npx -y datasieve-mcp@0.4.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.gitwormq/datasieve need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.gitwormq/datasieve open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.gitwormq/datasieve?

It is published by gitwormq. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.