Peptigraph
REMOTE · PEPTIGRAPH.ORG · SCANNED SEP 25
Deterministic peptide reconstitution and dosing math, so assistants compute it instead of guessing.
Available components
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. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · peptigraph.org
claude mcp add --transport http org-peptigraph-mcp 'https://peptigraph.org/mcp'
{
"mcpServers": {
"org-peptigraph-mcp": {
"url": "https://peptigraph.org/mcp"
}
}
} {
"servers": {
"org-peptigraph-mcp": {
"type": "http",
"url": "https://peptigraph.org/mcp"
}
}
} [mcp_servers.org-peptigraph-mcp] url = "https://peptigraph.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-peptigraph-mcp": {
"type": "remote",
"url": "https://peptigraph.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-peptigraph-mcp --url 'https://peptigraph.org/mcp' --transport streamable-http
mcp_servers:
org-peptigraph-mcp:
url: "https://peptigraph.org/mcp" {
"McpServers": {
"org-peptigraph-mcp": {
"Transport": "http",
"Url": "https://peptigraph.org/mcp"
}
}
} assistant mcp add org-peptigraph-mcp -t streamable-http -u 'https://peptigraph.org/mcp'
{
"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.
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 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
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 · Probed https://peptigraph.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=peptigraph.org | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f08ded79b3950da40e0c1a89b6b42ffb |
| SANs: peptigraph.org, *.peptigraph.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of peptigraph.org. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| peptigraph.org. | present | 2371 | 13 | Verified |
| peptigraph.org. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'sha256-I9Kc4bF6L7ow8R7TwnESkjngPJYIFZonD5/L9b32RPw=' 'wasm-unsafe-eval'; worker-src 'self' blob: 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'; connect-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://peptigraph.org/mcp | Verified | 200 | |
| http (plaintext) | http://peptigraph.org/mcp | HTTPS enforced | 301 | https://peptigraph.org/mcp |
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 →
reconstitution_calc ~461
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bac_ml | number | yes | Eingefülltes BAC-Wasser in ml |
| dose_mcg | number | yes | 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 | yes | Wirkstoffmenge im Vial in mg |
No output schema declared.
No examples provided.
reverse_calc ~237
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.
| Name | Type | Req | Description |
|---|---|---|---|
| total_units_drawn | number | yes | Gesamtzahl der bis zur Leerung gezogenen Einheiten |
| units_per_injection | number | yes | Einheiten in der betrachteten Einzel-Injektion |
| vial_mg | number | yes | Wirkstoffmenge im Vial in mg |
No output schema declared.
No examples provided.
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.