All MCP Servers
Dev Tools & GitMCP RegistrymcpbB · 64

Archytan Lite MCP gate

io.github.High-ArchyTech-Solutions · Updated

Puts an MCP tool server behind Archytan Lite: each tool call is authorized and spent before it runs.

At a glance

Archytan Lite MCP gate is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `npx -y https://github.com/High-ArchyTech-Solutions/archytan-mcp-gate/releases/download/v2.8.0/archytan-mcp-gate.mcpb`, and declares no required credentials. It scores B (64/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 0GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install Archytan Lite MCP gate in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install Archytan Lite MCP gate in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add archytan-mcp-gate -- npx -y https://github.com/High-ArchyTech-Solutions/archytan-mcp-gate/releases/download/v2.8.0/archytan-mcp-gate.mcpb
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes. It discovers them automatically.

What tools does Archytan Lite MCP gate expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

The published package could not be downloaded or read for analysis.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit today — Actively maintained.
  • Repository created 8 days ago — Very new project with little track record yet.
  • 0 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 64

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%100%

    Last commit 0 days ago.

  • Adoption20%0%

    0 stars.

  • Transparency20%75%

    3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.

  • Provenance15%75%

    Links to its own repository; package linkage unverified.

  • Packaging15%50%

    No pinned version — installs resolve to whatever is latest at launch.

Documentation

Full README

archytan-mcp-gate

archytan-mcp-gate sits between an MCP host (Claude Code, Claude Desktop, an IDE agent, your own agent) and an MCP tool server. Before any tool call reaches the server, an Archytan Lite gate service has to authorize it. The MCP gate checks the signed receipt for that decision and spends a single-use capability, and only then forwards the call. A call the policy doesn't allow comes back to the agent as a tool error it can read, and never reaches the server.

This repository is the MCP gate's source, under the Apache License 2.0. The Archytan Lite gate service it talks to is a separate product, distributed as a signed container image; its quickstart is in archytan-lite-community.

How it works

The host launches the MCP gate in place of the tool server, and the MCP gate launches the server itself, so it becomes the only path between the agent and its tools. For every tools/call it:

  1. asks the Archytan Lite gate service to authorize the action the call maps

to, on the resource the call names;

  1. verifies the receipt the service returns: its fields must hash to the

signed intent hash, the signature must be the service's key, and the receipt must describe exactly this call;

  1. redeems the single-use capability that came with the ALLOW;
  2. forwards the call to the tool server.

If any step fails, the call is refused and the server never sees it. The agent never holds anything that could skip these steps: the MCP gate holds the agent's credential, and the agent only ever speaks MCP.

Requirements

  • An Archytan Lite gate service with capabilities on

(ARCHYTAN_LITE_CAPABILITIES=on). The tests run against version 2.7.0, the first whose policy can scope a role to named resources.

Excerpt — the full document is on GitHub.

Maintain Archytan Lite MCP gate? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![Archytan Lite MCP gate on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-high-archytech-solutions-archytan-mcp-gate)](https://mcp-skills-hub.vercel.app/mcps/io-github-high-archytech-solutions-archytan-mcp-gate)

Catalog data refreshed . Something wrong? Report it.