Portkey MCP by usefulapi
io.usefulapi/portkeyusefulapi.iostreamable-httpv1.40.4Scanned
Read AI-gateway analytics, configs, virtual keys, workspaces and users; log request feedback.
16 tools: 1 can delete or cancel things and 15 only read.
- Reads private data · 3
- Reads text others write · 0
- Can send data out · 0
- 1 finding
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Portkey MCP by usefulapi can do
The Portkey MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (1 tool: portkey_create_feedback). 15 tools only read.
3 tools read private data (portkey_list_api_keys, portkey_get_api_key and portkey_list_virtual_keys).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Deletes or cancels 1Claude Code: deny
portkey_create_feedbackWRITES a feedback record into the Portkey account, attached to a request/trace by trace_id.No findings
Why it is in this group
- The name "portkey_create_feedback" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Create feedback
- destructiveHint: true
Only reads 15Show 15 read-only tools
portkey_get_analytics_graphGet a time-series analytics graph for a single metric (cost, requests, tokens, latency, error-rate, cache-hit-rate, …) over a time window.No findings
Why it is in this group
- The name "portkey_get_analytics_graph" says "get": a word for reading.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get analytics graph
- readOnlyHint: true
portkey_get_analytics_groupGet grouped analytics (aggregated by models, users, or metadata) over a time window.No findings
Why it is in this group
- The name "portkey_get_analytics_group" says "get": a word for reading.
Description, as the server wrote it Get grouped analytics (aggregated by models, users, or metadata) over a time window. Portkey: GET /analytics/groups/{group}.
Annotations the server declares
- title: Get analytics group
- readOnlyHint: true
portkey_get_api_keyGet a single API key's metadata by id (the secret is never returned).Reads private dataNo findings
Why it is in this group
- The name "portkey_get_api_key" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "secret": it reads secrets.
Description, as the server wrote it Get a single API key's metadata by id (the secret is never returned). Portkey: GET /api-keys/{id}.
Annotations the server declares
- title: Get API key
- readOnlyHint: true
portkey_get_configGet a single gateway config by slug (or id), including its routing rules.No findings
Why it is in this group
- The name "portkey_get_config" says "get": a word for reading.
Description, as the server wrote it Get a single gateway config by slug (or id), including its routing rules. Portkey: GET /configs/{slug}.
Annotations the server declares
- title: Get config
- readOnlyHint: true
portkey_get_userGet a single user by id.No findings
Why it is in this group
- The name "portkey_get_user" says "get": a word for reading.
Description, as the server wrote it Get a single user by id. Portkey: GET /users/{id}.
Annotations the server declares
- title: Get user
- readOnlyHint: true
portkey_get_virtual_keyGet a single virtual key by slug, including its provider + limits.No findings
Why it is in this group
- The name "portkey_get_virtual_key" says "get": a word for reading.
Description, as the server wrote it Get a single virtual key by slug, including its provider + limits. Portkey: GET /virtual-keys/{slug}.
Annotations the server declares
- title: Get virtual key
- readOnlyHint: true
portkey_get_workspaceGet a single workspace by slug/id.No findings
Why it is in this group
- The name "portkey_get_workspace" says "get": a word for reading.
Description, as the server wrote it Get a single workspace by slug/id. Portkey: GET /workspaces/{id}.
Annotations the server declares
- title: Get workspace
- readOnlyHint: true
portkey_list_api_keysList API keys in the organization/workspace (metadata only — secrets are never returned).Reads private dataNo findings
Why it is in this group
- The name "portkey_list_api_keys" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "secret": it reads secrets.
Description, as the server wrote it List API keys in the organization/workspace (metadata only — secrets are never returned). Portkey: GET /api-keys.
Annotations the server declares
- title: List API keys
- readOnlyHint: true
portkey_list_audit_logsList audit log entries (admin actions across the organization).No findings
Why it is in this group
- The name "portkey_list_audit_logs" says "list": a word for reading.
Description, as the server wrote it List audit log entries (admin actions across the organization). Portkey: GET /audit-logs.
Annotations the server declares
- title: List audit logs
- readOnlyHint: true
portkey_list_configsList gateway configs (routing/fallback/retry/cache rulesets applied to requests).No findings
Why it is in this group
- The name "portkey_list_configs" says "list": a word for reading.
Description, as the server wrote it List gateway configs (routing/fallback/retry/cache rulesets applied to requests). Portkey: GET /configs.
Annotations the server declares
- title: List configs
- readOnlyHint: true
portkey_list_user_invitesList pending user invitations to the organization.No findings
Why it is in this group
- The name "portkey_list_user_invites" says "list": a word for reading.
Description, as the server wrote it List pending user invitations to the organization. Portkey: GET /user-invites.
Annotations the server declares
- title: List user invites
- readOnlyHint: true
portkey_list_usersList users in the organization.No findings
Why it is in this group
- The name "portkey_list_users" says "list": a word for reading.
Description, as the server wrote it List users in the organization. Filter by role or email. Portkey: GET /users.
Annotations the server declares
- title: List users
- readOnlyHint: true
portkey_list_virtual_keysList virtual keys (the aliases that map to provider credentials + budget/rate limits used in requests).Reads private data1 finding
Why it is in this group
- The name "portkey_list_virtual_keys" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "credential": it reads secrets.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...keys (the aliases that map to provider credentials + budget/rate limits used in requests)...."
Description, as the server wrote it List virtual keys (the aliases that map to provider credentials + budget/rate limits used in requests). Portkey: GET /virtual-keys.
Annotations the server declares
- title: List virtual keys
- readOnlyHint: true
portkey_list_workspace_membersList members of a workspace (users + their roles).No findings
Why it is in this group
- The name "portkey_list_workspace_members" says "list": a word for reading.
Description, as the server wrote it List members of a workspace (users + their roles). Portkey: GET /workspaces/{id}/members.
Annotations the server declares
- title: List workspace members
- readOnlyHint: true
portkey_list_workspacesList workspaces in the organization.No findings
Why it is in this group
- The name "portkey_list_workspaces" says "list": a word for reading.
Description, as the server wrote it List workspaces in the organization. Portkey: GET /workspaces.
Annotations the server declares
- title: List workspaces
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://portkey.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://portkey.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
The description mentions "credentials".
What this check looks forMatched text
description: "...keys (the aliases that map to provider credentials + budget/rate limits used in requests)...."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://portkey.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://portkey.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http portkey https://portkey.usefulapi.io/mcpclaude mcp add --transport http portkey https://portkey.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__portkey__portkey_get_analytics_graph",
"mcp__portkey__portkey_get_analytics_group",
"mcp__portkey__portkey_list_configs",
"mcp__portkey__portkey_get_config",
"mcp__portkey__portkey_list_api_keys",
"mcp__portkey__portkey_get_api_key",
"mcp__portkey__portkey_list_virtual_keys",
"mcp__portkey__portkey_get_virtual_key",
"mcp__portkey__portkey_list_workspaces",
"mcp__portkey__portkey_get_workspace",
"mcp__portkey__portkey_list_workspace_members",
"mcp__portkey__portkey_list_users",
"mcp__portkey__portkey_get_user",
"mcp__portkey__portkey_list_user_invites",
"mcp__portkey__portkey_list_audit_logs"
],
"ask": [],
"deny": [
"mcp__portkey__portkey_create_feedback"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as portkey. Review it before you use it.
Capability tags behind 3 rules
- mcp__portkey__portkey_list_api_keys private-data
- mcp__portkey__portkey_get_api_key private-data
- mcp__portkey__portkey_list_virtual_keys private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/portkey/verify?hash=bcb83a793b7e8b1830040b98dc0cad842bc8d7f98f45247c4c9d0c1dfc15a9ff" | jq -e '.changed == false'Pinned hash bcb83a793b7e, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/portkey/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/portkey)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Portkey MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Portkey MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 16 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Portkey MCP by usefulapi delete data?
- Yes. 1 tool can delete, cancel or revoke something: portkey_create_feedback.
Can the Portkey MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Portkey MCP by usefulapi have?
- 16 tools: 1 destructive, 15 read. portkey_create_feedback, portkey_get_analytics_graph, portkey_get_analytics_group, portkey_list_configs, portkey_get_config, portkey_list_api_keys, portkey_get_api_key, portkey_list_virtual_keys and 8 more.
Does the Portkey MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Portkey MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Portkey MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.