Skip to main content
Glama
Proprius-Labs

PocketScout MCP

by Proprius-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to PocketScout MCP

No user-submitted related servers found.

    Related Servers

    • mcp-alphafold

      zeinab-sheikhi
      F
      license
      B
      quality
      D
      maintenance
      Provides programmatic access to AlphaFold protein structure predictions and UniProt data, enabling users to retrieve protein structures, summaries, and annotations through natural language.
      3
      -

    • protein-tools-mcp

      Tahsin-uv
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP-capable AI clients to characterize proteins end to end: PDB/mmCIF validation, sequence extraction and typing, pLDDT confidence summaries, metal-site geometry with bidentate chelate detection, GROMACS trajectory metrics and plots, and live UniProt, AlphaFold DB, and RCSB lookups. Also ships a point-and-click Protein Lab web UI (and a persistent run registry) so students and wet-lab biologists can get the same results without any client setup.
      31
      MIT

    • life-science-mcp

      achillesrasquinha
      A
      license
      A
      quality
      B
      maintenance
      Enables unified access to 110 life science APIs and databases, including genomics, proteomics, chemistry, literature, and clinical data. Users can query genes, proteins, compounds, pathways, and more through natural language.
      3
      MIT

    • MCPymol

      chemrich
      A
      license
      C
      quality
      B
      maintenance
      A Model Context Protocol server that lets you drive PyMOL with natural language, enabling structure loading, analytical views, measurements, and protein exploration through AI assistants.
      100
      16
      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 8 tools

    Disambiguation4/5

    Tools have distinct purposes: CharacterizeTarget, GetRelatedStructures, GetBindingSites, GetLigandHistory, CheckConservation, CheckKnownVariants, SearchTargetLiterature, and ConsolidateBindingSites. Some potential overlap exists between GetBindingSites and ConsolidateBindingSites (both analyze binding pockets), but descriptions clarify that ConsolidateBindingSites aggregates across multiple structures while GetBindingSites analyzes a single structure. An agent could still confuse when to use one versus the other, but the 'heaviest tool' warning helps.

    Naming Consistency5/5

    All tool names follow a consistent verb-noun (PascalCase) pattern: CharacterizeTarget, GetRelatedStructures, GetBindingSites, etc. No deviations or mixed conventions.

    Tool Count5/5

    8 tools is well-scoped for a specialized structural biology MCP server. Each tool covers a distinct analysis step, and the count is neither too thin nor too heavy.

    Completeness4/5

    The toolset covers key aspects: target characterization, structure discovery, binding site mapping, ligand history, conservation, variants, literature, and consolidation. However, there is no explicit tool for exporting or visualizing results, nor for direct comparison between human and model organism structures beyond conservation. These are minor gaps that might require workarounds but don't break core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources