Skip to main content
Glama
Sign In
Rediscover

Rediscover

by shyamolkonwar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Rediscover

No user-submitted related servers found.

    Related Servers

    • Data Science Agent MCP Server

      frzzzing
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides MCP-compatible tools for data analysis, including file reading, Python/SQL execution, and hypothesis testing. Enables autonomous data analysis agents to interact with a sandboxed environment.
      1
      -

    • ibm-quantum

      jaykobdetar
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to discover accessible quantum instances and backends, simulate circuits locally, preview transpiled circuits, submit Sampler or Estimator jobs, and inspect or cancel runtime jobs via typed MCP tools.
      10
      MIT

    • Wraith

      MRvirusIR
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to run scope-checked probes of MCP endpoints, analyze tool definitions for poisoning and dangerous capabilities, detect definition drift, and generate reproducible evidence bundles and bounty-ready reports.
      MIT
    • Valstorm Hosted MCP Server

      Valstorm Hosted MCP Serverofficial

      Valstorm-Corp
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables autonomous agents to securely access and manage virtual file systems, records, schemas, SQL and Mongo queries, and RAG search through scoped MCP tools, while supporting binary transfers via presigned S3 recipes.
      PolyForm Noncommercial 1.0.0
    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

    B3.2/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool maps to a distinct pipeline stage (orient, list, fetch, quality-check, analyze, retrieve, report, verify), and descriptions explicitly warn about the main confusion points (detector-frame vs source-frame, get_results vs get_catalog). The only residual overlap is between list_events and get_catalog, both catalog-facing, plus three 'get_*' tools that an agent must read carefully to distinguish.

    Naming Consistency5/5

    All nine names are snake_case verb_noun constructs (get_guide, fetch_strain, analyze_detector, make_report) with a predictable verb-first pattern. Verbs vary appropriately by action rather than chaotically, and resource nouns are clear.

    Tool Count5/5

    Nine tools is well within the ideal 3-15 range and each corresponds to a real step in the gravitational-wave analysis workflow. No tool appears redundant or bolted on; even verify_artifacts and get_guide earn their place as integrity and orientation steps.

    Completeness4/5

    The surface covers the full lifecycle: orientation, catalog listing, strain acquisition, quality gating, analysis, results, published inference, reporting, and artifact verification. Minor gaps exist — no run cleanup/deletion, no cross-event comparison, and no direct export of results beyond the HTML report — but these are workaroundable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources