Bolyra runs on your own machine — the client starts it, so there is no endpoint to ping. 208 installs a week from npm. Last commit 26 Oct 2026.
MCP auth middleware: gate tool calls so only authorized agents can act.
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, {
export function checkRequestBinding(
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 Bolyra 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 mcp -- npx -y @bolyra/mcp
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@bolyra/mcp"
]
}
}
}
[mcp_servers.mcp]
command = "npx"
args = ["-y", "@bolyra/mcp"]
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@bolyra/mcp"
]
}
}
}
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@bolyra/mcp"
]
}
}
}
Puts an MCP tool server behind Archytan Lite: each tool call is authorized and spent before it runs.
Authorizes MCP tool calls against a session policy, not one call at a time.
Read-only VMware vCenter/ESXi monitoring, 33 MCP tools; vSphere calls allowlist-gated in tests.
Local MCP gateway: approved tools behind a signed authority check, per call or as exactly-once jobs
AGENTS.md + skills MCP with CHP R0 gate and adversary decision tools.
Governed MCP gateway: approved tools only, each call policy-checked and recorded per agent
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.
Answers built from our own checks of this server.