# io.usefulapi/deepinfra (remote · deepinfra.usefulapi.io)

Run DeepInfra inference, list models and read account rate limits.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `deepinfra.usefulapi.io`: 78/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-deepinfra/deepinfra.md), [page](https://verifymcp.io/servers/io-usefulapi-deepinfra/deepinfra)

## Channel facts

- Endpoint: `https://deepinfra.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1181 tokens (~65/item across 18 items; 18 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.usefulapi/deepinfra MCP server?

io.usefulapi/deepinfra is a hosted endpoint at https://deepinfra.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-deepinfra 'https://deepinfra.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-deepinfra": {
      "url": "https://deepinfra.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-deepinfra": {
      "type": "http",
      "url": "https://deepinfra.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-deepinfra]
url = "https://deepinfra.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-deepinfra": {
      "type": "remote",
      "url": "https://deepinfra.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-deepinfra --url 'https://deepinfra.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-deepinfra:
    url: "https://deepinfra.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-deepinfra": {
      "Transport": "http",
      "Url": "https://deepinfra.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-deepinfra -t streamable-http -u 'https://deepinfra.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-deepinfra": {
      "type": "http",
      "url": "https://deepinfra.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-02 (score 78, +1)

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 77, +7)

- [security improvement] HTTPS: unverified → pass
- [security improvement] Authorization: fail → pass
- [security] First check of Authorization: partial
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 70, +52)

- [security regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (18)

### `deepinfra_get_account` (~51 tokens)

Get account

Get the current DeepInfra account / user details (identity, email, quotas). DeepInfra REST: GET /v1/me.

Input parameters:

- `checklist` (boolean): Include the onboarding checklist state in the response.

### `deepinfra_get_rate_limit` (~43 tokens)

Get rate limit

Get the account's current rate limits (per-model / per-endpoint request and token limits). DeepInfra REST: GET /v1/me/rate_limit.

### `deepinfra_list_api_tokens` (~37 tokens)

List API tokens

List the account's API tokens (metadata only, not secret values). DeepInfra REST: GET /v1/api-tokens.

### `deepinfra_get_usage` (~89 tokens)

Get usage

Get spend / usage for a billing period. DeepInfra REST: GET /payment/usage.

Input parameters:

- `from` (string, required): Period start (required). Format 'YYYY.MM', or 'current', or 'current(-N)' for N months back, or a unix timestamp in seconds.
- `to` (string): Period end (same format as `from`); defaults to the current period.

### `deepinfra_get_usage_tokens` (~92 tokens)

Get token usage

Get per-model token usage for a period. DeepInfra REST: GET /payment/usage/tokens.

Input parameters:

- `from` (string, required): Period start (required). Format 'YYYY.MM', or 'current', or 'current(-N)' for N months back, or a unix timestamp in seconds.
- `to` (string): Period end (same format as `from`); defaults to the current period.

### `deepinfra_get_usage_rent` (~74 tokens)

Get GPU rental usage

Get GPU rental (dedicated hardware) usage for a time range. DeepInfra REST: GET /payment/usage/rent.

Input parameters:

- `from` (integer, required): Range start as a unix timestamp in seconds (required).
- `to` (integer): Range end as a unix timestamp in seconds; defaults to now.

### `deepinfra_list_invoices` (~71 tokens)

List invoices

List billing invoices for the account. DeepInfra REST: GET /payment/invoices.

Input parameters:

- `invoice_type` (string): Filter by invoice type.
- `limit` (integer): Max number of invoices to return.
- `starting_after` (string): Cursor — return invoices after this invoice id (pagination).

### `deepinfra_list_deployments` (~51 tokens)

List deployments

List the account's dedicated deployments. DeepInfra REST: GET /deploy/list.

Input parameters:

- `status` (string): Comma-separated statuses to filter by, e.g. 'running,initializing'.

### `deepinfra_get_deployment` (~47 tokens)

Get deployment

Get one dedicated deployment by id (config + current status). DeepInfra REST: GET /deploy/{deploy_id}.

Input parameters:

- `deploy_id` (string, required): The deployment id (required).

### `deepinfra_get_deployment_stats` (~114 tokens)

Get deployment stats

Get time-series stats (throughput / latency / replicas) for a dedicated deployment. DeepInfra REST: GET /deploy/{deploy_id}/stats2.

Input parameters:

- `deploy_id` (string, required): The deployment id (required).
- `from` (string, required): Range start (required) — a unix timestamp or a relative expression like 'now-5h' (units: s, m, h, d, w).
- `to` (string): Range end — unix timestamp or relative expression; defaults to now.

### `deepinfra_get_gpu_availability` (~65 tokens)

Get GPU availability

Get GPU availability for LLM deployments (which hardware can currently be provisioned). DeepInfra REST: GET /deploy/llm/gpu_availability.

Input parameters:

- `base_model` (string): Filter by base model.
- `source` (string): Filter by source.

### `deepinfra_list_models` (~30 tokens)

List models

List the DeepInfra model catalog (all available models). DeepInfra REST: GET /models/list.

### `deepinfra_get_model` (~95 tokens)

Get model

Get one model's catalog entry (pricing, context length, capabilities). DeepInfra REST: GET /models/{model_name}.

Input parameters:

- `model_name` (string, required): The model name (required). May contain a slash, e.g. 'meta-llama/Meta-Llama-3-8B' — the slash is preserved in the path.
- `version` (string): A specific model version (defaults to latest).

### `deepinfra_get_hardware` (~51 tokens)

Get hardware

Get the hardware options / GPU configuration available for a given model. DeepInfra REST: GET /v2/hardware.

Input parameters:

- `model` (string, required): The model name to query hardware for (required).

### `deepinfra_query_logs` (~109 tokens)

Query logs

Query inference request logs for a dedicated deployment over a time window. DeepInfra REST: GET /v1/logs/query.

Input parameters:

- `deploy_id` (string, required): The deployment id to query logs for (required).
- `from` (string): Window start — fractional-seconds unix timestamp, inclusive.
- `limit` (integer): Max log lines to return (default 100, range 1..1000).
- `to` (string): Window end — fractional-seconds unix timestamp, exclusive.

### `deepinfra_get_live_metrics` (~38 tokens)

Get live metrics

Get global live inference metrics across the account (real-time throughput / activity). DeepInfra REST: GET /v1/metrics/live.

### `deepinfra_start_deployment` (~63 tokens)

Start deployment

Start (resume) a dedicated deployment. WARNING: this resumes a dedicated deployment and may incur GPU charges while it runs. DeepInfra REST: POST /deploy/{deploy_id}/start.

Input parameters:

- `deploy_id` (string, required): The deployment id to start (required).

### `deepinfra_stop_deployment` (~61 tokens)

Stop deployment

Stop (pause) a running dedicated deployment. This halts inference and stops accruing GPU charges for it. DeepInfra REST: POST /deploy/{deploy_id}/stop.

Input parameters:

- `deploy_id` (string, required): The deployment id to stop (required).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-deepinfra/deepinfra#diagnostics

## Score history

- 2026-10-03: 78
- 2026-10-02: 78
- 2026-10-01: 77
- 2026-09-30: 70
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/deepinfra MCP server?

io.usefulapi/deepinfra is an MCP server listed in the public MCP registry as io.usefulapi/deepinfra. Run DeepInfra inference, list models and read account rate limits. This page covers its hosted endpoint (https://deepinfra.usefulapi.io/mcp).

### Is the io.usefulapi/deepinfra MCP server safe to use?

io.usefulapi/deepinfra scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.usefulapi/deepinfra MCP server expose?

io.usefulapi/deepinfra exposes 18 tools: deepinfra_get_account, deepinfra_get_rate_limit, deepinfra_list_api_tokens, deepinfra_get_usage, deepinfra_get_usage_tokens, and 13 more. Their descriptions and schemas cost roughly 1,181 tokens of context every time the server is loaded.

### Does the io.usefulapi/deepinfra MCP server require authentication?

Yes. io.usefulapi/deepinfra asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.usefulapi/deepinfra MCP server still maintained?

io.usefulapi/deepinfra is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://deepinfra.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-deepinfra/deepinfra.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-deepinfra/deepinfra.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-deepinfra/deepinfra