# Fittest (remote · fittest-mcp.westus2.cloudapp.azure.com)

Three ML interatomic potentials check a molecule: trust (Beta-posterior score, 90% CI) or DFT.

- Trust score: 46/100 (low)
- Registry status: active
- Liveness: degraded
- Owner verified: no
- Last scored: 2026-11-05

> **Degraded**: one or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

## Components

- remote · `fittest-mcp.westus2.cloudapp.azure.com`: 46/100 (this document), [markdown](https://verifymcp.io/servers/pavel-tk-fittest/fittest-mcp.md), [page](https://verifymcp.io/servers/pavel-tk-fittest/fittest-mcp)

## Channel facts

- Endpoint: `https://fittest-mcp.westus2.cloudapp.azure.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## 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-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

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

Fittest is a hosted endpoint at https://fittest-mcp.westus2.cloudapp.azure.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 pavel-tk-fittest 'https://fittest-mcp.westus2.cloudapp.azure.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "pavel-tk-fittest": {
      "url": "https://fittest-mcp.westus2.cloudapp.azure.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pavel-tk-fittest": {
      "type": "http",
      "url": "https://fittest-mcp.westus2.cloudapp.azure.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.pavel-tk-fittest]
url = "https://fittest-mcp.westus2.cloudapp.azure.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pavel-tk-fittest": {
      "type": "remote",
      "url": "https://fittest-mcp.westus2.cloudapp.azure.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pavel-tk-fittest --url 'https://fittest-mcp.westus2.cloudapp.azure.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pavel-tk-fittest:
    url: "https://fittest-mcp.westus2.cloudapp.azure.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "pavel-tk-fittest": {
      "Transport": "http",
      "Url": "https://fittest-mcp.westus2.cloudapp.azure.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add pavel-tk-fittest -t streamable-http -u 'https://fittest-mcp.westus2.cloudapp.azure.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "pavel-tk-fittest": {
      "type": "http",
      "url": "https://fittest-mcp.westus2.cloudapp.azure.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-11-05 (score 46, −12)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-03 (score 58, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-02 (score 58, +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-11-01 (score 57, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 57)

First indexed and scored.

## MCP tools (4)

### `check_structures` (~543 tokens)

Ask the Fittest swarm whether a machine-learned interatomic potential can be trusted on your molecular structures, or whether they need DFT. Three model agents (MACE-MPA-0, AIMNet2, Orb-v3) predict forces; their disagreement sigma_F and the Calibrator's DFT-label ledger give the verdict.

Input `structures`: XYZ text (single or multi-frame; bare 'El x y z' atoms on separate lines or separated by commas/semicolons also work) and/or a list of objects {"Z": [8,1,1] or "symbols": ["O","H","H"], "R": [[x,y,z], ...]} in Angstrom. Exact element symbols only. Limits: <= 20 structures per call, 2..100 atoms each, isolated molecules (no periodic cells). Elements the full committee supports: H B C N O F Si P S Cl As Se Br I.

Returns per structure: verdict (trust / send_to_dft) with verdict_reasons, trust_score (Beta posterior P(correct), never exactly 1) with its 90% interval and labels_behind_score, the recommended model or blend, served and reference energy (eV; compare reference_energy_eV across a batch), max/mean force (eV/A), sigma_F vs tau, per-model summary, domain_warning outside C/H/N/O or Transition1x sizes. A bad structure gets its own error entry; the rest are still scored. Rule: trust only if: every model agent supports all elements, the forces do not all vanish, sigma_F < tau, and trust_score >= 0.5. Otherwise send_to_dft, with verdict_reasons. tau is a fixed escalation threshold: the 70th percentile of sigma_F on the round-0 pool. The Calibrator's threshold rule never moved it during the run (see results/RESULTS.md).

Logging: every call to this server is logged (UTC time, tool name, an anonymous client id = salted hash of client name + IP), structure and atom counts, verdict counts, latency and ok/error category. Raw IPs are not stored by the app or written to the access log; since 2026-10-31 19:11 UTC Caddy's error/unmapped-host logs drop them too (before that, some Caddy error and bare-IP entries in the system journal contained client IPs, kept until journa…

Input parameters:

- `include_forces` (boolean)
- `structures` (required)

### `explain` (~205 tokens)

Explain why Fittest trusted or escalated ONE structure (XYZ text or {Z|symbols, R}): the verdict rule applied, sigma_F vs tau, the Calibrator bucket with its label count, the posterior P(correct) of every candidate in it, which model agents disagree most, and the most uncertain atoms.

Logging: every call to this server is logged (UTC time, tool name, an anonymous client id = salted hash of client name + IP), structure and atom counts, verdict counts, latency and ok/error category. Raw IPs are not stored by the app or written to the access log; since 2026-10-31 19:11 UTC Caddy's error/unmapped-host logs drop them too (before that, some Caddy error and bare-IP entries in the system journal contained client IPs, kept until journal rotation). Structures, coordinates, element lists and names are NOT stored. Aggregate counts are public at /stats.

Input parameters:

- `structure` (required)

### `swarm_status` (~186 tokens)

Show the Fittest population: model agents (answerers) and the Skeptic (critic) with reputations from the ledger, the calibration domain, tau and the verdict rule, which models are live, and the evolution family trees if published.

Logging: every call to this server is logged (UTC time, tool name, an anonymous client id = salted hash of client name + IP), structure and atom counts, verdict counts, latency and ok/error category. Raw IPs are not stored by the app or written to the access log; since 2026-10-31 19:11 UTC Caddy's error/unmapped-host logs drop them too (before that, some Caddy error and bare-IP entries in the system journal contained client IPs, kept until journal rotation). Structures, coordinates, element lists and names are NOT stored. Aggregate counts are public at /stats.

### `usage_stats` (~179 tokens)

Aggregate usage of this server: distinct users (anonymous clients that got at least one structure verdict; internal test clients excluded), total calls, calls per tool, first/last call time. No per-user data.

Logging: every call to this server is logged (UTC time, tool name, an anonymous client id = salted hash of client name + IP), structure and atom counts, verdict counts, latency and ok/error category. Raw IPs are not stored by the app or written to the access log; since 2026-10-31 19:11 UTC Caddy's error/unmapped-host logs drop them too (before that, some Caddy error and bare-IP entries in the system journal contained client IPs, kept until journal rotation). Structures, coordinates, element lists and names are NOT stored. Aggregate counts are public at /stats.

## Diagnostics

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

## Score history

- 2026-11-05: 46
- 2026-11-04: 58
- 2026-11-03: 58
- 2026-11-02: 58
- 2026-11-01: 57
- 2026-10-31: 57

## Common questions

### What is the Fittest MCP server?

Fittest is an MCP server listed in the public MCP registry as io.github.Pavel-Tk/fittest. Three ML interatomic potentials check a molecule: trust (Beta-posterior score, 90% CI) or DFT. This page covers its hosted endpoint (https://fittest-mcp.westus2.cloudapp.azure.com/mcp).

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

Fittest scores 46 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 Fittest MCP server expose?

Fittest exposes 4 tools: check_structures, explain, swarm_status, usage_stats. Their descriptions and schemas cost roughly 1,113 tokens of context every time the server is loaded.

### Does the Fittest MCP server require authentication?

Its publisher declares no required credentials for Fittest. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Fittest MCP server still maintained?

Fittest is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 2 November 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://fittest-mcp.westus2.cloudapp.azure.com/mcp
- Repository: https://github.com/Pavel-Tk/fittest
- Website: https://fittest-mcp.westus2.cloudapp.azure.com/
- Changelog RSS feed: https://verifymcp.io/servers/pavel-tk-fittest/fittest-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/pavel-tk-fittest/fittest-mcp.json
- HTML version of this page: https://verifymcp.io/servers/pavel-tk-fittest/fittest-mcp