Skip to main content
Glama
bluesky050

tianyan-mcp-server

by bluesky050
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to tianyan-mcp-server

No user-submitted related servers found.

    Related Servers

    • qnexus-mcp

      Blite-HQ
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for Quantinuum Nexus that lets AI agents inspect projects and, when enabled, run quantum circuits on the free H2-1LE emulator. It is read-only by default with optional flags for spending credits or interacting with real hardware.
      10
      1
      Apache 2.0

    • inventory-mcp

      ruanderson1
      F
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server for querying product inventory, providing tools to retrieve product details and stock quantities.
      -

    • telemetry-mcp

      selamy-labs
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server for querying telemetry data from configurable backends. Provides tools to list sources, describe schemas, run bounded queries, and compute aggregates.
      MIT

    • DaraCloud Metabase MCP

      kosovadaria
      A
      license
      Not graded
      quality
      C
      maintenance
      A demonstration MCP server that enables read-only SQL queries and schema exploration of a synthetic IaaS database through the Metabase API.
      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.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing backends, getting a specific backend's details, and submitting an experiment. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: list_available_quantum_backends, get_quantum_backend, submit_quantum_experiment. This makes the naming predictable and clear.

    Tool Count4/5

    With only 3 tools, the server is on the smaller end but still covers the primary actions needed for the domain. It is slightly thin but not problematically so.

    Completeness2/5

    The server supports listing backends, getting backend details, and submitting experiments, but there is no way to track experiment status, retrieve results, or cancel a submission. This leaves a significant gap in the experiment lifecycle.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources