Skip to main content
Glama
OSIRIS-Solutions

OSIRIS MCP

Official
by OSIRIS-Solutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to OSIRIS MCP

No user-submitted related servers found.

    Related Servers

    • governed-rag-mcp

      Rlealbarili
      A
      license
      A
      quality
      B
      maintenance
      Provides governed retrieval over MCP with hybrid search, strict confidence gating, and access control, exposing three read-only tools.
      3
      Apache 2.0

    • Aegis

      Demi8-patch
      F
      license
      A
      quality
      C
      maintenance
      Provides read-only MCP tools to search and retrieve evidence-grounded knowledge compiled from video content, including hybrid semantic and lexical search with citations.
      5
      -

    • @cyanheads/orcid-mcp-server

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching and retrieving researcher profiles, works, affiliations, funding, and peer review records from the ORCID registry via MCP, supporting STDIO or Streamable HTTP.
      71 npm
      2
      Apache 2.0

    • grant-agent-harness

      YPCC
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables reviewing grant application text, running deterministic eval cases, and executing Office of Research Aid packet workflows through MCP.
      Apache 2.0

    • paper-search-cli

      X-T-E-R
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for searching academic, patent, and web sources, normalizing identifiers, and managing workspace records. Exposes the same operations to AI clients via MCP tools.
      37 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 12 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources