io.github.Tolomere21/latam-mcp
io.github.Tolomere21/latam-mcp
Is the io.github.Tolomere21/latam-mcp MCP server down? Yes. It has given no valid answer since 2026-10-20: not found.
Peruvian public data — SUNAT RUC, BCRP FX, SEACE tenders. Sourced from official open-data.
not found down since 2026-10-20 · probed 2026-11-15 · unchanged since 2026-10-27
npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /
- Run it
- npx -y @latam-mcp/mcp@0.1.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/Tolomere21/latam-mcp
- Website
- https://latam-mcp.com
- Registry
- active, updated 2026-04-22 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Elasticsearch io.github.TocharianOU/elasticsearch · crashed on start
- Kibana io.github.TocharianOU/kibana · crashed on start
- Tokenectomy Razor io.github.Tokenectomy-Labs/razor · needs network
- TollWire Evidence io.github.TollWire/evidence-mcp · alive
- io.github.TomasLucasUTN/godot-mcp-bridge · alive
- Story Mapper io.github.TomAtAP/storymapper · crashed on start
- io.github.TomD4vs/prumo · crashed on start
- Archprint io.github.Tommkruix/archprint · alive
Servers that mention latam.
- Emisso Connect ai.emisso/connect · needs auth
- LATAM Logistics (Envia: rates, labels, tracking, cancel across MX/CO/CL/BR/GT/AR/US/CA/ES) app.wishpool/latam-logistics-mcp · no DNS
- Tuki — Travel Marketplace (Chile y Latinoamérica) cl.tuki/travel-mcp · alive
- Plexa com.joinplexa/plexa · alive
- com.ruzora/ruzora · alive
- RESET Verifica com.resetparatodos/verifica · alive
- Tu Lugar com.tulugar/tulugar · alive
- dev.latamref/reference-data · 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-20, 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.