Skip to main content
Glama
luizzzvictor

mcp-comexstat

by luizzzvictor

Related Servers

Alternatives to mcp-comexstat

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      MCP Server do SEI Pro para o SEI (Sistema Eletrônico de Informações) via API REST mod-wssei v2 + scraper do frontend web (modo híbrido).
      100
      12
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying official Brazilian Federal Revenue data on foreign trade habilitation (Radar), allowing users to check habilitation status directly from the official source. Read-only MCP server with a single consultation tool.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for the U.S. Census Bureau's International Trade Data API, enabling queries of monthly export and import statistics by HS, NAICS, end-use, and other classifications, with tools for trade balance, top partners, and country code lookup.
      7
      Creative Commons Zero v1.0 Universal
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the Omie API to list products, consult clients, and create budgets
      16 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for the Brazilian Chamber of Deputies open-data API, enabling search and retrieval of federal legislative bills and their status.
      15
      76 PyPI
      1
      Apache 2.0

    TDQS

    D1.9/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes targeting different data entities (countries, states, cities, NBM, etc.) or metadata (available fields, filters, metrics). However, some pairs like getCities/getMunicipalitiesData and getNBM/getNBMDetails have potential overlap that could cause confusion without descriptions to clarify their boundaries.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'get' or 'query' prefixes, using camelCase uniformly throughout. The naming is highly predictable and readable, with clear conventions for different types of operations (get for metadata/entities, query for data retrieval).

    Tool Count3/5

    With 20 tools, this is borderline heavy for a trade statistics server. While the domain appears broad (covering countries, states, cities, NBM codes, auxiliary tables, etc.), the count feels somewhat inflated with multiple similar metadata tools (getAvailableFields/Filters/Metrics/Years) that might be consolidated.

    Completeness4/5

    The tool set appears to provide comprehensive coverage for trade data exploration and retrieval, including metadata discovery, entity lookups, and data querying across different dimensions (current, historical, municipal). Minor gaps might exist in data modification capabilities, but for a read-only statistical service, the surface seems reasonably complete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues