# io.github.Kromatic-Innovation/fermi (remote · fermi.krobar.ai)

Calibrated probability distributions from natural-language questions via REST and MCP.

- Trust score: 54/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `fermi.krobar.ai`: 54/100 (this document), [markdown](https://verifymcp.io/servers/kromatic-innovation-fermi/fermi.md), [page](https://verifymcp.io/servers/kromatic-innovation-fermi/fermi)

## Channel facts

- Endpoint: `https://fermi.krobar.ai/mcp/sse/`
- Transports: `sse`
- Auth: `none`
- Version: `1.0.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-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 40/100
  - Verified sse transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 976 tokens (~325/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**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http kromatic-innovation-fermi https://fermi.krobar.ai/mcp/sse/
```

### Codex

```toml
[mcp_servers.kromatic-innovation-fermi]
url = "https://fermi.krobar.ai/mcp/sse/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kromatic-innovation-fermi": {
      "type": "remote",
      "url": "https://fermi.krobar.ai/mcp/sse/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kromatic-innovation-fermi --url https://fermi.krobar.ai/mcp/sse/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kromatic-innovation-fermi:
    url: "https://fermi.krobar.ai/mcp/sse/"
```

### Other

```json
{
  "mcpServers": {
    "kromatic-innovation-fermi": {
      "type": "http",
      "url": "https://fermi.krobar.ai/mcp/sse/"
    }
  }
}
```

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-08-03 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 52, +2)

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

### 2026-07-30 (score 50, −2)

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

### 2026-07-29 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 50, 0)

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

### 2026-07-26 (score 50)

First indexed and scored.

## MCP tools (3)

### `estimate` (~568 tokens)

Return a calibrated probability distribution for a natural-language question.

    Args:
        question: The natural-language question (e.g. "What will the price of
            Bitcoin be in 6 months?").
        unit: The unit the answer should be expressed in (e.g. "USD", "people",
            "meters").
        target_horizon: When the estimate applies (e.g. "6 months", "2030",
            "current").
        disclaimer_acknowledged: Must be true. Confirms you understand estimates
            are probabilistic decision-support only, not financial/medical/legal
            advice.
        requested_tier_id: Tier (1=fast sync, 2=grounded sync, 3=deep research
            async). Default 1.
        context: Optional extra context to condition the estimate.
        coverage_probability: Width of the confidence interval (0, 1). Default
            0.9 (90% CI).
        source_inputs: Optional list of structured inputs (files, tables) for
            the model to consider. Each item needs source_type
            ("qualitative_text", "spreadsheet", or "structured_file") and
            either content (text) or structured_data (dict/list).
        callback_url: Optional webhook URL. When set, the completed or failed
            result is POSTed here with an HMAC signature, so you don't need
            to poll for async tiers.
        api_key: Your Fermi API key from POST /api/v1/accounts. Omit to use the
            anonymous tier.
        provider: Optional LLM provider selector ("openai" or "anthropic").
            When omitted the server uses its configured default. Tier 1
            supports both providers; tiers 2-3 currently accept "openai" only.
        model: Optional model id for the selected provider. Must match the
            model configured for (tier_id, provider); omit to accept the
            default.

    Returns:
        EstimateSuccessResponse as a dict: estimation_interval, distribution_family,
        distribution_parameters, point_estimate, re…

Input parameters:

- `api_key`
- `callback_url`
- `context`
- `coverage_probability` (number)
- `disclaimer_acknowledged` (boolean, required)
- `model`
- `provider`
- `question` (string, required)
- `requested_tier_id` (integer)
- `source_inputs`
- `target_horizon` (string, required)
- `unit` (string, required)

### `feedback` (~193 tokens)

Submit feedback, a feature request, or a bug report to the Fermi team.

    An email is sent to the team and a copy is sent to the address you provide.

    Args:
        feedback_type: One of "feedback", "feature_request", or "bug".
        message: Your feedback or request (10-5000 characters). Be specific.
        sender_email: Your email address. A confirmation copy is sent here.
        sender_name: Your name (optional).
        api_key: Your Fermi API key (optional). If provided, your account ID
            is attached to the message for context.

    Returns:
        Confirmation with status "sent".

    Raises:
        ValueError: if validation fails or email delivery fails.

Input parameters:

- `api_key`
- `feedback_type` (string, required)
- `message` (string, required)
- `sender_email` (string, required)
- `sender_name`

### `buy_credits` (~153 tokens)

Purchase credits using a saved payment method (off-session).

    Requires a prior Stripe Checkout session to have saved a card.
    Credits are $0.50 each. Use GET /api/v1/billing/pricing to confirm
    the current price.

    Args:
        credits: Number of credits to purchase (minimum 1).
        api_key: Your Fermi API key from POST /api/v1/accounts. Required.

    Returns:
        Dict with credits_purchased, new_balance, and payment_status.

    Raises:
        ValueError: if authentication fails, no payment method is on file,
            or the card is declined.

Input parameters:

- `api_key` (string, required)
- `credits` (integer, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kromatic-innovation-fermi/fermi#diagnostics

## Score history

- 2026-08-03: 54
- 2026-08-02: 53
- 2026-08-01: 53
- 2026-07-31: 52
- 2026-07-30: 50
- 2026-07-29: 52
- 2026-07-28: 51
- 2026-07-27: 50
- 2026-07-26: 50

## Links

- Remote endpoint: https://fermi.krobar.ai/mcp/sse/
- Repository: https://github.com/Kromatic-Innovation/fermi
- Changelog RSS feed: https://verifymcp.io/servers/kromatic-innovation-fermi/fermi/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/kromatic-innovation-fermi/fermi/changelog.json
- HTML version of this page: https://verifymcp.io/servers/kromatic-innovation-fermi/fermi