MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Deepinfra is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Run DeepInfra inference, list models and read account rate limits.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http deepinfra-mcp https://deepinfra.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# deepinfra_get_account, deepinfra_get_rate_limit, deepinfra_list_api_tokens and 15 more
Deepinfra costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http deepinfra-mcp https://deepinfra.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get the current DeepInfra account / user details (identity, email, quotas). DeepInfra REST: GET /v1/me.
No parameter schema on file.
Get the account's current rate limits (per-model / per-endpoint request and token limits). DeepInfra REST: GET /v1/me/rate_limit.
No parameter schema on file.
List the account's API tokens (metadata only, not secret values). DeepInfra REST: GET /v1/api-tokens.
No parameter schema on file.
Get spend / usage for a billing period. DeepInfra REST: GET /payment/usage.
No parameter schema on file.
Get per-model token usage for a period. DeepInfra REST: GET /payment/usage/tokens.
No parameter schema on file.
Get GPU rental (dedicated hardware) usage for a time range. DeepInfra REST: GET /payment/usage/rent.
No parameter schema on file.
List billing invoices for the account. DeepInfra REST: GET /payment/invoices.
No parameter schema on file.
List the account's dedicated deployments. DeepInfra REST: GET /deploy/list.
No parameter schema on file.
Get one dedicated deployment by id (config + current status). DeepInfra REST: GET /deploy/{deploy_id}.
No parameter schema on file.
Get time-series stats (throughput / latency / replicas) for a dedicated deployment. DeepInfra REST: GET /deploy/{deploy_id}/stats2.
No parameter schema on file.
Get GPU availability for LLM deployments (which hardware can currently be provisioned). DeepInfra REST: GET /deploy/llm/gpu_availability.
No parameter schema on file.
List the DeepInfra model catalog (all available models). DeepInfra REST: GET /models/list.
No parameter schema on file.
Get one model's catalog entry (pricing, context length, capabilities). DeepInfra REST: GET /models/{model_name}.
No parameter schema on file.
Get the hardware options / GPU configuration available for a given model. DeepInfra REST: GET /v2/hardware.
No parameter schema on file.
Query inference request logs for a dedicated deployment over a time window. DeepInfra REST: GET /v1/logs/query.
No parameter schema on file.
Get global live inference metrics across the account (real-time throughput / activity). DeepInfra REST: GET /v1/metrics/live.
No parameter schema on file.
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.
No parameter schema on file.
Stop (pause) a running dedicated deployment. This halts inference and stops accruing GPU charges for it. DeepInfra REST: POST /deploy/{deploy_id}/stop.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Deepinfra or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Deepinfra can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.