mcpField
D
datasieve

datasieve

Local
datasieve.xyzAI & Agents0Updated 16w ago
RepositoryVisit website

About datasieve

datasieve is an MCP server providing persistent monitoring and coordination infrastructure for AI agents. It combines on-chain and webpage watches, schedules, dead-man switches, and agent coordination, with paid watch creation handled through x402.

Key features

  1. 01On-chain condition watches
  2. 02Webpage change monitoring
  3. 03Agent dead-man switches
  4. 04Cron and timed webhooks
  5. 05Multi-agent barriers and locks
  6. 06Signed event receipts

Use cases

  1. 01Watch wallets, transfers, prices, or new pools
  2. 02Detect changes in selected webpage content
  3. 03Alert when an agent stops checking in
  4. 04Schedule agent wake-ups or coordinate sub-agents

MCP support

Exposes monitoring, scheduling, coordination, and watch-management tools to MCP clients. Some operations are free, while watch purchases use x402 payments.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "gitwormq-datasieve": {
      "command": "npx",
      "args": [
        "-y",
        "datasieve-mcp"
      ],
      "env": {
        "DATASIEVE_PRIVATE_KEY_FILE": "<DATASIEVE_PRIVATE_KEY_FILE>",
        "DATASIEVE_API_URL": "<DATASIEVE_API_URL>"
      }
    }
  }
}
Run commandnpx -y datasieve-mcp
Environment variables to set
DATASIEVE_PRIVATE_KEY_FILESecretPath to a file holding a burner wallet key (0x…) with USDC on Base. Optional — free tools work without it.
DATASIEVE_API_URLAPI base URL. Default https://api.datasieve.xyz; sandbox https://staging.datasieve.xyz (Base Sepolia, faucet USDC).

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmdatasieve-mcp0.4.1

Tools

19

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
tierenumNostandard | composite | standard30 | composite30
conditionsarrayYes
webhookUrlstringNo

Details

From the project 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

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.