Skip to main content
Glama
Sign In
RegNetwork MCP

RegNetwork MCP

by qi-717abc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to RegNetwork MCP

No user-submitted related servers found.

    Related Servers

    • EBI Complex Portal MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching a manually curated database of stable macromolecular protein complexes by protein or complex name, gene, GO term, or biological process, and fetching individual records by accession to retrieve subunits with UniProt identifiers, biological roles, and stoichiometry. Complements UniProt, IntAct, and STRING, and can be used keyless over a hosted gateway endpoint or run locally over stdio.
      358 npm
      MIT

    • STRING-db MCP Server

      Augmented-Nature
      A
      license
      B
      quality
      D
      maintenance
      A comprehensive Model Context Protocol (MCP) server for accessing the STRING protein interaction database. This server provides powerful tools for protein network analysis, functional enrichment, and comparative genomics through the STRING API.
      6
      4
      MIT

    • PubTator 3 MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to resolve genes, diseases, chemicals, variants and species to normalized ids, search ~36M PubMed abstracts and PMC full texts by free text or entity, and retrieve the machine-extracted relations between them with the supporting sentences and PMIDs. Supports auditing individual relations with full evidence passages and pulling per-article entity annotations with character offsets.
      255 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

    A3.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a distinct role: status, entity resolution, exact interaction search, one-hop neighbor retrieval, subnetwork extraction, summarization, evidence retrieval, export, and official file download. The descriptions explicitly bound overlapping concepts such as search vs. neighbors and extraction vs. summarization.

    Naming Consistency5/5

    All tool names use snake_case and follow a predictable verb_noun or verb_adjective_noun pattern. The verbs are clear and consistent across the set.

    Tool Count5/5

    Nine tools is well-scoped for a regulatory network database connector. Each tool covers a necessary stage of the workflow: status, lookup, traversal, extraction, analysis, evidence, export, and download.

    Completeness4/5

    The surface covers the main read-only lifecycle for querying, analyzing, exporting, and downloading regulatory network data. Minor gaps remain, such as no standalone search by PMID or explicit alias enumeration, but the descriptions acknowledge these limitations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources