io.github.SirPaul-code/eviduct
Eviduct Trust Firewall
Is the Eviduct Trust Firewall MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
MCP Trust Firewall: tenant-approved tools, schema-pinned public reads. Authorization is required.
needs auth probed 2026-11-14 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"Protected gateway requires a tenant-issued client token or OAuth authorization"}- Endpoint
- https://eviduct-mvp.onrender.com/mcp/gateway (streamable-http)
- Host
- eviduct-mvp.onrender.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://eviduct-mvp.onrender.com/mcp/gateway registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server eviduct-mvp.onrender.com, PKCE S256, grants authorization_code, refresh_token.
Scopes eviduct:read.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://eviduct-mvp.onrender.com/
- Registry
- active, updated 2026-11-13 · registry entry
- Changes
- 3 recorded, reachable in 3 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention firewall or trust.
- ai.agentrapay/agentra · needs auth
- AIﾉアカリ☆ Agent Trust Receipt ai.ai-akari/agent-trust-receipt · paid (402)
- Divinci AI ai.divinci/divinci · needs auth
- DJZS Trust MCP ai.djzs/trust-mcp · alive
- ENYAL by Greenland AI ai.enyal/enyal · alive
- ai.kaiv/dependency-trust · alive
- Modulos AI Governance Platform ai.modulos/demo-booking · alive
- Nordax AI Entity Network ai.nordax/mcp · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-14 10:52 | needs auth | ||||
| 2026-11-13 11:32 | alive | 478 ms | 6 | 1.2k | 637 |
| 2026-11-11 11:26 | alive | 1.0 s | 3 | 560 | 287 |
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 answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.