# Hesperan (remote · api.hesperan.com)

Calibrated decisions for agents: choice, yes/no and score questions answered with probabilities.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `api.hesperan.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-hesperan-mcp/api.md), [page](https://verifymcp.io/servers/com-hesperan-mcp/api)
- npm · `hesperan-mcp`: 64/100, [markdown](https://verifymcp.io/servers/com-hesperan-mcp/hesperan-mcp.md), [page](https://verifymcp.io/servers/com-hesperan-mcp/hesperan-mcp)

## Channel facts

- Endpoint: `https://api.hesperan.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.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-09-25.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 683 tokens (~227/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Hesperan MCP server?

Hesperan is a hosted endpoint at https://api.hesperan.com/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.

### Claude

```bash
claude mcp add --transport http com-hesperan-mcp 'https://api.hesperan.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hesperan-mcp": {
      "url": "https://api.hesperan.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hesperan-mcp": {
      "type": "http",
      "url": "https://api.hesperan.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hesperan-mcp]
url = "https://api.hesperan.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hesperan-mcp": {
      "type": "remote",
      "url": "https://api.hesperan.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hesperan-mcp --url 'https://api.hesperan.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hesperan-mcp:
    url: "https://api.hesperan.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hesperan-mcp": {
      "Transport": "http",
      "Url": "https://api.hesperan.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hesperan-mcp -t streamable-http -u 'https://api.hesperan.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-hesperan-mcp": {
      "type": "http",
      "url": "https://api.hesperan.com/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-09-25 (score 74, 0)

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

### 2026-09-24 (score 74)

First indexed and scored.

## MCP tools (3)

### `decide` (~216 tokens)

Decide with Hesperan

Ask Hesperan 1 one or more typed questions about a state and get a probability for every possible answer. Types: choice (pick one of named options), noul (probability that a statement is true), score (level on an ordinal scale). Use for decisions with known options: routing, triage, policy or risk checks, "should I proceed?". Not for writing text, summaries or knowledge questions. Ask all questions about the same state in one call: billing is by input tokens (the state once plus each question once), from the user's monthly allowance and then their prepaid balance; failed calls are free.

Input parameters:

- `questions` (object, required): Named questions, answered together: { "<name>": { "type": "choice" | "noul" | "score", "instructions": "...", "criteria": ... } }.
- `state` (required): The situation to judge: free text, or a JSON object (keeps dates, amounts and fields unambiguous). Leave out data that does not matter for the question.

### `decide_with_profile` (~249 tokens)

Decide with a calibrated profile

Run one of the user's decision profiles on a state. A profile is one question calibrated on the user's own labelled cases with a target precision; the answer is a decision, its calibrated confidence and an action: "auto" (confidence reaches the profile's threshold — act on it) or "review" (hand it to a person). Profiles are created in the Hesperan console; ask the user for the profile slug. Keep the returned decision_id to report the correct answer later with report_outcome. Billed by input tokens like decide; pass an idempotency_key to make retries safe (a repeat with the same key returns the first decision without charging again).

Input parameters:

- `idempotency_key` (string): Optional unique key for this decision (1-255 visible ASCII characters, e.g. the ticket id). Reusing it within 24 hours with the same state replays the stored decision.
- `profile` (string, required): Slug of the decision profile, e.g. "ticket-routing".
- `state` (required): The situation to judge: free text, or a JSON object (keeps dates, amounts and fields unambiguous). Leave out data that does not matter for the question.

### `report_outcome` (~90 tokens)

Report the correct answer

Record the correct answer for an earlier decide_with_profile decision, once it is known (e.g. the team that finally handled the ticket). This tracks the live precision of the profile in the console. actual must be one of the profile's option keys. Free of charge.

Input parameters:

- `actual` (string, required): The correct option key.
- `decision_id` (string, required): decision_id returned by decide_with_profile.

## Diagnostics

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

## Score history

- 2026-09-25: 74
- 2026-09-24: 74

## Common questions

### What is the Hesperan MCP server?

Hesperan is an MCP server listed in the public MCP registry as com.hesperan/mcp. Calibrated decisions for agents: choice, yes/no and score questions answered with probabilities. This page covers its hosted endpoint (https://api.hesperan.com/mcp).

### Is the Hesperan MCP server safe to use?

Hesperan scores 74 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 Hesperan MCP server expose?

Hesperan exposes 3 tools: decide, decide_with_profile, report_outcome. Their descriptions and schemas cost roughly 555 tokens of context every time the server is loaded.

### Does the Hesperan MCP server require authentication?

Yes. Hesperan 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 Hesperan MCP server still maintained?

Hesperan is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.hesperan.com/mcp
- Authorisation metadata: https://api.hesperan.com/.well-known/oauth-protected-resource/mcp
- Website: https://hesperan.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-hesperan-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hesperan-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/com-hesperan-mcp/api