Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hesperan

NPM · HESPERAN-MCP · 2 COMPONENTS · SCANNED SEP 25

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

Available components

remote · api.hesperan.com 74 npm · hesperan-mcp 64
64 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the Hesperan MCP server?

Hesperan runs locally as an npm package, launched with npx -y hesperan-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · hesperan-mcp

# add to Claude Code
claude mcp add com-hesperan-mcp -- npx -y hesperan-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-hesperan-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hesperan-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-hesperan-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hesperan-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-hesperan-mcp -- npx -y hesperan-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hesperan-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "hesperan-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-hesperan-mcp --command npx --arg -y --arg hesperan-mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-hesperan-mcp:
    command: "npx"
    args: ["-y", "hesperan-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-hesperan-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "hesperan-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-hesperan-mcp -t stdio -c npx -a -y hesperan-mcp
// mcp.json
{
  "mcpServers": {
    "com-hesperan-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hesperan-mcp"
      ]
    }
  }
}
Changelog

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.

  • 25 Sept 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
  • 24 Sept 26 64

    First indexed and scored.

Diagnostics

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 25 Sept 2026 · Analysed npm/hesperan-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~555 tokens

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 →

Tool Tokens
decide ~216

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.

NameTypeReqDescription
questionsobjectyesNamed questions, answered together: { "<name>": { "type": "choice" | "noul" | "score", "instructions": "...", "criteria": ... } }.
state–yesThe 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.

No output schema declared.

No examples provided.

decide_with_profile ~249

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).

NameTypeReqDescription
idempotency_keystring–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.
profilestringyesSlug of the decision profile, e.g. "ticket-routing".
state–yesThe 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.

No output schema declared.

No examples provided.

report_outcome ~90

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.

NameTypeReqDescription
actualstringyesThe correct option key.
decision_idstringyesdecision_id returned by decide_with_profile.

No output schema declared.

No examples provided.

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 npm package (hesperan-mcp).

Is the Hesperan MCP server safe to use?

Hesperan scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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.

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.

What licence is the Hesperan MCP server under?

Hesperan declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.