Skip to main content
Glama
pipaacebedo

seace-mcp

by pipaacebedo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to seace-mcp

No user-submitted related servers found.

    Related Servers

    • spij-mcp

      pipaacebedo
      A
      license
      A
      quality
      A
      maintenance
      Enables local MCP clients to search and read Peru's official legal information system, including legal norms and jurisprudence, with tools for full-text search, structure mapping, targeted reading, and filters. It provides clean content without storing files, using stdio transport and public session authentication.
      7
      6
      Apache 2.0

    • LATAM-MCP

      Tolomere21
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Peruvian public-data lookups including SUNAT RUC registrations, BCRP exchange rates, and SEACE tenders. Provides official open-data access through tools for Claude, Cursor, and other MCP clients.
      MIT

    • comprasal-mcp

      glassbit
      A
      license
      A
      quality
      C
      maintenance
      Enables querying El Salvador's public procurement data, including awarded processes, supplier contracts, and institution details, from the live COMPRASAL API through an MCP interface.
      8
      1
      MIT

    • chile-procurement

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables access to Chile's government procurement data (Mercado Público / ChileCompra) via MCP, allowing AI agents to query public procurement information.
      388 npm
      MIT

    • mcp-colombia-secop

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query Colombian government procurement data via MCP tools or natural language questions.
      428 npm
      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.6/5.0

    Scored across 25 tools

    Disambiguation4/5

    Each buscar_* tool targets a distinct SEACE dataset (processes, ACF, EI, requirements, OC/OS, CCO, entities, PAC, contracts), and detail tools are split into individual vs batch with explicit guidance. Minor overlap exists between buscar_expresiones_interes and buscar_requerimientos because their result shapes are similar, and between ficha_proceso and fichas_procesos, but descriptions clarify when to use each.

    Naming Consistency3/5

    Naming is readable and grouped (buscar_*, detalle_*, fichas_*), but it mixes verb-first search tools with noun-first detail/catalog tools and inconsistent singular/plural forms (ficha_proceso vs fichas_procesos, detalle_contrato vs detalles_contratos). It is not chaotic, but it does not follow one predictable verb_noun pattern throughout.

    Tool Count3/5

    25 tools is borderline heavy for the server's broad domain, spanning processes, contracts, PAC, georef, catalogs, and document URLs. Most tools earn their place, but the volume increases selection cost and could be streamlined with fewer parameterized endpoints.

    Completeness4/5

    Coverage is strong across search and detail for processes, ACF, EI, requirements, orders, contracts, PAC, entities, ubigeo, and documents, including batch helpers. Minor gaps remain, such as no general provider search beyond contract filters or profile URL, but core procurement workflows are well supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources