mcp-red-web-utils
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RED_UTILS_PRIVATE_KEY | Yes | Private key (e.g. 0x...) used by the stdio server for x402/USDC payments on Base. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| readerA | Read any web page as clean text (paid per call, USDC on Base via x402) |
| metadataB | Extract title/description/OG metadata from a URL (paid per call, USDC on Base via x402) |
| rssA | Parse an RSS/Atom feed into JSON (paid per call, USDC on Base via x402) |
| linksB | Extract all links from a web page (paid per call, USDC on Base via x402) |
| newpairsB | New Base token pairs from the internal scanner (paid per call, USDC on Base via x402) |
| deployerC | Base token deployer profile (paid per call, USDC on Base via x402) |
| deployer_scoreC | Base deployer reputation score (unique dataset) (paid per call, USDC on Base via x402) |
| swap_routeC | 0x swap quote across chains (paid per call, USDC on Base via x402) |
| edgar_searchB | Search SEC EDGAR full-text filings (paid per call, USDC on Base via x402) |
| edgar_companyB | SEC company facts by ticker or CIK (paid per call, USDC on Base via x402) |
| sanctions_checkC | OFAC + UK OFSI sanctions screening (paid per call, USDC on Base via x402) |
| insidersB | Latest SEC Form 4 insider transactions (paid per call, USDC on Base via x402) |
| holdingsB | Institutional 13F holdings by CIK or manager name (paid per call, USDC on Base via x402) |
| caselaw_searchB | Search UK case law (National Archives) (paid per call, USDC on Base via x402) |
| caselaw_fetchB | Fetch a UK judgment by path (paid per call, USDC on Base via x402) |
| legislation_searchB | Search UK legislation (legislation.gov.uk) (paid per call, USDC on Base via x402) |
| caselaw_usB | Search US case law (CourtListener) (paid per call, USDC on Base via x402) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.