Portkey MCP Server

io.usefulapi/portkey

not responding

Portkey is listed as active in the registry but did not answer our last check. It exposes 16 tools. Last commit 1 Aug 2026.

Read AI-gateway analytics, configs, virtual keys, workspaces and users; log request feedback.

Uptime history 41 hours of history · worst hour 0%

41 hours agonow

37.4%

Uptime 24h

34 of 91 checks

Tools

read from the server

183 ms

Response time

average over 24h

Stars

last commit 1 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add portkey --transport http https://portkey.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "portkey": {
      "url": "https://portkey.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.portkey]
url = "https://portkey.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "portkey": {
      "url": "https://portkey.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "portkey": {
      "url": "https://portkey.usefulapi.io/mcp"
    }
  }
}

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

portkey

portkey_create_feedback

WRITES a feedback record into the Portkey account, attached to a request/trace by trace_id. Use for logging a quality score (typically -10..10) with an optional weight (0..1) and metadata. Portkey: POST /feedback.

portkey_get_analytics_graph

Get a time-series analytics graph for a single metric (cost, requests, tokens, latency, error-rate, cache-hit-rate, …) over a time window. Optionally scope by virtual keys, configs, or metadata. Portkey: GET /analytics/graphs/{metric}.

portkey_get_analytics_group

Get grouped analytics (aggregated by models, users, or metadata) over a time window. Portkey: GET /analytics/groups/{group}.

portkey_get_api_key

Get a single API key's metadata by id (the secret is never returned). Portkey: GET /api-keys/{id}.

portkey_get_config

Get a single gateway config by slug (or id), including its routing rules. Portkey: GET /configs/{slug}.

portkey_get_user

Get a single user by id. Portkey: GET /users/{id}.

portkey_get_virtual_key

Get a single virtual key by slug, including its provider + limits. Portkey: GET /virtual-keys/{slug}.

portkey_get_workspace

Get a single workspace by slug/id. Portkey: GET /workspaces/{id}.

portkey_list_api_keys

List API keys in the organization/workspace (metadata only — secrets are never returned). Portkey: GET /api-keys.

portkey_list_audit_logs

List audit log entries (admin actions across the organization). Portkey: GET /audit-logs.

portkey_list_configs

List gateway configs (routing/fallback/retry/cache rulesets applied to requests). Portkey: GET /configs.

portkey_list_user_invites

List pending user invitations to the organization. Portkey: GET /user-invites.

portkey_list_users

List users in the organization. Filter by role or email. Portkey: GET /users.

portkey_list_virtual_keys

List virtual keys (the aliases that map to provider credentials + budget/rate limits used in requests). Portkey: GET /virtual-keys.

portkey_list_workspace_members

List members of a workspace (users + their roles). Portkey: GET /workspaces/{id}/members.

portkey_list_workspaces

List workspaces in the organization. Portkey: GET /workspaces.

Endpoints

URL	Transport	State	Latency	Checked
https://portkey.usefulapi.io/mcp	streamable-http	answering	46 ms	6 min ago

Portkey — questions

Answers built from our own checks of this server.

What can Portkey do?

It exposes 16 tools, read directly from the server on our last check. Among them: portkey_create_feedback, portkey_get_analytics_graph, portkey_get_analytics_group, portkey_get_api_key, portkey_get_config, portkey_get_user and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Portkey working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 34 of 91 checks got a reply (37.4%), average response time 183 ms. The bar chart above shows every period we have measured.

The registry lists Portkey as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Portkey?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Portkey need an API key?

No. Portkey completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Portkey?

It answers our handshake in 183 ms on average, which is faster than 66% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Portkey open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.