mtor-atlas-mcp

MCPcommunitylive
v1.2.1Oliver BartonMITUpdated 2d agonpmGitHub

MCP server for Oliver's mTOR Atlas: evidence-labelled mTOR studies, entities, signed pathway relations with supporting and conflicting evidence, and open questions.

Endpoint healthlive
checked 19h ago · 96ms
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
647Downloads/wk
2d agoLast update
Package
AuthorOliver Barton
LicenseMIT
Version1.2.1
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface11 tools · none privileged
Security scan✓ Cleanv1.2.1 · todayHow well does this scan work?
EvalsNone
IndexedOct 3, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

11 tools · none privileged
Statically extracted from the published packagev1.2.1 · 19h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

atlas_aboutDataset version, corpus snapshot date, counts, evidence-code legend and how to cite the dataset.

Dataset version, corpus snapshot date, counts, evidence-code legend and how to cite the dataset.

No input schema was published for this tool.

search_studiesSearch the curated studies by keywords (title, finding, authors, journal, model system), optionally filtered by evidence code, a linked entity (gene, drug, disease...) and year range. Returns summary records with evidence codes and URLs.

Search the curated studies by keywords (title, finding, authors, journal, model system), optionally filtered by evidence code, a linked entity (gene, drug, disease...) and year range. Returns summary records with evidence codes and URLs.

No input schema was published for this tool.

get_studyFull record for one study by Atlas ID (e.g. "SAB1994"): abstract excerpt, extracted findings, linked entities, the relations it supports or contradicts, related open questions.

Full record for one study by Atlas ID (e.g. "SAB1994"): abstract excerpt, extracted findings, linked entities, the relations it supports or contradicts, related open questions.

No input schema was published for this tool.

search_entitiesFind genes/proteins, complexes, drugs, diseases, processes, nutrients and outcomes by name or synonym.

Find genes/proteins, complexes, drugs, diseases, processes, nutrients and outcomes by name or synonym.

No input schema was published for this tool.

get_entityOne 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.

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.

No input schema was published for this tool.

find_relationsSigned, 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.

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.

No input schema was published for this tool.

get_relationOne pathway relation by ID (e.g. "RHEB-MTORC1"): mechanism, boundary conditions, confidence, supporting and conflicting studies.

One pathway relation by ID (e.g. "RHEB-MTORC1"): mechanism, boundary conditions, confidence, supporting and conflicting studies.

No input schema was published for this tool.

evidence_betweenDirect 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?".

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?".

No input schema was published for this tool.

find_contradictionsRelations the Atlas marks as contested or that carry conflicting studies, with both sides of the evidence. Optionally limited to one entity.

Relations the Atlas marks as contested or that carry conflicting studies, with both sides of the evidence. Optionally limited to one entity.

No input schema was published for this tool.

list_questionsThe Atlas's open questions (evidence gaps with testable hypotheses) and frontier questions.

The Atlas's open questions (evidence gaps with testable hypotheses) and frontier questions.

No input schema was published for this tool.

get_questionOne 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.

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.

No input schema was published for this tool.

11 of 11 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for Oliver's mTOR Atlas: evidence-labelled mTOR studies, entities, signed pathway relations with supporting and conflicting evidence, and open questions.

Keywords
mcpmodel-context-protocolmtormTORC1rapamycinaginglongevitybiologyevidenceknowledge-graph
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-03 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in memory & knowledge graphs