sh.fetcher/mcp (MCP Server)
The sh.fetcher/mcp Model Context Protocol (MCP) server provides access to 111 web-data endpoints across 11 services. It is described as pay per call in USDC via x402, indicating request-based usage and a USDC billing model per endpoint call.
🛠️ Key Features
- 111 web-data endpoints
- 11 services aggregated under one server
- Per-call billing denominated in USDC via x402
🚀 Use Cases
- Fetching web data from one of 11 services
- Integrations that require calling specific web-data endpoints
⚡ Developer Benefits
- Clear endpoint scope: 111 endpoints across 11 services
- Usage model aligned to pay-per-call in USDC through x402
⚠️ Limitations
- Limited scope to the listed web-data endpoints/services
- Cost depends on call frequency (pay per call in USDC via x402)