Oliver's mTOR Atlas
NPM · MTOR-ATLAS-MCP · 2 COMPONENTS
Evidence-labelled mTOR research: studies, entities, pathway claims, contradictions, open questions.
Available components
Last scanned (1 hour ago)
Scores higher than 67% 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 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
- 30 of 92 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 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1917 tokens (~147/item across 13 items; 13 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 Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 0
- Schema quality: 128 → 147 ▼ functional
- Tool coverage: 55% → 77% ▲ functional
- Package version: 1.3.0 → 1.3.3 functional
- 16 Oct 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 Oct 26 +36
- Injection markers: unverified → pass ▲ security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 43% → 55% ▲ functional
- Stability: unverified → 0.43 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 13 Oct 26 −35
- Stability: 0.37 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 1.2.2 → 1.3.0 functional
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 Oct 2026 · Analysed npm/mtor-atlas-mcp@1.3.3
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
atlas_about About the Atlas ~61
Dataset version, corpus snapshot date, counts, evidence-code legend and how to cite the dataset. When the Atlas does not report the contested and conflicting counts itself, derived_counts adds them, computed from the relations, so they can be compared with find_contradictions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
evidence_between Evidence between two entities ~105
Direct curated relations between two entities (either direction) with full cards for the supporting and conflicting studies. Answers questions such as "what is the evidence that A acts on B?". A study that repeats within the answer is sent in full once and afterwards as a short card with full_card_in.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | – |
| b | string | yes | – |
| dedupe | boolean | – | Send a repeated study in full only once. Pass false for a full card every time. |
No output schema declared.
No examples provided.
find_contradictions Find contested claims ~214
Relations the Atlas marks as contested or that carry conflicting studies, with both sides of the evidence. status says which; breakdown splits the total. A contested relation with no conflicting study listed is flagged conflicting_studies_missing; relations named in its note or boundary are shown in named_in_text (a mention is not evidence). Paged: pass next_offset as offset for the rest. Optionally limited to one entity.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | boolean | – | Shorten the long boundary and note text (text_truncated is set); get_relation has the full text. |
| dedupe | boolean | – | Send a repeated study in full only once. Pass false for a full card every time. |
| entity | string | – | – |
| limit | integer | – | Maximum 50; a larger value is capped at 50. |
| offset | integer | – | For the next page: pass next_offset from the previous answer. |
| only_contested | boolean | – | Keep only relations the Atlas flags contested, not those that merely carry conflicting studies. |
No output schema declared.
No examples provided.
find_relations Find pathway relations ~174
Signed, evidence-linked pathway relations (claims such as "Rheb activates mTORC1"). Filter by an entity on either end, by source/target, effect, contested status or minimum strength of the best supporting evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| contested_only | boolean | – | Only relations marked contested or with conflicting studies |
| effect | string | – | – |
| entity | string | – | Entity on either end of the relation |
| limit | integer | – | Maximum 50; a larger value is capped at 50. |
| offset | integer | – | For the next page: pass next_offset from the previous answer. |
| source | string | – | – |
| strongest_at_least | string | – | Keep relations whose best supporting study is at least this code in the order S > H > A > M |
| target | string | – | – |
No output schema declared.
No examples provided.
get_author Get one author ~91
One profiled author by profile id ("claudio-de-virgilio"), full name, author-list form or ORCID: lab, role, profile URL and short cards of their studies in the Atlas.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | e.g. "Claudio De Virgilio", "De Virgilio C", "claudio-de-virgilio" |
| id | string | – | Alias of author. |
No output schema declared.
No examples provided.
get_entity Get one entity ~114
One entity (gene/protein, complex, drug, disease, process...) with its linked studies as short cards (first studies_limit) and every pathway relation it takes part in as a one-line claim. Accepts an id, a name or a synonym.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | e.g. "mTORC1", "Rheb", "rapamycin" |
| id | string | – | Alias of entity. |
| studies_limit | integer | – | Maximum 50; a larger value is capped at 50. |
No output schema declared.
No examples provided.
get_question Get one question ~54
One open or frontier question by ID (e.g. "H1", "F2"): the gap, what changed, what is still open, how it could be tested, linked studies.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_relation Get one relation ~45
One pathway relation by ID (e.g. "RHEB-MTORC1"): mechanism, boundary conditions, confidence, supporting and conflicting studies.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_study Get one study ~102
Full record for one study by Atlas ID (e.g. "SAB1994"), PMID, DOI or PMCID: abstract excerpt, extracted findings, linked entities, the relations it supports or contradicts, related open questions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Alias of sid. |
| sid | string | – | Atlas study ID ("SAB1994"), PMID ("23716719"), DOI or PMCID |
| study_id | string | – | Alias of sid. |
No output schema declared.
No examples provided.
list_questions List open questions ~151
The Atlas's open questions (evidence gaps with testable hypotheses) and frontier questions. Paged. By default still_open is shortened at a sentence boundary (still_open_truncated); get_question has the full text, or pass brief=false.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | boolean | – | Shorten still_open; false returns the full text. |
| kind | string | – | – |
| limit | integer | – | Maximum 50; a larger value is capped at 50. |
| offset | integer | – | For the next page: pass next_offset from the previous answer. |
| query | string | – | Keywords to find questions by their title, gap, hypothesis or what is still open, e.g. "rapamycin immune". |
No output schema declared.
No examples provided.
search_authors Search authors ~143
People in the Atlas by full name ("Claudio De Virgilio"), author-list form ("De Virgilio C"), ORCID or lab. results are authors with a profile page (full name, ORCID, lab, their study IDs); in_author_lists are matching names in study author lists without a profile.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum 50; a larger value is capped at 50. |
| offset | integer | – | For the next page: pass next_offset from the previous answer. |
| query | string | yes | A name, ORCID or lab, e.g. "Sabatini", "Claudio De Virgilio", "Fribourg" |
No output schema declared.
No examples provided.
search_entities Search entities ~164
Find genes/proteins, complexes, drugs, diseases, processes, nutrients and outcomes by name or synonym. Each result says where it matched (match_field: name, synonym or description); use match="name" to leave out description-only hits.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum 100; a larger value is capped at 100. |
| match | string | – | "any" also searches descriptions; "name" searches names and synonyms only. |
| offset | integer | – | For the next page: pass next_offset from the previous answer. |
| query | string | yes | Name or synonym, e.g. "raptor", "sirolimus" |
| type | string | – | Optional type filter, e.g. "Drug", "Gene/Protein", "Disease" |
No output schema declared.
No examples provided.
search_studies Search studies ~249
Search the curated studies by keywords, optionally filtered by evidence code, a linked entity (gene, drug, disease...) and year range. Searches title, finding, authors (author-list form "Sabatini DM" and full names of profiled authors), PMID, DOI, PMCID, linked entities and their synonyms, journal, model system and the abstract excerpt. A query that is a PMID or DOI returns that study. Returns summary records with evidence codes and URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | Only studies linked to this entity (name, synonym or id), e.g. "Rheb". |
| evidence_code | array | – | Keep only these evidence codes, e.g. ["H","S"] for human evidence. |
| limit | integer | – | Maximum 50; a larger value is capped at 50. |
| offset | integer | – | For the next page: pass next_offset from the previous answer. |
| query | string | – | Keywords, e.g. "rapamycin lifespan mice", a person ("Claudio De Virgilio"), a PMID or a DOI. Omit to list by filters only. |
| year_from | integer | – | – |
| year_to | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Oliver's mTOR Atlas MCP server?
Oliver's mTOR Atlas runs locally as an npm package, launched with npx -y mtor-atlas-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 · mtor-atlas-mcp
claude mcp add open-mtor-atlas-mtor-atlas -- npx -y mtor-atlas-mcp
What is the Oliver's mTOR Atlas MCP server?
Oliver's mTOR Atlas is an MCP server listed in the public MCP registry as io.github.open-mtor-atlas/mtor-atlas. Evidence-labelled mTOR research: studies, entities, pathway claims, contradictions, open questions. This page covers its npm package (mtor-atlas-mcp).
Is the Oliver's mTOR Atlas MCP server safe to use?
Oliver's mTOR Atlas scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 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 Oliver's mTOR Atlas MCP server expose?
Oliver's mTOR Atlas exposes 13 tools: atlas_about, search_studies, get_study, search_entities, get_entity, and 8 more. Their descriptions and schemas cost roughly 1,667 tokens of context every time the server is loaded.
Is the Oliver's mTOR Atlas MCP server still maintained?
Oliver's mTOR Atlas is still listed as active in the MCP registry. We last reached this channel on 25 October 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 Oliver's mTOR Atlas MCP server under?
Oliver's mTOR Atlas declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.