Skip to content

Hypertune MCP by usefulapi

io.usefulapi/hypertuneusefulapi.iostreamable-httpv1.40.4Scanned

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

5 tools: 3 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 3 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 3 findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Hypertune MCP by usefulapi can do

The Hypertune MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 5 tools. It can create or change data (3 tools: hypertune_evaluate, hypertune_query and hypertune_introspect), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 3Claude Code: ask
  • hypertune_evaluateEvaluate one or more feature flags for a given context and get their resolved values.1 finding

    Why it is in this group

    • 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

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

      Matched text

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

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Evaluate feature flags
    • readOnlyHint: true
  • hypertune_introspectRun 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.1 finding

    Why it is in this group

    • 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

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

      Matched text

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

      What this check looks for
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Introspect the GraphQL schema
    • readOnlyHint: true
  • hypertune_queryRun an arbitrary GraphQL query (and optional variables) against the Hypertune edge endpoint.1 finding

    Why it is in this group

    • 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

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

      Matched text

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

      What this check looks for
    Description, as the server wrote it
    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: ...)`.

    Annotations the server declares

    • title: Run a raw GraphQL query
    • readOnlyHint: true
Only reads 2Show 2 read-only tools
  • hypertune_get_logicFetch the underlying LOGIC of flags without reducing them — i.e.No findings

    Why it is in this group

    • The name "hypertune_get_logic" says "get": a word for reading.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • title: Get flag logic (unreduced)
    • readOnlyHint: true
  • hypertune_list_flagsList the project's top-level feature flags (the fields of the query root type) with their return types and descriptions, derived from GraphQL introspection.No findings

    Why it is in this group

    • The name "hypertune_list_flags" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List feature flags
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

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

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://hypertune.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://hypertune.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

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

    What this check looks for
  • The server marks "hypertune_query" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

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

    What this check looks for
  • The server marks "hypertune_introspect" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

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

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://hypertune.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://hypertune.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http hypertune https://hypertune.usefulapi.io/mcp
claude mcp add --transport http hypertune https://hypertune.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.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": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hypertune. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/hypertune/verify?hash=7fbb5d4642acf260e7551d3582c9a581a94f8a1581310b8c01549632e6d8581c" | jq -e '.changed == false'

Pinned hash 7fbb5d4642ac, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/hypertune/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/hypertune
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/hypertune.svg)](https://radar.anlyon.com/servers/io.usefulapi/hypertune)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Hypertune MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Hypertune MCP by usefulapi safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Hypertune MCP by usefulapi delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Hypertune MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Hypertune MCP by usefulapi have?

5 tools: 3 write, 2 read. hypertune_evaluate, hypertune_query, hypertune_introspect, hypertune_get_logic and hypertune_list_flags.

Does the Hypertune MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Hypertune MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Hypertune MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.