OSIRIS MCP
OfficialRelated Servers
Alternatives to OSIRIS MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables users to run deep research, quick searches, and report writing, and to retrieve research sources and context through MCP-compatible clients.MIT
- AlicenseAqualityBmaintenanceProvides governed retrieval over MCP with hybrid search, strict confidence gating, and access control, exposing three read-only tools.3Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables life-science research by providing search and retrieval across linked publications, clinical trials, drugs, genes, regulatory approvals, and patents through MCP clients.1Apache 2.0
- FlicenseAqualityCmaintenanceProvides read-only MCP tools to search and retrieve evidence-grounded knowledge compiled from video content, including hybrid semantic and lexical search with citations.5-
- AlicenseNot gradedqualityAmaintenanceEnables searching and retrieving researcher profiles, works, affiliations, funding, and peer review records from the ORCID registry via MCP, supporting STDIO or Streamable HTTP.394 npm5Apache 2.0
- AlicenseNot gradedqualityFmaintenanceEnables reviewing grant application text, running deterministic eval cases, and executing Office of Research Aid packet workflows through MCP.Apache 2.0
TDQS
Scored across 12 tools
Each tool targets a distinct resource or action: instance info, server info, units, topics, activity types, activities, people, experts, and projects. The overlapping-sounding search_people and search_experts are clearly differentiated as identity search vs. expertise search.
Most tools follow a consistent verb_noun pattern: get_* for retrieval, list_* for enumeration, and search_* for search. server_info deviates slightly by lacking a verb, but the pattern is otherwise predictable.
12 tools is well-scoped for a read-only research discovery system, covering instance metadata, lookup vocabularies, activities, people, experts, and projects without unnecessary bloat.
The surface provides list/search and get operations for the core entities, with discovery tools feeding IDs into search tools. Minor gaps exist, such as get_person requiring a username rather than the person ID returned by search_people, and no dedicated get_unit/get_topic, but the list tools fully expose those entities.