borme-registry

BORME — the gazette of Spain's commercial registry

The borme MCP server holds the company notices of BORME Section A since 2009, parsed into typed events, plus tax-ID and trademark lookups. This skill says which tool to call, how to chain them, and how to report what comes back. Each tool's description and parameter schema explain its parameters; read them too.

Connect

The hosted endpoint is https://mcp.bormeapi.com/mcp (Streamable HTTP). It works without a key on the free plan. With a key, send it in the X-API-Key header:

• Claude Code: claude mcp add --transport http borme https://mcp.bormeapi.com/mcp --header "X-API-Key: YOUR_KEY"
• Clients configured with JSON (Cursor's mcp.json and similar): {"mcpServers": {"borme": {"url": "https://mcp.bormeapi.com/mcp", "headers": {"X-API-Key": "YOUR_KEY"}}}}

Keys: https://bormeapi.com/account. Plans and prices: https://bormeapi.com/pricing.

If the borme tools are not available in this session, say the BORME MCP server is not connected, give the user the lines above, and do not answer from memory.

What each plan includes

• No key (free): search_events, company_history and daily_digest over the last 7 days; list_act_types and registry_stats. 50 calls a day per IP address.
• basic: the last 365 days, plus company_by_nif, brand_owner and company_brands.
• pro: everything in basic, with the full history back to 2009.
• risk: everything in pro, plus recent_signals.

When an answer carries plan_window, the plan's window was applied (company_history carries it on every free or basic answer). Tell the user once, in one sentence, and say what covers the rest: a key for the last 365 days (basic), pro for the full history. Do not retry with older dates — the server cuts them the same way — and do not take an empty result as proof that nothing happened earlier.

A refusal that names a plan, or says a company's notices lie outside the window, is not a server failure: relay its message, say which plan covers it, and do not retry.