io.github.krishnaGauss/geo-shield
GEO Shield
Is the GEO Shield MCP server down? It gave no valid answer in the probe of 2026-11-13: crashed on start. One failed probe is not an outage.
Detects hidden AI prompt injection, AI recommendation poisoning, sneaky redirects and hidden spam.
crashed on start no valid answer since 2026-11-13 · probed 2026-11-15 · unchanged since 2026-11-13
MCP error -32000: Connection closed
{"level":60,"time":1794559886567,"pid":14,"hostname":"49f203b6b4cc","name":"geo-shield-mcp","err":{"type":"Error","message":- Run it
- npx -y geo-shield-mcp@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/krishnaGauss/MCP_WebSafe
- Registry
- active, updated 2026-11-12 · 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.krampslaag/uniteddepin · alive
- ZenMoney io.github.krax1337/mcp-server-zenmoney · alive
- io.github.krimto-labs/krimto · crashed on start
- MCP API Translator io.github.krishgok/mcp-api-translator · alive
- io.github.krishnabhat/indian-food-nutrition-mcp · crashed on start
- io.github.kriskraw80/mychart · alive
- io.github.kristoferbc/x402-funding · alive
- Apple Health MCP Server io.github.krumjahn/health-analyzer-mcp · alive
Servers that mention shield.
- app.decibelshield/decibel-shield · alive
- app.vercel.triageshield/triageshield · alive
- com.clauxel.tracepiishield/tracepiishield-mcp · no DNS
- com.craftedtrust/mcp-shield · alive
- com.edgethirteen.www/triageshield · not found
- MandateShield AI Payment Evidence com.mandateshield/payment-authority · alive
- dev.horizonshield/horizon-shield · alive
- Execute adversarial-prompt-shield-mcp io.github.Evozim/adversarial-prompt-shield-mcp · paid (402)
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 package did not start as an MCP server at its probe on 2026-11-13. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- The process exited on start before it answered initialize. The error output is above.