Algate MCP

The local MCP server exposes exactly one tool: check_action.

It selects the relevant Algate checks from the action profile and returns one machine-actionable decision. Each new call pays Algate's $0.001 fee in USDC on Algorand. A retry using the same payment_id is deduplicated. The tool never pays the target merchant.

npm install algate-mcp
# TypeScript client:
#   import { Algate, createPaymentId } from 'algate-mcp/client'

Environment:

ALGATE_PAYER_MNEMONIC="your local Algorand payer mnemonic"
ALGATE_URL="https://algate-x402.up.railway.app" # optional

Run it without installing it globally:

npx algate-mcp

Example MCP configuration:

{
  "mcpServers": {
    "algate": {
      "command": "npx",
      "args": ["-y", "algate-mcp"],
      "env": {
        "ALGATE_PAYER_MNEMONIC": "your local Algorand payer mnemonic"
      }
    }
  }
}

Keep payment_id with the logical operation and reuse it after timeouts. The returned error includes the identifier when a retry may be necessary.

The mnemonic is read only by the local process and is never sent to Algate. It signs Algate's own 0.001 USDC analysis payment; check_action never pays the target merchant.

Manual paid smoke

Installation and offline contracts are checked in CI-style scripts. A real MainNet call through the published package is deliberate and manual — see docs/SMOKE.md ($0.001 USDC, do not automate).