On-chain watches, web-page monitors, dead-man switches, cron, and agent coordination, paid via x402.
On-chain watches, web-page monitors, dead-man switches, cron, and agent coordination, paid via x402. That is what the datasieve mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
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
The server publishes 12 tools. What each one is for:
create_watch — $0.10 (standard/7d) · $0.25 (composite/7d, ≤5 conditions) · $0.35 (standard30/30d) · $0.85 (composite30/30d)renew_watch — tier pricecoord_workspace — $0.25 / 7dcron_next — $0.001x402_ping — $0.001watch_status — freedrain_events — freeping_heartbeat — freeverify_receipt — freedelete_watch — freeservice_health — freepayment_status — freeConfiguration is passed through the environment: DATASIEVE_PRIVATE_KEY, DATASIEVE_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as datasieve-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Datasieve's toolset — create_watch, renew_watch, coord_workspace and 9 more — is a fair guide to whether it matches your workflow. It is maintained by gitwormq; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Datasieve's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| create_watch | $0.10 (standard/7d) · $0.25 (composite/7d, ≤5 conditions) · $0.35 (standard30/30d) · $0.85 (composite30/30d) |
| renew_watch | tier price |
| coord_workspace | $0.25 / 7d |
| cron_next | $0.001 |
| x402_ping | $0.001 |
| watch_status | free |
| drain_events | free |
| ping_heartbeat | free |
| verify_receipt | free |
| delete_watch | free |
| service_health | free |
| payment_status | free |
{
"mcpServers": {
"datasieve": {
"command": "npx",
"args": ["-y", "datasieve-mcp"],
"env": {
"DATASIEVE_PRIVATE_KEY": "your-value",
"DATASIEVE_API_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| DATASIEVE_PRIVATE_KEY | Credential the server authenticates with. | Yes |
| DATASIEVE_API_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.