Skip to main content
Glama
bormeapi

BORME MCP Server

by bormeapi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to BORME MCP Server

No user-submitted related servers found.

    Related Servers

    • Mapa Societario

      anbrme
      A
      license
      Not graded
      quality
      B
      maintenance
      Search Spanish companies, directors and corporate relationships from official BORME registry filings — ~3.2M companies since 2009. Read-only, anonymous.
      MIT

    • APIEmpresas MCP

      abasmartinc
      A
      license
      A
      quality
      B
      maintenance
      Enables assistants to query Spanish company registry data in natural language, including lookups by CIF or name, KYB verification, directors, BORME filings, public contracts and risk profiles. All tools are read-only and draw on the user's own API plan credits.
      8
      0
      MIT

    • Asiento Uno

      odela-pixel
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform due diligence, KYB, and supplier or client verification by querying Spanish company registry data cross-referenced with public grants and procurement awards, each fact linking to its official publication.
      MIT

    • Spain & EU Public Data MCP

      opendata-forge
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude, Cursor, and other MCP clients to search Spanish BOE/BORME gazettes, open and forthcoming EU funding calls, and TED public procurement notices through read-only tools that return live JSON with source links.
      3
      MIT

    • BODACC MCP Server

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and retrieving French official business-event notices (creations, insolvency, sales, modifications, etc.) for companies by SIREN or name, with filtering by event type, department, and date range, all via keyless access.
      216 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

    A4.6/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: company search vs. event search vs. single-company history vs. NIF lookup vs. brand lookups in both directions. Overlaps such as search_events vs. daily_digest are explicitly differentiated by the descriptions, and the inverse brand_owner/company_brands pair is unambiguous.

    Naming Consistency4/5

    All names use snake_case and are readable, but the set mixes verb-first names (search_events, list_act_types) with entity-first names (company_history, brand_owner, daily_digest). The variation is minor and appropriate for resource-oriented lookup tools, so it is not confusing.

    Tool Count5/5

    Ten tools is well within a healthy range for a registry-data server and each tool covers a distinct user need: search, entity lookup, timelines, brands, metadata, digests, and signals. No tool feels extraneous.

    Completeness4/5

    The surface covers the main BORME workflows: finding companies, retrieving histories, searching events, resolving brands, checking coverage, and sampling risk signals. Minor gaps exist, such as no direct single-event lookup or full signal feed, but they are workaroundable through the available search and history tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources