English Français العربية

io.github.gitwormq/datasieve

Registre officiel IA et agents

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

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

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
Configuration JSON (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>"
            }
        }
    }
}

Variables d'environnement

  • 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

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent 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.

Questions fréquentes

Qu'est-ce que io.github.gitwormq/datasieve ?

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

Comment installer io.github.gitwormq/datasieve ?

Il s'exécute sur votre machine. Dans 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. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.gitwormq/datasieve ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.gitwormq/datasieve est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.gitwormq/datasieve ?

Il est publié par gitwormq. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.