mcp-red-web-utils
# mcp-red-web-utils
MCP server exposing 17 pay-per-call utilities (web reading, SEC/EDGAR, sanctions screening, insider + 13F holdings, UK/US case law, UK legislation, Base deployer intel, swap routing). Payments: x402, USDC on Base, per call $0.001-$0.005.
## Remote (no install)
POST streamable-HTTP MCP to `https://red-web-utils.agent-tools-x402.workers.dev/mcp` (`initialize`, `tools/list`, `tools/call`). Unpaid calls return a 402 x402/MPP challenge; retry with the payment credential.
## Stdio
```json
{
"mcpServers": {
"red-web-utils": {
"command": "npx",
"args": ["-y", "mcp-red-web-utils"],
"env": { "RED_UTILS_PRIVATE_KEY": "0x..." }
}
}
}
```
TDQS
Scored across 17 tools
Most tools have clearly distinct purposes: reader, metadata, rss, and links cover different web extraction tasks, and SEC/legal/crypto tools target different resources. The only mild overlaps are deployer vs deployer_score and caselaw_search vs caselaw_us, but jurisdiction and output differences make them separable.
Naming is readable but mixes bare nouns (reader, metadata, rss, links, newpairs, deployer, insiders, holdings) with prefixed or compound names (deployer_score, swap_route, edgar_search, sanctions_check, caselaw_fetch). There is no single predictable convention, though the domain prefixes help group related tools.
17 tools is in the borderline-heavy range, and the server spans several unrelated domains: web extraction, Base token scanning, SEC filings, sanctions, and legal research. The count is justifiable for a multi-purpose utility server but feels sprawling rather than tightly scoped.
Several domains have notable gaps: UK case law has search and fetch, but US case law only has search; legislation has search but no fetch; web utilities lack a general search tool. SEC and crypto coverage is reasonable, but agents will hit dead ends in the legal and web-search workflows.