Koskamo

BORME API MCP

An official Model Context Protocol server provided by BORME API that allows AI assistants to access Spain's official company registry (BORME) data. It enables resolving companies, reconstructing published histories, searching by name or NIF, monitoring changes, and exposing officers and brands with official-source provenance.

Visit BORME API

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

BORME API MCP logo, by BORME APIVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by BORME API
You need:You sign in with your BORME API accountyour API key in the X-API-Key headercalls count against your plan's daily quota
MCP endpoint (Streamable HTTP)
https://mcp.bormeapi.com/mcp/oauth
Vendor documentation

What you can do with it

  • Resolve a company by NIF or registry sheet to get officers and status
  • Reconstruct published company history and timeline from gazette notices
  • Monitor companies for new published events or risk signals via webhooks
  • Search for companies by name or expose officers and brands

Source and maintenance

Vendor evidenceRegistry 2.1.0
mcp-registry: com.bormeapi/borme-mcp@2.1.0Source repositoryProject website
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
779 ms
95th percentile latency
779 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 779 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http borme-api-mcp-bormeapi https://mcp.bormeapi.com/mcp/oauth

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add borme-api-mcp-bormeapi --url https://mcp.bormeapi.com/mcp/oauth

Cursor

Merge this server into .cursor/mcp.json in your project, then enable borme-api-mcp-bormeapi in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "borme-api-mcp-bormeapi": {
      "url": "https://mcp.bormeapi.com/mcp/oauth"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "borme-api-mcp-bormeapi": {
      "type": "streamableHttp",
      "url": "https://mcp.bormeapi.com/mcp/oauth",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start borme-api-mcp-bormeapi and inspect its tools.
VS Code configuration
{
  "servers": {
    "borme-api-mcp-bormeapi": {
      "type": "http",
      "url": "https://mcp.bormeapi.com/mcp/oauth"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http borme-api-mcp-bormeapi https://mcp.bormeapi.com/mcp/oauth

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "borme-api-mcp-bormeapi": {
      "url": "https://mcp.bormeapi.com/mcp/oauth"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "borme-api-mcp-bormeapi": {
      "serverUrl": "https://mcp.bormeapi.com/mcp/oauth"
    }
  }
}

Let your agent find its tools

Find servers like BORME API MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 4,752

Do you run BORME API MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing