Gateway is listed as active in the registry but did not answer our last check. 22 installs a week from npm.
Governed MCP gateway: approval gates, signed audit receipts, and cost control for agent tool calls.
Gateway does not always answer
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.
claude mcp add gateway --transport http https://api.blacklake.systems/mcp{
"mcpServers": {
"gateway": {
"url": "https://api.blacklake.systems/mcp"
}
}
}[mcp_servers.gateway]
url = "https://api.blacklake.systems/mcp"{
"mcpServers": {
"gateway": {
"url": "https://api.blacklake.systems/mcp"
}
}
}{
"mcpServers": {
"gateway": {
"url": "https://api.blacklake.systems/mcp"
}
}
}Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.blacklake.systems/mcp | streamable-http | answering | 405 ms | 5 min ago |
Alternatives to Gateway
same job, measured the same waySigned receipts and Cedar policies for AI agent tool calls. Claude Code hooks, MCP gateway.
Governed MCP front door to FLOCORE; write calls need human approval and signed receipts.
Policy-based governance for AI agent tool calls. YAML policy, approval gates, audit logging.
Governed AI workflows with human approval gates and audit trails for Claude and MCP clients.
Governed USDC wallet for AI agents — policy gates, spending caps, and Ed25519-signed receipts.
Financial governance for AI agents — spend gates and audit trail exposed as MCP tools.
MCP gateway with runtime security policy, tool-call-level control, and audit of agent actions.
A local receipt and approval gate for AI agent sessions. The agent can act, but it cannot sign.
Gateway — questions
Answers built from our own checks of this server.