Gateway runs on your own machine — the client starts it, so there is no endpoint to ping. 72 installs a week from npm. Last commit 26 Oct 2026.
MCP auth gateway: verify agent identity, enforce per-tool permissions, block replays, emit receipts.
We read the source, 6 d ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
result = subprocess.run(
const content = fs.readFileSync(path.join(receiptDir, latest), 'utf-8');
const child: ChildProcess = spawn(serverCmd, serverCmdArgs, {
pipeline.innerHTML = STEPS.map(s =>
…d00cf5f5b2fc97d9bbfdb7d025"}}});var j,I=co(()=>{j={tavily:{label:"Tavily POST /search 402 (observed 2026-09-29)",header:"eyJ4NDAyVmVyc2lvbiI6MiwiZXJyb3IiOiJQYXltZW50IGhlYWRlciBpcyByZXF1aXJlZCIsInJlc291cmNlIjp7InVybCI6Imh0dHBzOi8veDQwMi50YXZpbHkuY29tL3NlYXJjaCIsImRlc2NyaXB0aW9uIjo…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Today is the operative word: we check Gateway every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add gateway -- npx -y @bolyra/gateway
{
"mcpServers": {
"gateway": {
"command": "npx",
"args": [
"-y",
"@bolyra/gateway"
]
}
}
}
[mcp_servers.gateway]
command = "npx"
args = ["-y", "@bolyra/gateway"]
{
"mcpServers": {
"gateway": {
"command": "npx",
"args": [
"-y",
"@bolyra/gateway"
]
}
}
}
{
"servers": {
"gateway": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@bolyra/gateway"
]
}
}
}
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.
Stdio MCP auth proxy: wrap any MCP server with per-tool permission enforcement.
Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.
Identity and auth for AI agents: credentials, tokens, delegations, and permission checks.
Owner-signed permissions for AI agent actions; ALLOW/BLOCK/REVIEW with request-bound receipts.
Post-quantum, tamper-evident receipts for agent actions. Ed25519 + ML-DSA-65, offline verify.
Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.
Answers built from our own checks of this server.