Local MCP Wrapper | Stdio Transport | Agent-First Install

Augur MCP Setup

Use the local wrapper when you want Augur's paid HTTP API exposed as MCP tools inside Claude Desktop, Codex-compatible clients, or any MCP host that can launch a stdio server.

This keeps x402 payment on the client side while preserving the same `skill.md`, OpenAPI, and paid `/analyze` contract used by direct integrations.

stdioLocal Server

x402Client Side

2 toolsDefault Set

npxFast Install

Fast Install

npx -y augurrisk-mcp

Set CLIENT_PRIVATE_KEY in your MCP host environment so the local wrapper can handle x402 payments on Base.

What this gives you

This wrapper is for agents that prefer MCP-native tool calling over direct HTTP. The underlying service contract does not change.

Local stdio MCP server
x402 payment stays client-side on your machine
No API key or signup for Augur itself
Two tools out of the box: analyze_base_contract_risk and describe_augur_service

Install

npx -y augurrisk-mcp

The package is published on npm as augurrisk-mcp. Set CLIENT_PRIVATE_KEY in your MCP client env so the local wrapper can handle x402 payments.

If you want to inspect or fork the wrapper source, it still lives in the repo:

git clone https://github.com/JleviEderer/risk-api
cd risk-api/examples/javascript/augur-mcp
npm install
npm run smoke
npm run smoke -- --paid

Wire it into an MCP client

Point your MCP host at the local stdio entrypoint. Keep AUGUR_URL pointed at the canonical public deployment unless you are testing against another environment.

Point your MCP client at the local stdio server entrypoint:

{
  "command": "npx",
  "args": ["-y", "augurrisk-mcp"],
  "env": {
    "CLIENT_PRIVATE_KEY": "0xYOUR_PRIVATE_KEY",
    "AUGUR_URL": "https://augurrisk.com"
  }
}

Use the same stdio command in Claude Desktop, Codex-compatible clients, or other MCP tooling that supports local servers.

Augur MCP Setup

What this gives you

Install

Wire it into an MCP client

Read the wrapper docs