io.github.nickjlamb/studydiff
NPM · STUDYDIFF-MCP · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. 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 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).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 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · studydiff-mcp
claude mcp add nickjlamb-studydiff -- npx -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": {
"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.
- 3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +59
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −40
- Malware scan: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 96 packages
96 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.