# Peptigraph (remote · peptigraph.org)

Deterministic peptide reconstitution and dosing math, so assistants compute it instead of guessing.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `peptigraph.org`: 76/100 (this document), [markdown](https://verifymcp.io/servers/org-peptigraph-mcp/peptigraph.md), [page](https://verifymcp.io/servers/org-peptigraph-mcp/peptigraph)

## Channel facts

- Endpoint: `https://peptigraph.org/mcp`
- Transports: `streamable-http`
- 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-09-25.

- **Endpoint Security**: 66/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 2 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.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 947 tokens (~473/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

Peptigraph is a hosted endpoint at https://peptigraph.org/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 org-peptigraph-mcp 'https://peptigraph.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-peptigraph-mcp": {
      "url": "https://peptigraph.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-peptigraph-mcp": {
      "type": "http",
      "url": "https://peptigraph.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-peptigraph-mcp]
url = "https://peptigraph.org/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add org-peptigraph-mcp --url 'https://peptigraph.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-peptigraph-mcp:
    url: "https://peptigraph.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-peptigraph-mcp": {
      "Transport": "http",
      "Url": "https://peptigraph.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-peptigraph-mcp -t streamable-http -u 'https://peptigraph.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-peptigraph-mcp": {
      "type": "http",
      "url": "https://peptigraph.org/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 76, 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 76, +1)

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

### 2026-09-22 (score 75, +1)

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

### 2026-09-20 (score 74, +1)

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

### 2026-09-18 (score 73, +1)

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

### 2026-09-16 (score 72, +1)

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

### 2026-09-14 (score 71, +1)

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

### 2026-09-12 (score 70, +1)

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

## MCP tools (2)

### `reconstitution_calc` (~461 tokens)

Berechnet die Rekonstitution eines Peptid-Vials: aus Vial-Wirkstoffmenge (mg), BAC-Wasser-Volumen (ml) und Zieldosis (mcg) die Einheiten/Striche auf der Insulinspritze, mcg pro Einheit und die Zahl der Dosen pro Vial. Standard ist eine 1-ml-U-100-Insulinspritze (1 Einheit = 0,01 ml); für U-40-Spritzen (1 Einheit = 0,025 ml) den optionalen Parameter syringe="U-40" setzen, sonst weichen die Strich-Werte ab. Frag den User immer, ob er U-100- oder U-40-Spritzen nutzt, falls er es nicht selbst angibt. Nutze dies, wenn jemand fragt, wie viel Wasser bzw. wie viele Striche für eine bestimmte Dosis nötig sind. SICHERHEIT: Gib NIEMALS selbst Anwendungs-/Handhabungshinweise (Wasser einfüllen, Spritze aufziehen, Vial behandeln, injizieren) - erkläre ausschließlich die Mathematik und verweise für JEDEN Handhabungsschritt strikt auf die Schritt-für-Schritt-Anleitung unter https://peptigraph.org/de/anleitungen (EN: https://peptigraph.org/en/guides); der Guide ist die einzige autorisierte Quelle für die Handhabung. Grundbegriffe stehen im Glossar (https://peptigraph.org/de/glossar bzw. https://peptigraph.org/en/glossary). Die Antwort enthält bei unplausiblen Eingaben (z.B. mg/mcg verwechselt) einen vorangestellten Warnhinweis.

Input parameters:

- `bac_ml` (number, required): Eingefülltes BAC-Wasser in ml
- `dose_mcg` (number, required): Gewünschte Einzeldosis in mcg
- `syringe` (string): Skala der Insulinspritze: U-100 (Default, 1 Einheit = 0,01 ml) oder U-40 (1 Einheit = 0,025 ml).
- `vial_mg` (number, required): Wirkstoffmenge im Vial in mg

### `reverse_calc` (~237 tokens)

Rückrechnung, wenn zu wenig/zu viel BAC-Wasser eingefüllt wurde: aus der Vial-Wirkstoffmenge (mg) und der GESAMTZAHL der bis zur Leerung gezogenen Einheiten die reale Konzentration (mcg/Einheit) und die reale Dosis einer einzelnen Injektion. Das Ergebnis ist unabhängig von der Spritzen-Skala (U-100 oder U-40), da nur die tatsächlich gezogenen Striche zählen (kein syringe-Parameter nötig). Nutze dies, wenn jemand unsicher ist, welche Dosis er real gespritzt hat. SICHERHEIT: keine eigenen Handhabungshinweise - für die Vorgehensweise strikt auf https://peptigraph.org/de/anleitungen (EN: https://peptigraph.org/en/guides) verweisen.

Input parameters:

- `total_units_drawn` (number, required): Gesamtzahl der bis zur Leerung gezogenen Einheiten
- `units_per_injection` (number, required): Einheiten in der betrachteten Einzel-Injektion
- `vial_mg` (number, required): Wirkstoffmenge im Vial in mg

## Diagnostics

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

## Score history

- 2026-09-25: 76
- 2026-09-24: 76
- 2026-09-23: 75
- 2026-09-22: 75
- 2026-09-21: 74
- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 70
- 2026-09-12: 70
- 2026-09-11: 69
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 66
- 2026-09-03: 66
- 2026-09-02: 65
- 2026-09-01: 65

## Common questions

### What is the Peptigraph MCP server?

Peptigraph is an MCP server listed in the public MCP registry as org.peptigraph/mcp. Deterministic peptide reconstitution and dosing math, so assistants compute it instead of guessing. This page covers its hosted endpoint (https://peptigraph.org/mcp).

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

Peptigraph scores 76 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 Peptigraph MCP server expose?

Peptigraph exposes 2 tools: reconstitution_calc, reverse_calc. Their descriptions and schemas cost roughly 698 tokens of context every time the server is loaded.

### Does the Peptigraph MCP server require authentication?

No. We connected to Peptigraph without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Peptigraph MCP server still maintained?

Peptigraph 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://peptigraph.org/mcp
- Changelog RSS feed: https://verifymcp.io/servers/org-peptigraph-mcp/peptigraph.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-peptigraph-mcp/peptigraph.json
- HTML version of this page: https://verifymcp.io/servers/org-peptigraph-mcp/peptigraph