Oliver's mTOR Atlas
Related Servers
Alternatives to Oliver's mTOR Atlas
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides read-only access to the ProPaths verified protein interactome, letting AI agents search proteins, retrieve mechanistic interaction details, and explore pathway ontology through MCP tools, resources, and prompts.11MIT
- FlicenseNot gradedqualityBmaintenanceEnables agents to query a single-source ontology of types, entities, statements, evidence, and controlled vocabulary, including bitemporal "as of" and "as recorded" fact lookups. Supports writing by letting agents propose candidate statements while keeping approval, review transitions, and authoritative reasoning restricted to approved facts.-
- AlicenseNot gradedqualityAmaintenanceA unified biomedical graph database that integrates 50+ primary data sources — genes, proteins, compounds, diseases, pathways, and clinical data — into a single queryable graph with billions of cross-reference edges. Its native MCP server gives LLMs direct access to structured, authoritative biomedical data, complementing their reasoning with reliable identifiers and up-to-date database content.20AGPL 3.0

CAgneT Knowledgeofficial
FlicenseNot gradedqualityCmaintenanceEnables grounded read-only queries over a local knowledge base, reviewable pending updates, and audited merging of changes.-- AlicenseAqualityBmaintenanceProvides a compiled knowledge substrate, extracting atomic claims from an append-only capture log and querying a bitemporal claim graph over MCP. Read-only by default, with opt-in writes for trusted sources.4MIT
- FlicenseNot gradedqualityBmaintenanceProvides read-only access to a personal RAG knowledge base, enabling hybrid search, evidence-grounded retrieval with citations, and knowledge gap tracking for LLM agents.-
TDQS
Scored across 11 tools
Most tools target distinct resources (studies, entities, relations, questions) with clear get_/search_ pairs. However, evidence_between overlaps with find_relations (both return curated relations, the former just a special case for a two-entity pair), and find_contradictions overlaps with find_relations' contested-status filter. Descriptions help but an agent could still misselect among the relation-oriented tools.
The set is predominantly snake_case verb_noun (search_studies, get_study, find_relations, list_questions), which is readable and predictable. The main deviation is the inconsistent use of search_ vs find_ for essentially the same lookup semantics, plus the noun-only atlas_about.
11 tools is well-scoped for a read-only curated atlas, with each tool mapping to a distinct resource or query pattern. No tool feels redundant or trivially thin.
The surface covers the full read lifecycle for the domain: metadata (atlas_about), search+get for studies, entities, relations and questions, plus specialized views for evidence-between and contradictions. As a curated read-only dataset, no create/update/delete is needed, so coverage is complete.