io.usefulapi/hypertune
REMOTE · HYPERTUNE.USEFULAPI.IO · SCANNED SEP 20
Evaluate and inspect your Hypertune feature flags from your AI assistant.
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 Usability81
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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/hypertune MCP server?
io.usefulapi/hypertune is a hosted endpoint at https://hypertune.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 · hypertune.usefulapi.io
claude mcp add --transport http io-usefulapi-hypertune 'https://hypertune.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-hypertune": {
"url": "https://hypertune.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-hypertune": {
"type": "http",
"url": "https://hypertune.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-hypertune] url = "https://hypertune.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-hypertune": {
"type": "remote",
"url": "https://hypertune.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-hypertune --url 'https://hypertune.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-hypertune:
url: "https://hypertune.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-hypertune": {
"Transport": "http",
"Url": "https://hypertune.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-hypertune -t streamable-http -u 'https://hypertune.usefulapi.io/mcp'
{
"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.
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.
- 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
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://hypertune.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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a2a4e773ffaf67d70ef14f9b8e964722 |
| SANs: usefulapi.io, hypertune.usefulapi.io, *.hypertune.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 hypertune.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://hypertune.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://hypertune.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://hypertune.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://hypertune.usefulapi.io/mcp |
| Authorisation server | https://hypertune.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hypertune.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://hypertune.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 →
hypertune_evaluate Evaluate feature flags ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | GraphQL selection of flag fields under root, e.g. `exampleFlag` or `homePage { showBanner } exampleFlag`. |
No output schema declared.
No examples provided.
hypertune_get_logic Get flag logic (unreduced) ~127
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | Optional partial context, inlined as the `context` arg if the schema requires it. |
| selection | string | yes | GraphQL selection of flag fields under root, e.g. `exampleFlag`. |
No output schema declared.
No examples provided.
hypertune_introspect Introspect the GraphQL schema ~72
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hypertune_list_flags List feature flags ~63
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hypertune_query Run a raw GraphQL query ~132
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: ...)`.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 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. |
No output schema declared.
No examples provided.
What is the io.usefulapi/hypertune MCP server?
io.usefulapi/hypertune is an MCP server listed in the public MCP registry as io.usefulapi/hypertune. Evaluate and inspect your Hypertune feature flags from your AI assistant. This page covers its hosted endpoint (https://hypertune.usefulapi.io/mcp).
Is the io.usefulapi/hypertune MCP server safe to use?
io.usefulapi/hypertune 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/hypertune MCP server expose?
io.usefulapi/hypertune exposes 5 tools: hypertune_evaluate, hypertune_get_logic, hypertune_query, hypertune_introspect, hypertune_list_flags. Their descriptions and schemas cost roughly 607 tokens of context every time the server is loaded.
Does the io.usefulapi/hypertune MCP server require authentication?
Yes. io.usefulapi/hypertune 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/hypertune MCP server still maintained?
io.usefulapi/hypertune 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.