# io.usefulapi/portkey (remote · portkey.usefulapi.io)

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

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `portkey.usefulapi.io`: 73/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-portkey/portkey.md), [page](https://verifymcp.io/servers/io-usefulapi-portkey/portkey)

## Channel facts

- Endpoint: `https://portkey.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1318 tokens (~82/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-portkey": {
      "type": "remote",
      "url": "https://portkey.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-portkey --url https://portkey.usefulapi.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-portkey:
    url: "https://portkey.usefulapi.io/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 71, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 69, +57)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 12)

First indexed and scored.

## MCP tools (16)

### `portkey_get_analytics_graph` (~223 tokens)

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}.

Input parameters:

- `configs` (string): Comma-separated config slugs to scope the graph.
- `metadata` (string): JSON string of metadata key/values to scope the graph.
- `metric` (string, required): Which metric graph to return.
- `time_of_generation_max` (string, required): End of the window (ISO8601, format YYYY-MM-DDTHH:MM:SS±HH:MM).
- `time_of_generation_min` (string, required): 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.

### `portkey_get_analytics_group` (~157 tokens)

Get analytics group

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

Input parameters:

- `current_page` (integer): Page number (0-based) for pagination. Default 0.
- `group` (string, required): Dimension to group the analytics by.
- `page_size` (integer): Number of records per page. Default 50.
- `time_of_generation_max` (string, required): End of the window (ISO8601, format YYYY-MM-DDTHH:MM:SS±HH:MM).
- `time_of_generation_min` (string, required): Start of the window (ISO8601, format YYYY-MM-DDTHH:MM:SS±HH:MM).

### `portkey_list_configs` (~49 tokens)

List configs

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

Input parameters:

- `workspace_id` (string): Scope configs to a workspace id/slug.

### `portkey_get_config` (~47 tokens)

Get config

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

Input parameters:

- `slug` (string, required): The config slug or id.

### `portkey_list_api_keys` (~90 tokens)

List API keys

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

Input parameters:

- `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.

### `portkey_get_api_key` (~49 tokens)

Get API key

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

Input parameters:

- `id` (string, required): The API key id.

### `portkey_list_virtual_keys` (~77 tokens)

List virtual keys

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

Input parameters:

- `current_page` (integer): Page number (0-based) for pagination. Default 0.
- `page_size` (integer): Number of records per page. Default 50.

### `portkey_get_virtual_key` (~47 tokens)

Get virtual key

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

Input parameters:

- `slug` (string, required): The virtual key slug.

### `portkey_list_workspaces` (~63 tokens)

List workspaces

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

Input parameters:

- `current_page` (integer): Page number (0-based) for pagination. Default 0.
- `page_size` (integer): Number of records per page. Default 50.

### `portkey_get_workspace` (~40 tokens)

Get workspace

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

Input parameters:

- `id` (string, required): The workspace slug or id.

### `portkey_list_workspace_members` (~83 tokens)

List workspace members

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

Input parameters:

- `current_page` (integer): Page number (0-based) for pagination. Default 0.
- `id` (string, required): The workspace slug or id.
- `page_size` (integer): Number of records per page. Default 50.

### `portkey_list_users` (~96 tokens)

List users

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

Input parameters:

- `current_page` (integer): Page number (0-based) for pagination. Default 0.
- `email` (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).

### `portkey_get_user` (~36 tokens)

Get user

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

Input parameters:

- `id` (string, required): The user id.

### `portkey_list_user_invites` (~67 tokens)

List user invites

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

Input parameters:

- `current_page` (integer): Page number (0-based) for pagination. Default 0.
- `page_size` (integer): Number of records per page. Default 50.

### `portkey_list_audit_logs` (~69 tokens)

List audit logs

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

Input parameters:

- `current_page` (integer): Page number (0-based) for pagination. Default 0.
- `page_size` (integer): Number of records per page. Default 50.

### `portkey_create_feedback` (~125 tokens)

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.

Input parameters:

- `metadata` (object): Arbitrary metadata key/values.
- `trace_id` (string, required): The request/trace id to attach feedback to.
- `value` (number, required): Feedback score, typically -10..10.
- `weight` (number): Relative weight of this feedback, 0..1.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-portkey/portkey#diagnostics

## Score history

- 2026-08-03: 73
- 2026-08-02: 72
- 2026-08-01: 72
- 2026-07-31: 71
- 2026-07-30: 68
- 2026-07-29: 70
- 2026-07-28: 69
- 2026-07-27: 69
- 2026-07-26: 12

## Links

- Remote endpoint: https://portkey.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-portkey/portkey/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-portkey/portkey/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-portkey/portkey