io.github.checkra1neth/xbird
io.github.checkra1neth/xbird
Is the io.github.checkra1neth/xbird MCP server down? Yes. It has given no valid answer since 2026-10-17: not found.
Twitter/X MCP server — 30 tools with x402 micropayments. Runs locally from your IP.
not found down since 2026-10-17 · probed 2026-11-14 · unchanged since 2026-10-31
npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo
- Run it
- npx -y xbird-mcp@0.1.4 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/checkra1neth/xbird
- Registry
- active, updated 2026-02-11 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Resolve402 io.github.charleskremer-hub/resolve402 · alive
- io.github.charliemtnez/ghost-inspector-mcp · alive
- io.github.charo360/statecli · crashed on start
- io.github.chaytanc/reality-next-door-walk · alive
- io.github.cheedli/doubleoh-mcp · needs env
- io.github.chefcohen/corroborate-mcp · alive
- io.github.chelslava/md-semantic-search · crashed on start
- io.github.chemic/indiebob · alive
Servers that mention micropayments or locally.
- Lattiq x402 Trading Signals ai.lattiq/x402-trading-signals · no DNS
- nullpath Agent Marketplace com.nullpath/marketplace · timeout
- com.verifyum/mcp · alive
- com.vithanco/vgraph-mcp · not MCP
- dev.journalize/journalize · alive
- Mark dev.tatastu/proof · alive
- x711 — Universal Agent Gas Station io.github.0580iris-lang/x711-gas-station · alive
- io.github.AlexanderLawson17/revettr-mcp · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-17, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.