Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Datasieve
Overview
Description from the maker (original English)
On-chain watches, web-page monitors, dead-man switches, cron, and agent coordination, paid via x402.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
DATASIEVE_PRIVATE_KEY_FILE,DATASIEVE_API_URL
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"datasieve": {
"command": "npx",
"args": [
"-y",
"datasieve-mcp"
],
"env": {
"DATASIEVE_PRIVATE_KEY_FILE": "your-value",
"DATASIEVE_API_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add datasieve --env DATASIEVE_PRIVATE_KEY_FILE=your-value --env DATASIEVE_API_URL=your-value -- npx -y datasieve-mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"datasieve": {
"command": "npx",
"args": [
"-y",
"datasieve-mcp"
],
"env": {
"DATASIEVE_PRIVATE_KEY_FILE": "your-value",
"DATASIEVE_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"datasieve": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"datasieve-mcp"
],
"env": {
"DATASIEVE_PRIVATE_KEY_FILE": "your-value",
"DATASIEVE_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
DATASIEVE_PRIVATE_KEY_FILEenvPath to a file holding a burner wallet key (0x…) with USDC on Base. Optional — free tools work without it.DATASIEVE_API_URLenvAPI base URL. Default https://api.datasieve.xyz; sandbox https://staging.datasieve.xyz (Base Sepolia, faucet USDC).
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account gitwormq, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32403 servers in this category
- Published to the registry more recently than 17% of the other 32403 servers in this category
- Basic checks equal to or better than 100% of the other 32403 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Datasieve safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.4.1) reached the registry 4 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, LickityClick
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
LickityClick
by lickity.click
Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.
Computer or cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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-mcpMost 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-skillInstalls 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:
- 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.
- Keep the key out of config files — point at a file instead:
echo '0xYOUR_BURNER_KEY' > ~/.datasieve/key.txt && chmod 600 ~/.datasieve/key.txtclaude 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
| tool | cost | what |
|---|---|---|
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_watch | tier price | one more period, trigger budget reset |
coord_workspace | $0.25 / 7d | multi-agent barriers + locks; every op after is free |
cron_next | $0.001 | parse a cron expression: next N run times, any timezone |
x402_ping | $0.001 | end-to-end payment stack self-test |
watch_status | free | heartbeat, triggers, expiry, up/down per dead-man switch |
drain_events | free | collect everything caught while you weren't running |
pause_watch / resume_watch | free | stop firing without deleting; backlog-free resume |
ping_heartbeat | free | keep your dead-man switch alive |
verify_receipt | free | check the Ed25519 receipt on any delivered event |
coord_barrier / coord_arrive / coord_lock / coord_release / coord_events | free | workspace ops |
delete_watch | free | cancel |
service_health | free | verify our scanner is alive before you pay |
payment_status | free | wallet 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.