io.github.eddyflores100-lang/uta-shield-remote
uta-shield Remote (Barter-enabled)
Is the uta-shield Remote (Barter-enabled) MCP server down? Yes. It has given no valid answer since 2026-10-28: not found (HTTP 405).
Remote MCP firewall with barter protocol: identity, threat-intel, IoC lookup.
not found down since 2026-10-28 · probed 2026-11-15 · unchanged since 2026-10-30 · HTTP 405
Streamable HTTP error: Error POSTing to endpoint: <html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></ce
- Endpoint
- https://wall.utalabs.tech/mcp (streamable-http)
- Host
- wall.utalabs.tech
- Repository
- https://github.com/eddyflores100-lang/uta-shield
- Website
- https://wall.utalabs.tech
- Registry
- active, updated 2026-10-27 · registry entry
Compare this server with others.
More servers
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
- No valid answer since 2026-10-28, in every probe since then.
- The endpoint answers HTTP 405. 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.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.