ImmunoGraph MCP
OCI · GHCR.IO/AJEY95/IMMUNO-GRAPH
Provenance-aware computational epitope research tools with reproducible offline demonstrations.
Available components
Last scanned (3 hours ago)
Scores higher than 41% of OCI servers
Category Health and Science
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 7653 tokens (~166/item across 46 items; 46 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 Management17
- Stability observed for 5 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_duplicate_candidates" implies "remove" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 46 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.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +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.
- 31 Oct 26 38
First indexed and scored.
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 5 Nov 2026 · Analysed oci/ghcr.io/ajey95/immuno-graph@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
validate_docking_box ~140
Validate the center and size of a proposed docking search box and calculate its volume. Use before run_docking to catch invalid box geometry; this does not run Vina or establish a binding site. Returns validated dimensions or a structured validation failure.
| Name | Type | Req | Description |
|---|---|---|---|
| center | object | yes | Docking-box center coordinates x, y, and z in angstroms. |
| dockingBoxId | string | yes | Caller-chosen identifier for the validated docking search box. |
| runId | string | yes | Caller-chosen identifier linking this call to one research run. |
| size | object | yes | Docking-box edge lengths x, y, and z in angstroms. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Tool-specific result fields on success. |
| error | object | – | Structured failure on unsuccessful execution. |
| meta | object | yes | Run identifiers, timings, and input/output hashes. |
| ok | boolean | yes | Whether execution completed successfully. |
No examples provided.
validate_sequence ~100
Validate one protein FASTA record and return its normalized sequence, length, header, and SHA-256 identity. Use before peptide generation or prediction; this checks sequence syntax, not structure or biological activity. Invalid input returns a structured validation error.
| Name | Type | Req | Description |
|---|---|---|---|
| fasta | string | yes | One protein FASTA record with header and amino-acid sequence. |
| profileVersion | string | yes | Version of the sequence validation profile; mvp-v1.0 is the current profile. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Tool-specific result fields on success. |
| error | object | – | Structured failure on unsuccessful execution. |
| meta | object | yes | Run identifiers, timings, and input/output hashes. |
| ok | boolean | yes | Whether execution completed successfully. |
No examples provided.
validate_structure ~184
Check supplied structure metadata and, when PDB bytes are provided, parse actual atoms, chains, and residues. Use before mapping, accessibility, or docking preparation; this does not evaluate model confidence or binding. Mismatched metadata returns a structured failure.
| Name | Type | Req | Description |
|---|---|---|---|
| chainIds | array | yes | Protein chain identifiers selected from the supplied structure. |
| format | string | yes | Requested structure or export format, as enumerated by this tool. |
| residueCount | integer | yes | Expected protein residue count for metadata consistency checks. |
| runId | string | yes | Caller-chosen identifier linking this call to one research run. |
| sourceStatus | string | yes | Provenance label for the supplied structure or compound. |
| structureId | string | yes | Stable identifier of the supplied or retrieved structure. |
| structurePdbBase64 | string | – | Base64-encoded protein PDB coordinate bytes for direct computation. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Tool-specific result fields on success. |
| error | object | – | Structured failure on unsuccessful execution. |
| meta | object | yes | Run identifiers, timings, and input/output hashes. |
| ok | boolean | yes | Whether execution completed successfully. |
No examples provided.
validate_thresholds ~110
Evaluate the versioned hard biological threshold profile against supplied candidates. Use before categorization or final constraint application; this reports rule outcomes rather than ranking candidates. Missing evidence is represented in the rule results instead of invented as a pass.
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | Caller-supplied candidate records; required nested fields depend on this operation. |
| ruleProfileVersion | string | yes | Version of the biological constraint rule profile. |
| runId | string | yes | Caller-chosen identifier linking this call to one research run. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Tool-specific result fields on success. |
| error | object | – | Structured failure on unsuccessful execution. |
| meta | object | yes | Run identifiers, timings, and input/output hashes. |
| ok | boolean | yes | Whether execution completed successfully. |
No examples provided.
visualize_results ~120
Build a deterministic visualization view model from supplied evidence for the selected chart or graph type. Use when a UI will render results; create_molstar_view is for coordinate-based 3D HTML. Returns view-model data, not a PNG or an independent scientific analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | Caller-chosen identifier linking this call to one research run. |
| visualizationSnapshot | object | – | Caller-supplied data for building a view model; no image is rendered. |
| visualizationType | string | yes | Named chart or graph view-model type to construct. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Tool-specific result fields on success. |
| error | object | – | Structured failure on unsuccessful execution. |
| meta | object | yes | Run identifiers, timings, and input/output hashes. |
| ok | boolean | yes | Whether execution completed successfully. |
No examples provided.
How do I install the ImmunoGraph MCP server?
ImmunoGraph MCP runs locally as a container image, launched with docker run --rm -i ghcr.io/ajey95/immuno-graph:0.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/ajey95/immuno-graph
claude mcp add ajey95-immunograph -- docker run --rm -i ghcr.io/ajey95/immuno-graph:0.2.1
What is the ImmunoGraph MCP server?
ImmunoGraph MCP is listed in the public MCP registry as io.github.Ajey95/immunograph. Provenance-aware computational epitope research tools with reproducible offline demonstrations. This page covers its container image (ghcr.io/ajey95/immuno-graph).
Is the ImmunoGraph MCP server safe to use?
ImmunoGraph MCP scores 40 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 ImmunoGraph MCP server expose?
ImmunoGraph MCP exposes 46 tools: validate_sequence, generate_candidate_peptides, predict_mhci, predict_mhcii, predict_bcell, and 41 more. Their descriptions and schemas cost roughly 7,653 tokens of context every time the server is loaded.
Is the ImmunoGraph MCP server still maintained?
ImmunoGraph MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 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 ImmunoGraph MCP server under?
ImmunoGraph MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.