io.github.Realbizdigital/barzelvault-mcp
BarzelVault: AI Action Authorization Firewall
Is the BarzelVault MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-10.
Authorize AI agent tool calls before they run: policy-as-code, human approval, signed receipts.
needs auth probed 2026-11-15 · unchanged since 2026-11-10 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32603,"message":"Bearer token required"},"id":null}- Endpoint
- https://barzelvault-mcp.mcpize.run/mcp (streamable-http)
- Host
- barzelvault-mcp.mcpize.run
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://barzelvault-mcp.mcpize.run/mcp 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 barzelvault-mcp.mcpize.run, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp:tools mcp:resources mcp:prompts.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://mcpize.com/mcp/barzelvault-mcp
- Registry
- active, updated 2026-11-09 · registry entry
Compare this server with others.
More servers
Servers that mention authorization or firewall.
- InfraPulse ai.infrapulse/infrapulse · rejects our protocol version
- by.authorized/brands · alive
- Healthcare Admin — Authorization Review — Northgate Advisors (2bd7f518) com.a2awire/benchmark-authorization-review-2026-09-16-2bd7f518 · alive
- Alkemata Knowledge Gateway com.alkemata/public-knowledge · alive
- Enshape com.enshapeapp/enshape · needs auth
- Agent Observatory Digital Twin com.virus-alert/agent-observatory · alive
- Enforcer dev.instruxi.enforcer/v3 · needs auth
- dk.humanified/values-firewall · server error
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.