Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/gitwormq/datasieve-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/gitwormq/datasieve-mcp/datasieve)<a href="https://agentmods.dev/mcp/gitwormq/datasieve-mcp/datasieve"><img src="https://agentmods.dev/badge/mcp/gitwormq/datasieve-mcp/datasieve/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/gitwormq/datasieve-mcp/datasieve"><img src="https://agentmods.dev/badge/mcp/gitwormq/datasieve-mcp/datasieve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
datasieve scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"datasieve": {
"command": "npx",
"args": [
"-y",
"datasieve-mcp"
],
"env": {
"DATASIEVE_PRIVATE_KEY_FILE": "",
"DATASIEVE_API_URL": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 13 lines scan A 20873981c374
datasieve is an MCP server published in the GitHub repository gitwormq/datasieve-mcp (0 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
x402-seller
Rug-check & launch radar for trading agents: composite honeypot score, EVM+Solana, keyless x402. Remote server at x402-seller-m8nx.onrender.com.
whale-data-mcp
Signed settled outcomes (Polymarket, sports, Kalshi) + whale signals as agent tools, paid via x402. Runs locally from the @predge/whale-data-mcp npm package. Needs 7 environment variables to run.
agentservices
52 paid x402 API endpoints for AI agents — crypto, data, DeFi, market intelligence. Remote server at agentservices.to.
x402-bazaar-mcp
Check, then act, on Base and NEAR: token-safety gates, then swaps at the best price — over x402. Runs locally from the x402-bazaar-mcp npm package. Needs 3 environment variables to run.
mainstreet
Reputation oracle for AI agents on Base: SAFE/CAUTION/BLOCK + 0-100 score before you pay. x402+MCP. Remote server at avisradar-production.up.railway.app.
base-transaction-decoder
Decode any Base tx: plain English, strict JSON, risk flags, no LLM. 50 free/day per IP, then $0.02. Remote server at api.0200project.com.