Skip to main content
Glama
Sign In
automic-mcp

automic-mcp

by quelixir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to automic-mcp

No user-submitted related servers found.

    Related Servers

    • Local Knowledge MCP

      TuanLe-bk18
      A
      license
      Not graded
      quality
      B
      maintenance
      A security-first, read-only MCP server that lets clients browse and read text, PDF, and XLSX files from an explicit allowlist of local folders, with strict path and secret protections.
      MIT

    • Blocksize Market Data

      jf-cmyk
      A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for Blocksize real-time market data: crypto VWAP, bid/ask, FX, metals and tokenized equities, with pricing, coverage and x402 endpoint lookup. Signed-in users of the Claude, ChatGPT and Cursor connectors get 30,000 free live-data credits every month (1 credit = $0.001); subscriptions from EUR 49/month.
      7
      1
      MIT

    • tokenbel/financial-data

      Red-Panda-Dev
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server providing access to Belarusian securities data: tokens, shares, bonds, companies, ticker search, and company name or UNP search.
      MIT

    • financial-trading-risk-aiops

      jadenmong
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only MCP tools for market snapshots, position risk, order reconciliation, and daily report previews with deterministic financial calculations, evidence chains, and audit trails.
      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 11 tools

    Disambiguation4/5

    Most tools target a distinct resource or report type, and the three run_*_report variants are separated by their subject matter. The only mild friction is between list_distributions and get_distribution_payment_list (aggregate vs per-holder payment detail) and the generic get_report, but descriptions resolve both.

    Naming Consistency5/5

    Every name is snake_case verb_noun (list_issuers, get_daily_prices, run_register_listing_report), with consistent verbs chosen for the action type: list for collections, get for single fetches, run for async reports.

    Tool Count5/5

    Eleven tools is well within the sweet spot for a domain-specific data server, and each tool covers a distinct data product (issuers, securities, prices, holders, distributions, payments, three report types, report retrieval, plus a formatting helper).

    Completeness4/5

    The core read workflow is covered end to end: issuers to securities to prices/holders, distributions to per-holder payments, and async reports with a retrieval tool. Minor gaps exist — no single-record get_issuer/get_security detail endpoint and no holder lookup — but agents can work around these via the list tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources