Gateway

MCP auth gateway: verify agent identity, enforce per-tool permissions, block replays, emit receipts.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "gateway-3": {
      "command": "npx",
      "args": [
        "-y",
        "gateway-3"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Bolyra

Verified agent actions: authorization policy, signed receipts, and tamper-evident audit for AI agent tool calls.

Domain: bolyra.ai
Company: ZKProva Inc.
License: Apache-2.0 (with DCO sign-off — every commit requires Signed-off-by:)

What this is

When an AI agent calls a tool, Bolyra proves who — and what — authorized the action. Put the gateway in front of any MCP server (or embed the verifier in your agent platform) and every tool call gets four checks: credential verification, per-tool policy, replay protection, and a signed audit receipt.

Bolyra ships in two tiers on the same verifier contract:

Bolyra Core — classical crypto, no circuits, no trusted setup: per-tool policy, nonce replay protection, ES256K-signed action receipts, credential binding against registered credentials, and JWT-based delegation claims (@bolyra/delegation). This is the gateway's --dev mode; with a credentials section (or --credentials) configured, claimed identities and permission masks are enforced against the registry — unknown, forged, or expired credentials are denied fail-closed with signed receipts. Without registered credentials, permission claims remain self-asserted (the gateway warns at startup and flags the receipts).
Bolyra ZK — the privacy upgrade: humans prove uniqueness via a Semaphore v4-style enrollment circuit; AI agents prove EdDSA-signed credentials with cumulative-bit permissions; a delegation circuit narrows scope one-way (permissions can only drop, never widen), with the delegation path hidden from the verifier. A handshake binds the human and agent Groth16 proofs to a shared session nonce, verified atomically on-chain.

Core gets you policy-gated, replay-protected, receipted actions. ZK gets you cryptographically bound verified actions without disclosure — the verifier learns that the predicate holds, not your credentials, policies, or delegation graph. You don't need ZK to gate your first MCP server with one command.

Building an agent platform? Bolyra plugs in as an external verifier and gives you an enterprise security capability — verified agent actions — without rebuilding auth. See bolyra.ai.

Repository layout

Code

circuits/        Circom 2 circuits + snarkjs/rapidsnark proving
contracts/       Hardhat — Solidity verifiers + on-chain registry
sdk/             @bolyra/sdk (TypeScript, public API)
sdk-python/      bolyra (Python — pure types + subprocess bridge)
integrations/    langchain, crewai, mcp, openclaw, payment-protocols
spec/            DID method, IETF-style draft, conformance runner
examples/        mcp-demo, provider-mock
docs/            quickstart, OWASP agentic mapping

Quickstart

See sdk/QUICKSTART.md for the TypeScript SDK quickstart.

Build & test

Terminal

npm install
npm run compile:circuits
npm run compile:contracts
npm test                              # circuits fast + contracts
FULL_PROOF=1 npm run test:circuits:slow  # full Groth16/PLONK proving (~2 min)

Protocol Conformance

112 executable test vectors verify the implementation matches the protocol specification. CI runs them on every PR. See spec/CONFORMANCE.md for the current generated report.

Terminal

npm run conformance          # run all 112 vectors
npm run conformance:report   # generate spec/CONFORMANCE.md

Implementing your own EVC host? 28 of those vectors test host behavior and run against any host in any language, with no install:

Terminal

npx @bolyra/evc-conformance --host "/path/to/your-host --flags"

See spec/IMPLEMENTER.md for the full pass path — the Host-Under-Test contract, failure classes, troubleshooting, and a CI snippet.

Contributing

This project requires a Developer Certificate of Origin (DCO) sign-off on every commit. Use git commit -s. See CONTRIBUTING.md for details.

License

Apache-2.0. See LICENSE.

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Gateway

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "gateway": { "command": "npx", "args": ["-y", "gateway"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/gateway-3?style=directory)](https://allmcps.com/mcp/gateway-3)

HTML Embed

<a href="https://allmcps.com/mcp/gateway-3"><img src="https://allmcps.com/api/badge/gateway-3?style=directory" alt="Gateway on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

28Quality signal: Emerging · 28/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools12/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Gateway →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

Bolyra

Verified agent actions: authorization policy, signed receipts, and tamper-evident audit for AI agent tool calls.

Domain: bolyra.ai
Company: ZKProva Inc.
License: Apache-2.0 (with DCO sign-off — every commit requires Signed-off-by:)

What this is

Bolyra ships in two tiers on the same verifier contract:

Bolyra Core — classical crypto, no circuits, no trusted setup: per-tool policy, nonce replay protection, ES256K-signed action receipts, credential binding against registered credentials, and JWT-based delegation claims (@bolyra/delegation). This is the gateway's --dev mode; with a credentials section (or --credentials) configured, claimed identities and permission masks are enforced against the registry — unknown, forged, or expired credentials are denied fail-closed with signed receipts. Without registered credentials, permission claims remain self-asserted (the gateway warns at startup and flags the receipts).
Bolyra ZK — the privacy upgrade: humans prove uniqueness via a Semaphore v4-style enrollment circuit; AI agents prove EdDSA-signed credentials with cumulative-bit permissions; a delegation circuit narrows scope one-way (permissions can only drop, never widen), with the delegation path hidden from the verifier. A handshake binds the human and agent Groth16 proofs to a shared session nonce, verified atomically on-chain.

Building an agent platform? Bolyra plugs in as an external verifier and gives you an enterprise security capability — verified agent actions — without rebuilding auth. See bolyra.ai.

Repository layout

Code

circuits/        Circom 2 circuits + snarkjs/rapidsnark proving
contracts/       Hardhat — Solidity verifiers + on-chain registry
sdk/             @bolyra/sdk (TypeScript, public API)
sdk-python/      bolyra (Python — pure types + subprocess bridge)
integrations/    langchain, crewai, mcp, openclaw, payment-protocols
spec/            DID method, IETF-style draft, conformance runner
examples/        mcp-demo, provider-mock
docs/            quickstart, OWASP agentic mapping

Quickstart

See sdk/QUICKSTART.md for the TypeScript SDK quickstart.

Build & test

Terminal

npm install
npm run compile:circuits
npm run compile:contracts
npm test                              # circuits fast + contracts
FULL_PROOF=1 npm run test:circuits:slow  # full Groth16/PLONK proving (~2 min)

Protocol Conformance

112 executable test vectors verify the implementation matches the protocol specification. CI runs them on every PR. See spec/CONFORMANCE.md for the current generated report.

Terminal

npm run conformance          # run all 112 vectors
npm run conformance:report   # generate spec/CONFORMANCE.md

Implementing your own EVC host? 28 of those vectors test host behavior and run against any host in any language, with no install:

Terminal

npx @bolyra/evc-conformance --host "/path/to/your-host --flags"

See spec/IMPLEMENTER.md for the full pass path — the Host-Under-Test contract, failure classes, troubleshooting, and a CI snippet.

Contributing

This project requires a Developer Certificate of Origin (DCO) sign-off on every commit. Use git commit -s. See CONTRIBUTING.md for details.

License

Apache-2.0. See LICENSE.