# `io.usefulapi/hypertune` on anlyon.dev

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by anlyon.dev. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://anlyon.dev/servers/io.usefulapi/hypertune
- JSON: https://anlyon.dev/api/v1/servers/io.usefulapi/hypertune
- Version: 1.17.0 (active)
- Publisher: io.usefulapi (domain proven to the MCP Registry)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Repository: https://github.com/m190/usefulapi-mcp
- Metadata from the official MCP Registry, synced 2026-10-23T08:18:43.317Z

Title and description, as the publisher wrote them:

```untrusted-server-text
Hypertune MCP by usefulapi
Evaluate and inspect your Hypertune feature flags from your AI assistant.
```

Scanned 2026-10-23T08:20:56.666Z over streamable-http.

**5 tools: 3 change things and 2 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 3 | ask |
| Only reads | read | 2 | allow |

## Exfil surface

No private-data -> untrusted-input -> outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | none |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | none |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | none |

## Findings

- **warn** Annotations that disagree with the tool in `hypertune_evaluate` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "hypertune_evaluate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true}; The name "hypertune_evaluate" says "evaluate": a word for a change.
```

- **warn** Annotations that disagree with the tool in `hypertune_query` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "hypertune_query" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true}; The name "hypertune_query" says "query": a word for reading.
```

- **warn** Annotations that disagree with the tool in `hypertune_introspect` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "hypertune_introspect" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true}; The description's first verb is "run": a word for a change.
```


## Changes things (3)

Creates or changes something that can be changed back. Claude Code: ask.

### `hypertune_evaluate`

- The name "hypertune_evaluate" says "evaluate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
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.
```

### `hypertune_introspect`

- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
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_query`

- The name "hypertune_query" says "query": a word for reading.
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
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: ...)`.
```

## Only reads (2)

Looks things up and changes nothing. Claude Code: allow.

### `hypertune_get_logic`

- The name "hypertune_get_logic" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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`.
```

### `hypertune_list_flags`

- The name "hypertune_list_flags" says "list": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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.
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `hypertune`:

```json
{
  "permissions": {
    "allow": [
      "mcp__hypertune__hypertune_get_logic",
      "mcp__hypertune__hypertune_list_flags"
    ],
    "ask": [
      "mcp__hypertune__hypertune_evaluate",
      "mcp__hypertune__hypertune_query",
      "mcp__hypertune__hypertune_introspect"
    ],
    "deny": []
  }
}
```

## Remote posture

What an anonymous client saw at the remote endpoint, last 2026-10-22T15:29:21.718Z, unchanged since 2026-10-22T15:29:21.718Z. No credentials were sent and no tool was called. Values are shown as the endpoint returned them. Method: https://anlyon.dev/methodology#remote-posture

| Fact | Observed |
| --- | --- |
| Reachable | `yes` |
| HTTP status of an anonymous initialize | `200` |
| tools/list served without credentials | `yes` |
| Tools that change things, listed without credentials | `3` |
| Protocol version | `2025-06-18` |
| WWW-Authenticate on 401 | `not observed` |
| resource_metadata in WWW-Authenticate | `none` |
| RFC 9728 protected resource metadata | `https://hypertune.usefulapi.io/.well-known/oauth-protected-resource/mcp` |
| Authorization servers | `https://hypertune.usefulapi.io` |
| Legacy HTTP+SSE transport | `no` |
| Dynamic client registration | `yes` |
| Client ID metadata documents | `no` |

- **warn** Tools that change things, listed to anyone ([unauth-remote-writes](https://anlyon.dev/methodology#unauth-remote-writes))

```untrusted-server-text
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

https://hypertune.usefulapi.io/mcp: tools/list returned 5 tools to an anonymous client, including hypertune_evaluate (write), hypertune_query (write), hypertune_introspect (write)
```