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

Evaluate and inspect your Hypertune feature flags from your AI assistant.

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

## Components

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

## Channel facts

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

## 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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 607 tokens (~121/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - 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-hypertune https://hypertune.usefulapi.io/mcp
```

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-hypertune": {
      "type": "http",
      "url": "https://hypertune.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-02 (score 73, +1)

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

### 2026-07-31 (score 72, +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 69, −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 71, +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 70, +1)

- [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 (5)

### `hypertune_evaluate` (~213 tokens)

Evaluate feature flags

Evaluate one or more feature flags for a given context and get their resolved values. Builds `query { root(context: <context>) { <selection> } }`. Provide `selection` = the flag fields to read (e.g. `exampleFlag anotherFlag { nestedField }`) and `context` = the evaluation context (environment + user/attributes). Every field must supply all of its arguments (Hypertune reduces the flag logic to a JSON result). Use hypertune_list_flags / hypertune_introspect first if you don't know the flag names.

Input parameters:

- `context` (object): Evaluation context object, inlined as the `context` arg. e.g. {"environment":"production","user":{"id":"u_123","email":"a@b.com"}}. Omit to return the flag LOGIC instead of a reduced value.
- `selection` (string, required): GraphQL selection of flag fields under root, e.g. `exampleFlag` or `homePage { showBanner } exampleFlag`.

### `hypertune_get_logic` (~127 tokens)

Get flag logic (unreduced)

Fetch the underlying LOGIC of flags without reducing them — i.e. `query { root { <selection> } }` with no context. Returns the flag's conditional expression / rules rather than a single resolved value, useful for inspecting how a flag is configured. If the schema requires a context arg you can still pass a partial one via `context`.

Input parameters:

- `context` (object): Optional partial context, inlined as the `context` arg if the schema requires it.
- `selection` (string, required): GraphQL selection of flag fields under root, e.g. `exampleFlag`.

### `hypertune_query` (~132 tokens)

Run a raw GraphQL query

Run an arbitrary GraphQL query (and optional variables) against the Hypertune edge endpoint. Power-user escape hatch for full control — each Hypertune project has its own generated schema, so this handles any flag shape, nested selections, inline enum literals, or variables the convenience tools can't express. The query root field is `root(context: ...)`.

Input parameters:

- `query` (string, required): A complete GraphQL query string, e.g. `query { root(context: {environment: "production"}) { myFlag } }`.
- `variables` (object): Optional GraphQL variables object matching the query's declared variables.

### `hypertune_introspect` (~72 tokens)

Introspect the GraphQL schema

Run a GraphQL introspection query to discover the project's schema — all types and fields, including the available flags and the shape of the evaluation context. Best-effort: some edge deployments disable introspection, in which case this returns a clear error (use hypertune_query with a known flag name instead).

### `hypertune_list_flags` (~63 tokens)

List feature flags

List the project's top-level feature flags (the fields of the query root type) with their return types and descriptions, derived from GraphQL introspection. A convenient first call to see what flags exist before evaluating. Requires introspection to be enabled on the edge endpoint.

## Diagnostics

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

## Score history

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

## Links

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