Portkey MCP by usefulapi
REMOTE · PORTKEY.USEFULAPI.IO
Read AI-gateway analytics, configs, virtual keys, workspaces and users; log request feedback.
Available components
Last scanned (23 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 4 Nov 2026.
Category AI and Machine Learning
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_virtual_keys_their_limits_and_api_keys” functional
- New prompt “compare_models_users_or_metadata_by_usage” functional
- New prompt “log_a_quality_score_for_a_request” functional
- New prompt “review_gateway_configs_and_their_routing_rules” functional
- New prompt “review_users_invites_and_admin_actions” functional
- New prompt “track_cost_tokens_errors_and_latency_over_time” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 functional
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 4 Nov 2026 · Probed https://portkey.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 portkey.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://portkey.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/portkey/ |
| http (plaintext) | http://portkey.usefulapi.io/mcp | Inconclusive | 302 | http://portkey.usefulapi.io/mcp |
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 →
portkey_create_feedback Create feedback ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| metadata | object | – | Arbitrary metadata key/values. |
| trace_id | string | yes | The request/trace id to attach feedback to. |
| value | number | yes | Feedback score, typically -10..10. |
| weight | number | – | Relative weight of this feedback, 0..1. |
No output schema declared.
No examples provided.
portkey_get_analytics_graph Get analytics graph ~223
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| configs | string | – | Comma-separated config slugs to scope the graph. |
| metadata | string | – | JSON string of metadata key/values to scope the graph. |
| metric | string | yes | Which metric graph to return. |
| time_of_generation_max | string | yes | End of the window (ISO8601, format YYYY-MM-DDTHH:MM:SS±HH:MM). |
| time_of_generation_min | string | yes | Start of the window (ISO8601, format YYYY-MM-DDTHH:MM:SS±HH:MM). |
| total_units | string | – | Bucket size for the series, e.g. "day" or "hour". |
| virtual_keys | string | – | Comma-separated virtual key slugs to scope the graph. |
No output schema declared.
No examples provided.
portkey_get_analytics_group Get analytics group ~157
Get grouped analytics (aggregated by models, users, or metadata) over a time window. Portkey: GET /analytics/groups/{group}.
| Name | Type | Req | Description |
|---|---|---|---|
| current_page | integer | – | Page number (0-based) for pagination. Default 0. |
| group | string | yes | Dimension to group the analytics by. |
| page_size | integer | – | Number of records per page. Default 50. |
| time_of_generation_max | string | yes | End of the window (ISO8601, format YYYY-MM-DDTHH:MM:SS±HH:MM). |
| time_of_generation_min | string | yes | Start of the window (ISO8601, format YYYY-MM-DDTHH:MM:SS±HH:MM). |
No output schema declared.
No examples provided.
portkey_get_api_key Get API key ~49
Get a single API key's metadata by id (the secret is never returned). Portkey: GET /api-keys/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The API key id. |
No output schema declared.
No examples provided.
portkey_get_config Get config ~47
Get a single gateway config by slug (or id), including its routing rules. Portkey: GET /configs/{slug}.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The config slug or id. |
No output schema declared.
No examples provided.
portkey_get_user Get user ~36
Get a single user by id. Portkey: GET /users/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The user id. |
No output schema declared.
No examples provided.
portkey_get_virtual_key Get virtual key ~47
Get a single virtual key by slug, including its provider + limits. Portkey: GET /virtual-keys/{slug}.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The virtual key slug. |
No output schema declared.
No examples provided.
portkey_get_workspace Get workspace ~40
Get a single workspace by slug/id. Portkey: GET /workspaces/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The workspace slug or id. |
No output schema declared.
No examples provided.
portkey_list_api_keys List API keys ~90
List API keys in the organization/workspace (metadata only — secrets are never returned). Portkey: GET /api-keys.
| Name | Type | Req | Description |
|---|---|---|---|
| current_page | integer | – | Page number (0-based) for pagination. Default 0. |
| page_size | integer | – | Number of records per page. Default 50. |
| workspace_id | string | – | Scope keys to a workspace id/slug. |
No output schema declared.
No examples provided.
portkey_list_audit_logs List audit logs ~69
List audit log entries (admin actions across the organization). Portkey: GET /audit-logs.
| Name | Type | Req | Description |
|---|---|---|---|
| current_page | integer | – | Page number (0-based) for pagination. Default 0. |
| page_size | integer | – | Number of records per page. Default 50. |
No output schema declared.
No examples provided.
portkey_list_configs List configs ~49
List gateway configs (routing/fallback/retry/cache rulesets applied to requests). Portkey: GET /configs.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_id | string | – | Scope configs to a workspace id/slug. |
No output schema declared.
No examples provided.
portkey_list_user_invites List user invites ~67
List pending user invitations to the organization. Portkey: GET /user-invites.
| Name | Type | Req | Description |
|---|---|---|---|
| current_page | integer | – | Page number (0-based) for pagination. Default 0. |
| page_size | integer | – | Number of records per page. Default 50. |
No output schema declared.
No examples provided.
portkey_list_users List users ~96
List users in the organization. Filter by role or email. Portkey: GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| current_page | integer | – | Page number (0-based) for pagination. Default 0. |
| string | – | Filter users by email address. | |
| page_size | integer | – | Number of records per page. Default 50. |
| role | string | – | Filter users by role (e.g. admin, member). |
No output schema declared.
No examples provided.
portkey_list_virtual_keys List virtual keys ~77
List virtual keys (the aliases that map to provider credentials + budget/rate limits used in requests). Portkey: GET /virtual-keys.
| Name | Type | Req | Description |
|---|---|---|---|
| current_page | integer | – | Page number (0-based) for pagination. Default 0. |
| page_size | integer | – | Number of records per page. Default 50. |
No output schema declared.
No examples provided.
portkey_list_workspace_members List workspace members ~83
List members of a workspace (users + their roles). Portkey: GET /workspaces/{id}/members.
| Name | Type | Req | Description |
|---|---|---|---|
| current_page | integer | – | Page number (0-based) for pagination. Default 0. |
| id | string | yes | The workspace slug or id. |
| page_size | integer | – | Number of records per page. Default 50. |
No output schema declared.
No examples provided.
portkey_list_workspaces List workspaces ~63
List workspaces in the organization. Portkey: GET /workspaces.
| Name | Type | Req | Description |
|---|---|---|---|
| current_page | integer | – | Page number (0-based) for pagination. Default 0. |
| page_size | integer | – | Number of records per page. Default 50. |
No output schema declared.
No examples provided.
How do I install the Portkey MCP by usefulapi server?
Portkey MCP by usefulapi is a hosted endpoint at https://portkey.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 · portkey.usefulapi.io
claude mcp add --transport http io-usefulapi-portkey 'https://portkey.usefulapi.io/mcp'
What is the Portkey MCP by usefulapi server?
Portkey MCP by usefulapi is listed in the public MCP registry as io.usefulapi/portkey. Read AI-gateway analytics, configs, virtual keys, workspaces and users; log request feedback. This page covers its hosted endpoint (https://portkey.usefulapi.io/mcp).
Is the Portkey MCP by usefulapi server safe to use?
Portkey MCP by usefulapi scores 18 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 Portkey MCP by usefulapi server expose?
Portkey MCP by usefulapi exposes 16 tools: portkey_get_analytics_graph, portkey_get_analytics_group, portkey_list_configs, portkey_get_config, portkey_list_api_keys, and 11 more. Their descriptions and schemas cost roughly 1,318 tokens of context every time the server is loaded.
Does the Portkey MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Portkey MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Portkey MCP by usefulapi server still maintained?
Portkey MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.