This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Model Context Protocol (MCP) server for INFERVA. It lets AI agents buy inference through INFERVA and read the network's public state, including the settlement log they can verify themselves.
INFERVA is one inference endpoint that AI agents pay through. Agents send standard chat-completion requests to a single URL. Each request is routed to a provider, metered, paid in USDC and written to a hash-chained settlement log. A protocol fee on every request goes to $INFER stakers and to the capacity sponsors whose prepaid capacity served it, with the rest going to the treasury. Rewards come only from fees agents actually paid. INFERVA is launching on Elysium.
Website: https://inferva.xyz
Docs: https://docs.inferva.xyz
GitHub: https://github.com/inferva
Related MCP server: alexa-pay-mcp
chat is the only tool that spends money: it charges the agent key owner's USDC balance. Every other tool is a free public read and needs no key.
Tool | What it does | INFERVA route |
| Paid chat completion. Returns the reply, |
|
| Models served by active providers, with list price per 1k tokens. |
|
| Per model: list and all-in price per 1M tokens, usage, latency, success rate, and the endpoint limits. |
|
| Requests, volume, fees, treasury, INFER staked, sponsored capacity, providers, current epoch and a 24-epoch series. |
|
| Live protocol parameters with readable values and whether governance can change them. |
|
| Most recent settled requests with cost, fee split, hashes and receipt URLs. |
|
| One request's receipt, with its hash and links re-checked locally. |
|
| Downloads the whole settlement log from the genesis value and recomputes every SHA-256 hash locally. Reports records checked and the first broken record, if any. |
|
| Providers: status, routability, routing weight, INFER bond, slashed amount, usage and per-model prices. |
|
| One provider in detail: billed USDC, success rate, uptime, slashes, events, recent requests. |
|
| Executed slashes and the INFER the treasury holds from them. |
|
| Governance proposals (parameter, slash, routing weight) with stake-weighted votes. |
|
| One proposal with every vote. |
|
| Live gateway load, congestion state and the admission ceiling per stake tier. |
|
| Fee epochs with volume, fees and the staker / sponsor / treasury split. |
|
| Top stakers, capacity sponsors and providers. |
|
| Open listings of sponsored capacity positions and recent sales. |
|
Where a tool converts amounts it names the unit (_usdc, _infer). Where it passes the API's data through, it says so in a units field: amounts there are integers in micro units (1 USDC or 1 INFER = 1,000,000).
Every settlement record stores the hash of the record before it. A record's hash is
sha256(prev_hash | id | payer | provider | model | tokens | base | discount | fee | capacity_id | epoch | created_at)with the fields joined by | and the first record chained to the published genesis value. verify_settlement_chain rebuilds every hash from the record contents and never trusts the stored hash column, so an edited, dropped or reordered record shows up as the first broken record.
You need Node.js 20 or newer. Build from source:
git clone https://github.com/inferva/inferva-mcp.git
cd inferva-mcp
pnpm install
pnpm buildThe server is node /path/to/inferva-mcp/dist/cli.js (bin name inferva-mcp). For the chat tool, create an agent key in the app under Endpoint & keys. Read tools work without a key.
claude mcp add inferva \
--env INFERVA_API_KEY=inf_sk_your_key \
-- node /path/to/inferva-mcp/dist/cli.jsLeave out --env INFERVA_API_KEY=... to use the read tools only.
Add this to claude_desktop_config.json:
{
"mcpServers": {
"inferva": {
"command": "node",
"args": ["/path/to/inferva-mcp/dist/cli.js"],
"env": { "INFERVA_API_KEY": "inf_sk_your_key" }
}
}
}Add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"inferva": {
"command": "node",
"args": ["/path/to/inferva-mcp/dist/cli.js"],
"env": { "INFERVA_API_KEY": "inf_sk_your_key" }
}
}
}Variable | Default | Purpose |
| none | Agent key ( |
|
| App and endpoint origin. |
|
| Per-request timeout. |
| unset | Set to |
Tool errors come back as { "error": <code>, "status": <http>, "message": <from INFERVA>, "hint": <what to do> }. Codes from the endpoint include invalid_api_key, insufficient_funds, spend_cap_reached, model_not_allowed, model_not_found, rate_limit_exceeded, congestion_deferred, capacity_exhausted and provider_error. A request that fails at the provider is not charged.
pnpm install
pnpm test # vitest, mocked fetch
pnpm typecheck
pnpm build # tsup -> dist/MIT © INFERVA
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Paid agent work and paid verification, settled in USDC. Verified outcomes get signed receipts.
Marketplace and payment rail for AI agents: list, buy and settle with signed receipts.
A public home for AI agents and humans: readable chat, play, and human-controlled access tokens.
Machine-payable API infrastructure for autonomous agents. Per-call x402 settlement in USDC.
