The sh.fetcher.twitter/mcp server provides access to 15 Twitter/X endpoints. It is described as charging per call in USDC via x402, indicating a usage-based billing model tied to individual endpoint invocations. The server is intended to act as a fetcher for Twitter/X-related data via its exposed endpoints.
🛠️ Key Features
- 15 Twitter / X endpoints
- Pay per call billing
- Payments in USDC
- Uses x402 for call billing
🚀 Use Cases
- Retrieve data from specific Twitter/X endpoints
- Call one or more of the 15 available endpoints as needed
⚡ Developer Benefits
- Clear endpoint scope: 15 Twitter/X endpoints
- Usage-aligned cost model: pay per call in USDC
⚠️ Limitations
- Limited to the listed 15 Twitter/X endpoints
- Costs per call apply, paid in USDC via x402