io.github.nickjlamb/studydiff
NPM · STUDYDIFF-MCP · SCANNED SEP 20
Explain why two scientific papers disagree, every claim grounded in a verbatim source quote.
Available components
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 Security98
- 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
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 68 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 414 tokens (~138/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 Management90
- Stability observed for 27 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 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 io.github.nickjlamb/studydiff MCP server?
io.github.nickjlamb/studydiff runs locally as an npm package, launched with npx -y studydiff-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · studydiff-mcp
claude mcp add nickjlamb-studydiff -- npx -y studydiff-mcp
{
"mcpServers": {
"nickjlamb-studydiff": {
"command": "npx",
"args": [
"-y",
"studydiff-mcp"
]
}
}
} {
"servers": {
"nickjlamb-studydiff": {
"command": "npx",
"args": [
"-y",
"studydiff-mcp"
]
}
}
} codex mcp add nickjlamb-studydiff -- npx -y studydiff-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nickjlamb-studydiff": {
"type": "local",
"command": [
"npx",
"-y",
"studydiff-mcp"
],
"enabled": true
}
}
} openclaw mcp add nickjlamb-studydiff --command npx --arg -y --arg studydiff-mcp
mcp_servers:
nickjlamb-studydiff:
command: "npx"
args: ["-y", "studydiff-mcp"] {
"McpServers": {
"nickjlamb-studydiff": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"studydiff-mcp"
]
}
}
} assistant mcp add nickjlamb-studydiff -t stdio -c npx -a -y studydiff-mcp
{
"mcpServers": {
"nickjlamb-studydiff": {
"command": "npx",
"args": [
"-y",
"studydiff-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 13 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 20 Sept 2026 · Analysed npm/studydiff-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 →
compare_example Run a cached worked example ~154
Run one of StudyDiff's built-in worked examples – real, famous contradictions with verbatim abstracts. Runs fully offline against cached papers: no API key and no network needed, so it is the quickest way to see the grounded output. Options: "mouse-inflammation" (Seok 2013 vs Takao 2015 – same datasets, opposite conclusions), "resveratrol-sirt1" (Howitz 2003 vs Beher 2009 – an assay artifact), "treg-stability" (Zhou 2009 vs Rubtsov 2010 – stable vs unstable Treg lineage, driven by the fate-mapping method).
| Name | Type | Req | Description |
|---|---|---|---|
| example | string | yes | Which built-in example to run |
No output schema declared.
No examples provided.
compare_studies Compare two studies and explain why they disagree ~228
Explain WHY two scientific papers reach different conclusions. Extracts each study design (species, model, intervention, assay, dose, timing, endpoint, sample size, statistic, finding, limitations), verifies every extracted value against the source text with deterministic grounding, then ranks the design differences that most plausibly drive the disagreement (primary driver / also differs / ruled out) and suggests what evidence would resolve it. Every claim is traced to a verbatim quote; unsupported fields are returned as "not reported" rather than guessed. Never picks a winner. Each paper is given as {id} (PMID or DOI) or {text}. Requires ANTHROPIC_API_KEY – use compare_example for a no-key demonstration.
| Name | Type | Req | Description |
|---|---|---|---|
| paperA | object | yes | First study – {id} (PMID/DOI) or {citation, text} |
| paperB | object | yes | Second study – {id} (PMID/DOI) or {citation, text} |
| question | string | – | The question under comparison, e.g. "Is the Treg lineage stable in vivo?" |
No output schema declared.
No examples provided.
list_examples List the built-in worked examples ~32
List StudyDiff's cached worked examples (real published contradictions) that can be run with compare_example without an API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.nickjlamb/studydiff MCP server?
io.github.nickjlamb/studydiff is an MCP server listed in the public MCP registry as io.github.nickjlamb/studydiff. Explain why two scientific papers disagree, every claim grounded in a verbatim source quote. This page covers its npm package (studydiff-mcp).
Is the io.github.nickjlamb/studydiff MCP server safe to use?
io.github.nickjlamb/studydiff scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.nickjlamb/studydiff MCP server expose?
io.github.nickjlamb/studydiff exposes 3 tools: compare_studies, compare_example, list_examples. Their descriptions and schemas cost roughly 414 tokens of context every time the server is loaded.
Is the io.github.nickjlamb/studydiff MCP server still maintained?
io.github.nickjlamb/studydiff is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.nickjlamb/studydiff MCP server under?
io.github.nickjlamb/studydiff declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.