Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.usefulapi/deepinfra

REMOTE · DEEPINFRA.USEFULAPI.IO · SCANNED OCT 3

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

78 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1181 tokens (~65/item across 18 items; 18 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

remote · deepinfra.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-deepinfra 'https://deepinfra.usefulapi.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-usefulapi-deepinfra": {
      "url": "https://deepinfra.usefulapi.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-usefulapi-deepinfra": {
      "type": "http",
      "url": "https://deepinfra.usefulapi.io/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-deepinfra --url 'https://deepinfra.usefulapi.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-deepinfra:
    url: "https://deepinfra.usefulapi.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-usefulapi-deepinfra": {
      "Transport": "http",
      "Url": "https://deepinfra.usefulapi.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-usefulapi-deepinfra -t streamable-http -u 'https://deepinfra.usefulapi.io/mcp'
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Oct 26 +1
    • Server version: 1.3.0 → 1.5.1 functional
  • 1 Oct 26 +7
    • HTTPS: unverified → pass ▲ security
    • Authorization: fail → pass ▲ security
    • First check of Authorization: partial security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.0 → 1.3.0 functional
  • 30 Sept 26 +52
    • Authorization: unverified → fail ▼ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → fail ▼ functional
    • 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 functional
  • 29 Sept 26 18

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Oct 2026 · Probed https://deepinfra.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of deepinfra.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://deepinfra.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://deepinfra.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://deepinfra.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://deepinfra.usefulapi.io/mcp
Authorisation server https://deepinfra.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://deepinfra.usefulapi.io/mcp Verified 200
http (plaintext) http://deepinfra.usefulapi.io/mcp HTTPS enforced 301 https://deepinfra.usefulapi.io/mcp
MCP tools · 18 exposed · ~1,181 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
deepinfra_get_account ~51

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

NameTypeReqDescription
checklistboolean–Include the onboarding checklist state in the response.

No output schema declared.

No examples provided.

deepinfra_get_deployment ~47

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

NameTypeReqDescription
deploy_idstringyesThe deployment id (required).

No output schema declared.

No examples provided.

deepinfra_get_deployment_stats ~114

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

NameTypeReqDescription
deploy_idstringyesThe deployment id (required).
fromstringyesRange start (required) — a unix timestamp or a relative expression like 'now-5h' (units: s, m, h, d, w).
tostring–Range end — unix timestamp or relative expression; defaults to now.

No output schema declared.

No examples provided.

deepinfra_get_gpu_availability ~65

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

NameTypeReqDescription
base_modelstring–Filter by base model.
sourcestring–Filter by source.

No output schema declared.

No examples provided.

deepinfra_get_hardware ~51

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

NameTypeReqDescription
modelstringyesThe model name to query hardware for (required).

No output schema declared.

No examples provided.

deepinfra_get_live_metrics ~38

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

deepinfra_get_model ~95

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

NameTypeReqDescription
model_namestringyesThe model name (required). May contain a slash, e.g. 'meta-llama/Meta-Llama-3-8B' — the slash is preserved in the path.
versionstring–A specific model version (defaults to latest).

No output schema declared.

No examples provided.

deepinfra_get_rate_limit ~43

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

deepinfra_get_usage ~89

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

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

No output schema declared.

No examples provided.

deepinfra_get_usage_rent ~74

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

NameTypeReqDescription
fromintegeryesRange start as a unix timestamp in seconds (required).
tointeger–Range end as a unix timestamp in seconds; defaults to now.

No output schema declared.

No examples provided.

deepinfra_get_usage_tokens ~92

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

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

No output schema declared.

No examples provided.

deepinfra_list_api_tokens ~37

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

deepinfra_list_deployments ~51

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

NameTypeReqDescription
statusstring–Comma-separated statuses to filter by, e.g. 'running,initializing'.

No output schema declared.

No examples provided.

deepinfra_list_invoices ~71

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

NameTypeReqDescription
invoice_typestring–Filter by invoice type.
limitinteger–Max number of invoices to return.
starting_afterstring–Cursor — return invoices after this invoice id (pagination).

No output schema declared.

No examples provided.

deepinfra_list_models ~30

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

deepinfra_query_logs ~109

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

NameTypeReqDescription
deploy_idstringyesThe deployment id to query logs for (required).
fromstring–Window start — fractional-seconds unix timestamp, inclusive.
limitinteger–Max log lines to return (default 100, range 1..1000).
tostring–Window end — fractional-seconds unix timestamp, exclusive.

No output schema declared.

No examples provided.

deepinfra_start_deployment ~63

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.

NameTypeReqDescription
deploy_idstringyesThe deployment id to start (required).

No output schema declared.

No examples provided.

deepinfra_stop_deployment ~61

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

NameTypeReqDescription
deploy_idstringyesThe deployment id to stop (required).

No output schema declared.

No examples provided.

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.