Skip to main content
Glama
vor-bot

xyz.crossgrain/epitaxy

by vor-bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to xyz.crossgrain/epitaxy

No user-submitted related servers found.

    Related Servers

    • fda-inspections

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying FDA inspection outcomes, Form 483 observations, compliance actions, and import refusals, plus a combined firm risk profile, from the FDA Data Dashboard.
      11 npm
      MIT

    • Verilex Data

      carrierone
      A
      license
      B
      quality
      C
      maintenance
      Query 20 structured datasets from AI agents — healthcare providers (9M NPI records), SEC EDGAR filings, PACER federal courts, USPTO patents and trademarks, OFAC sanctions screening, crypto whale wallets, DeFi liquidation signals, Polymarket smart money, economic indicators (FRED/BLS), federal contracts, NOAA weather, and OTC shell risk scoring. Pay per query, no subscriptions
      75
      1
      MIT

    • dod-contract-announcements

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying US defense contract awards of $7.5M+ from the daily press-release feed, including recent announcements, contractor/service rankings, and coverage statistics.
      276 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.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a clear, distinct concern: shortages, recalls, federal contracts, cross-source supplier exposure, and data freshness. There is no meaningful overlap in purpose, and get_supplier_exposure is explicitly a join/view rather than another list endpoint.

    Naming Consistency5/5

    Tool names follow a consistent list_/get_ + noun pattern in snake_case. Collections use list_, single objects and metadata use get_, making the API predictable and easy to navigate.

    Tool Count5/5

    With 5 tools, the server is tightly scoped to pharmaceutical supply chain risk. Each tool supports a distinct part of the workflow, and none feel redundant or missing enough to make the set feel thin.

    Completeness4/5

    The core workflow of finding shortages, recalls, contracts, and supplier exposure is covered well. A minor gap is the lack of a company/detail lookup to discover valid company_id values, and no individual record retrieval, but these are workarounds via filters rather than dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources