Catnap
NPM · @PIPEWORX/MCP-CATNAP · 2 COMPONENTS
CATNAP (Compile, Analyze, and Tally Neutralizing Antibody Panels) + the LANL HIV Molecular…
Available components
Last scanned (2 hours ago)
Scores higher than 72% of npm 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-catnap). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 821 tokens (~273/item across 3 items; 3 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 Management23
- Stability observed for 7 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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 0
- Security disclosure: fail → unverified ▼ functional
- 4 Nov 26 +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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 79
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 npm/@pipeworx/mcp-catnap@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-catnap |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-catnap/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3606691058 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:71605b21bade933365c40ecf543302eb9c772e9048754e1e834aef109f2911f80e4f7ea275c1a44b2142d84182a28d88a82a13dedd347c6e0698e8e97 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
catnap_antibody_info ~171
Metadata for an HIV antibody in LANL CATNAP: which region of the virus it binds (CD4 binding site, V3 glycan, MPER, …), its aliases, the paper that isolated it with PubMed id, light chain type, ADCC activity, and its mean panel IC50 with the number of viruses tested. Answers "what does PGT121 bind", "who isolated 10-1074", "how broad is this antibody's panel". For the per-strain measurements behind that panel, use catnap_search_neutralization.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum antibodies to return (default 10, max 50). |
| name | string | yes | Antibody name or alias, substring match, e.g. "VRC01", "PGT121". |
No output schema declared.
No examples provided.
catnap_search_neutralization ~232
HIV broadly neutralizing antibody POTENCY: IC50/IC80/ID50 measurements for an antibody across viral strains, or for a strain across antibodies, from LANL CATNAP. Answers "how potent is VRC01 against this strain", "which antibodies neutralize CNE8", "compare this antibody's panel across subtypes". Every value carries its assay citation and PubMed id. A value like ">10" is a BOUND the assay could not resolve past: it is returned with numeric_value null and censored true, never as the number 10. Pass antibody, virus, or both. For where an immune response BINDS rather than how strongly it neutralizes, use immunology_search.
| Name | Type | Req | Description |
|---|---|---|---|
| antibody | string | – | Antibody name, substring match, e.g. "VRC01", "10-1074", "PGT121". |
| limit | number | – | Maximum measurements to return (default 50, max 500). |
| virus | string | – | Virus/strain name, substring match, e.g. "CNE8", "BG505". |
No output schema declared.
No examples provided.
immunology_search ~366
Search the LANL HIV Molecular Immunology Database for T-cell epitopes (CTL/CD8+ or T-helper/CD4+) or antibody binding sites — a different question from catnap_search_neutralization: this is about WHERE on the virus an immune response targets and WHICH HLA restricts it, not how potently an antibody neutralizes. Answers "what CTL epitopes are in HIV Gag", "which antibodies bind the CD4 binding site", "what HLA restricts this epitope", "find epitopes at position 296-331 of Env". Queried LIVE against LANL's own keyless JSON API (no ingest — always current). table selects which of the three response types you get: ctl (CD8+ T-cell), helper (CD4+ T-cell), or ab (antibody binding sites). At least one of mab_name, epitope, protein_name is required. Returns citation, keywords, HXB2 coordinates and (for ab) binding region/neutralizing classification for each match.
| Name | Type | Req | Description |
|---|---|---|---|
| epitope | string | – | Epitope amino acid sequence, e.g. "GGKKKYKLK". Matches if this sequence is contained in the epitope. |
| limit | number | – | Maximum records to return (default 20, max 100) — applied client-side after the upstream call. |
| mab_name | string | – | Antibody name or alias. "ab" table only. |
| protein_name | string | – | HIV protein name, e.g. "Gag", "Env", "Nef". |
| table | string | yes | "ctl" = CD8+ T-cell epitopes, "helper" = CD4+ T-cell epitopes, "ab" = antibody binding sites. |
No output schema declared.
No examples provided.
How do I install the Catnap MCP server?
Catnap runs locally as an npm package, launched with npx -y @pipeworx/mcp-catnap. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-catnap
claude mcp add pipeworx-io-catnap -- npx -y @pipeworx/mcp-catnap
What is the Catnap MCP server?
Catnap is an MCP server listed in the public MCP registry as io.github.pipeworx-io/catnap. CATNAP (Compile, Analyze, and Tally Neutralizing Antibody Panels) + the LANL HIV Molecular… This page covers its npm package (@pipeworx/mcp-catnap).
Is the Catnap MCP server safe to use?
Catnap scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Catnap MCP server expose?
Catnap exposes 3 tools: catnap_search_neutralization, catnap_antibody_info, immunology_search. Their descriptions and schemas cost roughly 769 tokens of context every time the server is loaded.
Is the Catnap MCP server still maintained?
Catnap 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 Catnap MCP server under?
Catnap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.