Log inSubmit server
Datasieve logo

Datasieve

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

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Datasieve

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "datasieve": {
      "command": "npx",
      "args": [
        "-y",
        "datasieve-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 19 tools correctly (6d ago).

Overview

Tools19

What Datasieve lets your agent do. Expand a tool for its parameters.

Verified live~2.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

What it can do

From the 19 tools this server returned when we ran it.

Can delete or modify data · 2Handles credentials · 2Makes network requests · 1Read-only tools · 17
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age98 days
Maintainers1

Observed 2026-10-18 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7h ago via OSV.dev · datasieve-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads217Package downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed19Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

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

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

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

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

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Datasieve

datasieve is an MCP server that provides standing infrastructure for AI agents, including on-chain watches on Base, URL-change monitoring, dead-man switches, cron webhooks, and multi-agent coordination. It uses x402 payments, supports gasless USDC signing, and attaches signed Ed25519 observation receipts to events. Most management tools require no wallet.

datasieve can watch Base wallet activity, whale transfers, price crossings, and new pools; monitor web-page changes using scoped CSS selectors or regular expressions; run dead-man switches; schedule cron webhooks; and coordinate agents with barriers and locks.

Buying tools use x402: one gasless USDC payment is signed locally for the selected route. A dedicated burner wallet with USDC on Base is recommended, while most status, monitoring, coordination, and management tools work without a wallet. Failed calls are not billed.

Install datasieve with `claude mcp add datasieve -- npx -y datasieve-mcp`. No key is required to start. For purchases, provide a dedicated burner key through `DATASIEVE_PRIVATE_KEY_FILE` or `DATASIEVE_PRIVATE_KEY`; the server stores watch IDs and secrets in `~/.datasieve/watches.json` with mode 600.

Related MCP servers

All in Monitoring All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDatasieve AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/datasieve?style=directory)](https://allmcps.com/mcp/datasieve)
HTML Embed
<a href="https://allmcps.com/mcp/datasieve"><img src="https://allmcps.com/api/badge/datasieve?style=directory" alt="Datasieve on AllMCPs" /></a>