Skip to main content
Glama
AM253906

metrc-mcp

by AM253906
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to metrc-mcp

No user-submitted related servers found.

    Related Servers

    • alterios-mcp

      SayAMSTASI
      F
      license
      C
      quality
      A
      maintenance
      A production-ready MCP server for inventory and interaction with Alterios/LIMS instances, enabling project listing, readonly data queries via REST and script-services, and controlled write operations.
      100
      -

    • fallpharm-mcp

      sjgant80-hub
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.
      MIT

    • Amazon FBA Ops MCP Server

      TNKfreelance
      F
      license
      A
      quality
      C
      maintenance
      A local MCP server that enables querying Amazon Selling Partner API for profitability analysis (revenue, fees, COGS, net margin) and inventory alerts (FBA stock levels and low-stock warnings) using read-only operations.
      9
      -

    • tibet-pol-mcp

      Humotica
      A
      license
      A
      quality
      D
      maintenance
      MCP server for running infrastructure health checks with TIBET provenance. It enables users to define, execute, and audit process health checks with dependency chaining and drift tracking.
      6
      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/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: facilities, active packages, single package lookup, finishing packages, items, incoming/outgoing transfers, and lab results. Even the package-related tools are clearly separated by scope (list vs. get vs. lab results).

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern using snake_case, with list_ for collection queries, get_ for single-record lookups, and finish_ for the one mutation. This makes the toolset predictable and easy for an agent to route.

    Tool Count5/5

    Eight tools is a well-scoped size for this domain. Each tool covers a meaningful part of the METRC workflow without unnecessary redundancy or bloat.

    Completeness3/5

    The read-side coverage is solid for facilities, packages, items, transfers, and lab results, and finish_package provides one mutation. However, common lifecycle operations such as creating or adjusting packages, receiving incoming transfers, and creating outgoing transfers are missing, leaving agents able to observe but not fully complete many compliance workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources