io.usefulapi/portkey
REMOTE · PORTKEY.USEFULAPI.IO · SCANNED SEP 20
Read AI-gateway analytics, configs, virtual keys, workspaces and users; log request feedback.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1318 tokens (~82/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
How do I install the io.usefulapi/portkey MCP server?
io.usefulapi/portkey 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'
{
"mcpServers": {
"io-usefulapi-portkey": {
"url": "https://portkey.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-portkey": {
"type": "http",
"url": "https://portkey.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-portkey] url = "https://portkey.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-portkey": {
"type": "remote",
"url": "https://portkey.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-portkey --url 'https://portkey.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-portkey:
url: "https://portkey.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-portkey": {
"Transport": "http",
"Url": "https://portkey.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-portkey -t streamable-http -u 'https://portkey.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-portkey": {
"type": "http",
"url": "https://portkey.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 −1
No change was recorded against any check on this day. Endpoint Security went from 80 to 78.
- 18 Sept 26 +1
No change was recorded against any check on this day. Endpoint Security went from 78 to 80.
- 10 Sept 26 0
- Stability: 0.97 → pass security
- 9 Sept 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 0
- Authorization: unverified → pass ▲ security
- Stability: fail → 0.73 functional
- 15 Aug 26 0
- Authorization: fail → unverified ▼ security
- Stability: 0.60 → fail ▼ security
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 20 Sept 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 | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 385d93df35f2bf830ebe34a6ff239333 |
| SANs: usefulapi.io, portkey.usefulapi.io, *.portkey.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 | 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://portkey.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://portkey.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://portkey.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://portkey.usefulapi.io/mcp |
| Authorisation server | https://portkey.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://portkey.usefulapi.io/mcp | Inconclusive | 401 |
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.
What is the io.usefulapi/portkey MCP server?
io.usefulapi/portkey is an MCP server 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 io.usefulapi/portkey MCP server safe to use?
io.usefulapi/portkey scores 86 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/portkey MCP server expose?
io.usefulapi/portkey 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 io.usefulapi/portkey MCP server require authentication?
Yes. io.usefulapi/portkey 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/portkey MCP server still maintained?
io.usefulapi/portkey is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.