Other · Local MCP server
Agent Gate
Local mandate gate and proof trail for AI agents that take consequential actions.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.forgeorbital/agent-gate- Version
- 0.1.5
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-10
- Updated
- 2026-07-10
- Publisher
- com.forgeorbital
- Namespace
- Namespace verified by the MCP Registry via the domain forgeorbital.com · how
- Website
- forgeorbital.com/agent-gate
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | forge-agent-gate | 0.1.5 | stdio |
How to connect Agent Gate
Agent Gate runs locally from a Node.js package published to the npm registry: forge-agent-gate version 0.1.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y forge-agent-gate@0.1.5. It reads these environment variables: FORGE_API_KEY (secret), FORGE_BEARER_TOKEN (secret), FORGE_API_BASE_URL, FORGE_TENANT_ID (required), FORGE_RECORD_MODE, AGENT_GATE_MANDATE_PATH, AGENT_GATE_KILL_FILE, KALSHI_API_KEY_ID (secret), KALSHI_PRIVATE_KEY_PATH and KALSHI_ENV; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"agent-gate": {
"command": "npx",
"args": [
"-y",
"forge-agent-gate@0.1.5"
],
"env": {
"FORGE_API_KEY": "<secret>",
"FORGE_BEARER_TOKEN": "<secret>",
"FORGE_API_BASE_URL": "<value>",
"FORGE_TENANT_ID": "<value>",
"FORGE_RECORD_MODE": "<value>",
"AGENT_GATE_MANDATE_PATH": "<value>",
"AGENT_GATE_KILL_FILE": "<value>",
"KALSHI_API_KEY_ID": "<secret>",
"KALSHI_PRIVATE_KEY_PATH": "<value>",
"KALSHI_ENV": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Agent Facing CatalogMachine catalog for products that want agent clients: surfaces, hops, discovery paths. | Remote · HTTPLive check: ✓ handshake |
| Agent FactoryDeterministic, receipted digital microservices. Gate A is simulation-only. | Remote · HTTPLive check: ✗ no handshake |
| Agent Failure Archive186 real AI agent post-mortems, 107 of them measurement failures. Free tools, paid via x402. | Remote · HTTPLive check: ✓ handshake |
| Agent Firewall MCPInput/output safety for AI agents: known-pattern injection and obfuscation scan, URL/IP, secrets. | Local · stdio |
| Agent GateFail-closed quality gate and hash-chained receipt ledger for AI agent workflows. | Local · stdio |
| Agent GatewayRelux Works studio gateway: read services/pricing and submit a project inquiry to hire the team. | Remote · HTTPLive check: ✓ handshake |
| Agent Graph AuditorFinds transitive excessive agency across LangGraph/CrewAI/AutoGen orchestration graphs. | Local · stdio |
| Agent GuardSafety checks an agent runs before it acts: package malware, destructive command, secret leak. | Local · stdio |