The sh.fetcher.twitter/mcp server exposes 15 Twitter / X endpoints for fetching data. Usage is billed on a per-call basis in USDC via x402. The server is available under the sh.fetcher.twitter/mcp identifier and provides 6 tools as part of its interface.
🛠️ Key Features
- 15 Twitter / X endpoints
- Per-call billing in USDC via
x402 - 6 tools available
🚀 Use Cases
- Fetching from Twitter / X using a fixed set of provided endpoints
- Integrating Twitter / X retrieval into MCP-based workflows
⚡ Developer Benefits
- Straightforward endpoint-based access (15 endpoints)
- Predictable cost model: pay per call in USDC via
x402
⚠️ Limitations
- Limited to the provided Twitter / X endpoints (15 total)
- Requires USDC billing via
x402per call