Skip to main content
Glama
io.github.olzhas-raiganiyev/goszakup-mcp

io.github.olzhas-raiganiyev/goszakup-mcp

Related Servers

Alternatives to io.github.olzhas-raiganiyev/goszakup-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      MCP server for the AI-agent economy: free Kazakhstan / Central-Asia utilities (Kazpost parcel tracking, IIN/BIN & IBAN validation, GLEIF LEI lookup, KZT/ECB FX rates, weather) callable with no account, plus per-call purchase of KYA-verified API listings governed by Regent Protocol.
      10
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for verifying Russian counterparties (legal entities and individual entrepreneurs) via public Federal Tax Service data: EGRUL/EGRIP, bankruptcy registry (EFRSB), Transparent Business, bailiff service (FSSP), and arbitration courts (KAD).
      8
      114 PyPI
      15
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides free read-only business checks for IBANs, EU VAT number format, Peppol e-invoice rules, supplier bank-detail changes, and CSV/XLSX data cleaning.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Look up Russian companies by INN (tax ID) from Claude Desktop, Cursor or any MCP client: full company card, multi-year financials from official tax filings, bankruptcy and state-inspection history, trademarks and sanctions lists. Works without an API key — the anonymous free tier is enabled by default.
      5
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to validate Russian business requisites (INN, OGRN, bank accounts) via checksums, extract them from text, and retrieve counterparty details by INN using DaData.
      5
      MIT

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    check_bin validates an identifier while server_status reports runtime metadata; the two purposes have zero overlap. An agent can pick the right tool without any description ambiguity.

    Naming Consistency4/5

    Both names are snake_case and readable, but check_bin follows a verb_noun pattern while server_status is a noun phrase. Minor stylistic deviation rather than a real inconsistency.

    Tool Count2/5

    Two tools is far too thin for a Kazakhstan procurement server, especially since one slot is consumed by a generic status/health tool. The surface feels like a stub rather than a scoped feature set.

    Completeness1/5

    There are no procurement operations at all: no company lookup, no lot/tender search, no contract or award retrieval. check_bin's own description tells the agent to use it 'before looking up a company or person by identifier', but no such lookup tool exists, creating an explicit dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues