Skip to main content
Glama
io.github.veriko-mx-labs/veriko

io.github.veriko-mx-labs/veriko

Official

Related Servers

Alternatives to io.github.veriko-mx-labs/veriko

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables querying Mexico's SAT public lists to verify RFCs in bulk, search by business name, and obtain tax risk verdicts such as critical, high, medium, low, or clean.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous financial agents to submit payment webhooks, ledger entries, or transaction streams and receive balanced journal records, risk verification dossiers, and detection of card-testing clusters, volume spikes, and account takeovers.
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables official-source lookups on people and companies, covering registration status, tax and labor clearance certificates, sanctions lists, trademarks/patents, and electronic invoices, with platform-hosted pay-per-query access.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients such as Claude, Cursor, and VS Code to validate, cross-check, and verify Mexican CURPs against RENAPO, check verification status, and query token balance.
      5
      32 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to validate IBANs and bank codes across multiple countries, verify payee names against account holders, and screen names against major global sanctions lists. It connects clients to a hosted banking reference-data service over OAuth-authenticated HTTP.
      MIT

    TDQS

    A3.8/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools are mostly distinct: one lists public plans, the other compares capabilities and prices. However, there is potential overlap since a listing might include the same data, and an agent could be unsure whether to use list or comparison for pricing details.

    Naming Consistency5/5

    Both tools follow a clear, consistent pattern: a shared 'veriko_' prefix followed by a verb_noun structure (list_public_plans, get_public_plan_comparison). All snake_case and predictable.

    Tool Count3/5

    With only 2 tools, the set is borderline thin for a public plan API. While the narrow scope may justify a small count, it feels under-provisioned compared to typical 3–15 tool servers.

    Completeness4/5

    The surface covers listing and comparison of public plans, which likely satisfies the core read-only use case. A minor gap is the absence of a tool to fetch an individual plan’s full details by ID, though agents could work around it using the comparison tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues