io.github.Asthanaji05/pokeapi-mcp-server
pokemon-mcp-server
Is the io.github.Asthanaji05/pokeapi-mcp-server MCP server down? No. It is up and needs network, probed 2026-10-30.
Empower your AI with Pokédex powers! Fetch and explore Pokémon data seamlessly via PokeAPI.
needs network probed 2026-11-15 · unchanged since 2026-10-30
MCP error -32603: Failed to fetch tools: getaddrinfo EAI_AGAIN pokemon-mcp-server-vs8m.onrender.com ⚠️ WARNING: HTTP server at https://pokemon-mcp-server-vs8m.
- Run it
- npx -y pokeapi-mcp-server@1.12.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- pokemon-mcp-server 1.0.0
- Capabilities
- tools
- Repository
- https://github.com/Asthanaji05/MCP_Pokemon
- Registry
- active, updated 2025-11-02 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.Askrion/stateark · crashed on start
- Assistant Mail MCP io.github.AssistantMail/assistantmail-mcp · alive
- AsterMind MCP io.github.AsterMindAI/astermind-mcp · alive
- io.github.Asthanaji05/openapi-mcp · needs args
- io.github.Astralchemist/matchstick · alive
- Chrome DevTools MCP io.github.Async23/chrome-devtools-mcp · alive
- io.github.Ataraxy-Labs/sem · crashed on start
- AtlaSent MCP Server io.github.AtlaSent/mcp-server · alive
Servers that mention pokeapi or seamlessly or empower.
- io.github.cyanheads/pokeapi-mcp-server · alive
- io.github.mrfentmen/pokeapi-mcp · alive
- ai.smithery/Hint-Services-obsidian-github-mcp · not found
- ai.smithery/Kryptoskatt-mcp-server · not found
- ai.smithery/ProfessionalWiki-mediawiki-mcp-server · not found
- ai.waystation/airtable · paid (402)
- ai.waystation/monday · paid (402)
- ai.smithery/feeefapp-mcp · not found
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
- The server tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.