RMCP.DEV
← Registry

API Tools

inferenceapis.com

Manages Inference APIs accounts, API keys, model listings, usage and billing via API.

1 endpoint9 known toolsFirst detected October 9, 2026Last detected October 9, 2026

ENDPOINT 1

https://api.inferenceapis.com/mcp

No auth detected

MCP server metadata

Name
inferenceapis
Version
1.0.0
Capabilities
tools
Server instructions

Tools for setting up and managing an Inference APIs account (OpenAI-compatible open-model hosting). Start with docs or list_models; use signup to get a key for a person; account tools need the key on the connection as a Bearer token. Money is added by the person at https://inferenceapis.com/billing.

Known tools 9

signup

Create an Inference APIs account and API key for a person, without a browser.

Potential side effects
list_models

List available models with prices (USD), context length, capabilities and aliases.

Inferred read-only
account

The account behind the key: email, current balance in USD, starter-credit and email-confirmation status, and where to add funds.

Potential side effects
usage

Balance, spend today/this week/this month and over the last N days (default 7, max 90) by model, the account spend limit, and every key's limit, spend, pause/expiry status and allowed models.

Inferred read-only
create_api_key

Create an additional API key for the same account (for a second tool or machine), optionally with a spend limit, expiry and allowed models.

Potential side effects
update_api_key

Change a key's spend limit, period, expiry, allowed models, or pause/resume it.

Inferred read-only
set_account_limits

Set the account-wide spend limit (caps every key together) and the low-balance email threshold.

Potential side effects
test_completion

Send one small chat completion to confirm the key and model work, and report what it cost.

Potential side effects
docs

The plain-text documentation an agent needs: endpoints, models and prices, per-tool config blocks, limits, error codes.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.inferenceapis]
url = "https://api.inferenceapis.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "inferenceapis": {
      "type": "http",
      "url": "https://api.inferenceapis.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: inferenceapis
Remote MCP URL: https://api.inferenceapis.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "inferenceapis": {
      "url": "https://api.inferenceapis.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "inferenceapis": {
      "type": "http",
      "url": "https://api.inferenceapis.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "inferenceapis",
  "transport": "streamable-http",
  "url": "https://api.inferenceapis.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.