BORME API MCP server
com.bormeapi/borme-mcpbormeapi.comstreamable-httpv2.1.0Scanned
Spain's company registry gazette (BORME): more than 9.6 million events since 2009. API key or OAuth.
13 tools: 2 change things and 11 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the BORME API MCP server can do
The BORME API MCP server is published by bormeapi.com, a domain the MCP Registry verified. It has 13 tools. It can create or change data (2 tools: company_by_nif and registry_stats), but cannot delete data. 11 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 2.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Changes things 2Claude Code: ask
company_by_nifLook up a Spanish company by its NIF/CIF tax ID.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Look up a Spanish company by its NIF/CIF tax ID. Use it when the user gives a tax ID (with a name use search_companies); on a hit, call company_history with company_slug. Returns JSON {found, company_slug, current_name, status, nif_source, nif_caveat, ...}; use current_name. BORME has no dedicated tax-ID field: more than 580,000 NIF mappings from public sources and the text of BORME notices cover a minority of companies, so a miss (reason nif_unmapped) means "not matched yet", not "does not exist". reason nif_revoked: AEAT records a revocation; relay tell_the_user. On a company match, relay nif_status.note if present. invalid_input true: not a NIF/CIF. reason nif_check_character_failed: relay tell_the_user and did_you_mean. reason not_registry_entity: explain entity_type. ambiguous true: ask which candidate. nif_caveat present: say the link is not settled. Read-only. Needs the basic plan or higher: send your API key in the X-API-Key header (https://bormeapi.com/account).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Find a company by NIF
registry_statsReport the coverage and freshness of the BORME data behind this server.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Report the coverage and freshness of the BORME data behind this server. Use it to answer "how much data is there?", "how fresh is it?" and "can I trust date filters for period X?" before running searches; it says nothing about any one company. Returns JSON {events_approx, companies_approx, coverage: {from, to}, parse_completeness_last_30d, source}: exact event and company counts from the latest hourly snapshot (planner estimates if no snapshot exists), the first and latest publication day held (YYYY-MM-DD), and the event-weighted parse completeness over the 30 days up to the latest run (e.g. 0.9987). Takes no arguments. Read-only, open to everyone, no key needed and not counted against a quota. The same report is the resource borme://coverage.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Data coverage and freshness
Only reads 11Show 11 read-only tools
act_statsCount BORME acts by act type, period (month, quarter or year) and province: how many companies and entries had mergers, spin-offs, capital increases or any other act type, newest p…No findings
Why it is in this group
- The description's first verb is "count": a word for reading.
Description, as the server wrote it Count BORME acts by act type, period (month, quarter or year) and province: how many companies and entries had mergers, spin-offs, capital increases or any other act type, newest period first. Use it for trends ("mergers per quarter in Spain since 2020"). To read the acts themselves use search_events. Returns JSON {grain, count, truncated, rows: [{period, act_type, province, companies, events}], data_through, built_from, built_to, note, plan_window}, plus hidden_by_plan when the plan left buckets out, and not_built (no rows, never zeros) when the range reaches years outside built_from..built_to. period is the bucket's first day by BORME publication date. companies counts distinct companies in that bucket: never add rows up. Province "*" is all of Spain; a community gives one row per province, not a total. Read-only; one request per call. Needs the pro plan or higher: send your key in the X-API-Key header (https://bormeapi.com/account).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Act counts by type, period and province
brand_ownerFind the Spanish company a trademark or trading name is linked to, in the Spanish patent office's (OEPM) trademark and commercial-name records we hold (the archive starts in 1987).No findings
Why it is in this group
- The description's first verb is "find": a word for reading.
Description, as the server wrote it Find the Spanish company a trademark or trading name is linked to, in the Spanish patent office's (OEPM) trademark and commercial-name records we hold (the archive starts in 1987). Use it when the user names a brand; for a company's own name use search_companies, for a known company's brands use company_brands. Returns JSON {found, brand, matches: [{brand, kind, company_slug, company_name, company_status, file}], truncated, source, note}. kind commercial_name identifies a business; trademark distinguishes goods or services (NESCAFÉ is not another name for Nestlé): say which kind a hit is. Links come from holder-name matching (the office publishes no tax IDs); ambiguous holders stay unlinked: present a hit as a name match, not confirmed ownership. found false is not proof the brand is unused. On a hit, use company_history with the slug. Read-only; one request per call. Needs the basic plan or higher: send your API key in the X-API-Key header (https://bormeapi.com/account).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Find a brand's company
company_brandsList the trademarks and trading names that the Spanish patent office (OEPM) records under a holder with this company's name.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List the trademarks and trading names that the Spanish patent office (OEPM) records under a holder with this company's name. Use it for a known company (a slug from search_companies or company_history); to go from a brand to its company use brand_owner. Returns JSON {company_slug, commercial_names, trademarks (each {name, file, status, since}), counts, truncated, limit_per_kind, source, note}. The office publishes no tax IDs, so every link is a name match, not confirmed ownership. An empty result means none is linked in our data, not that the company holds none; {error, suggested_companies} means no company was found with that slug, so nothing was looked up. limit applies to each kind separately, newest first; counts is what this answer lists, not the company's total, and truncated true for a kind means more are linked: raise limit. Read-only; one request per call. Needs the basic plan or higher: send your API key in the X-API-Key header (https://bormeapi.com/account).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: A company's brands
company_historyGet one company's BORME timeline: its published registry events within your plan's window.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get one company's BORME timeline: its published registry events within your plan's window. Use it once the company is known (a slug from search_companies or company_by_nif); across many companies use search_events. A name is searched too: several matches return {ambiguous: true, candidates}, none returns {error, suggested_companies}. Returns JSON {company_slug, total_events, first_seen, last_seen, truncated, next_offset, count, events} (as in search_events), with former_slugs for a merged company (an old slug returns the merged timeline) and plan_window on a limited plan. total_events, first_seen and last_seen cover the whole timeline in your window, not this page. To page, keep limit and order and pass next_offset as offset (at most 10000) until it is null. Read-only; one request per call. Without an API key (X-API-Key header) only the last 7 days; basic covers 365 days, pro and risk the full history back to 2009. If all its events are outside your window, the refusal counts them.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Company registry timeline
company_signalsGet one company's derived signals within your plan's window, newest first: the REST API's GET /v1/companies/{slug}/signals.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get one company's derived signals within your plan's window, newest first: the REST API's GET /v1/companies/{slug}/signals. Use it for one company's ownership changes, mass exits, insolvency declarations and the like; across all companies use recent_signals. A name is searched as in company_history: several matches return {ambiguous: true, candidates}, none returns {error, suggested_companies}. Returns JSON {company_slug, total, count, next_offset, signals: [{event_id, signal_type, date, company_slug, company_name, province, details}]}, with former_slugs for a merged company (every slug is read), and plan_window or hidden_by_plan when your plan's window applied: relay their notes. AEAT_DEBTOR: say the company was on the list published on that date, never that the debt is outstanding. count 0 is not proof of good health. Read-only; one request per call. Needs the pro plan or higher; key in the X-API-Key header (https://bormeapi.com/account).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: A company's signals
company_snapshotGet one company's current registry card: the same answer as the REST API's GET /v1/companies/{slug}.No findings
Why it is in this group
- The name "company_snapshot" says "snapshot": a word for reading.
Description, as the server wrote it Get one company's current registry card: the same answer as the REST API's GET /v1/companies/{slug}. Use it for "who runs it, who owns it, what capital": officers (the current roles derived from the published acts), sole_shareholder as printed, capital_eur, address, status, NIF with its source, public_contracts and a size_hint estimate. For the dated acts use company_history. A name is searched as in company_history: several matches return {ambiguous: true, candidates, candidate_names with name, province and status}, none returns {error, suggested_companies}. Returns JSON with company_slug, company_name, current_name, status, officers, sole_shareholder, capital_eur, nif, nif_caveat, sources and the other snapshot fields, plus former_slugs for a merged company. BORME publishes no minority shareholdings, employees or revenue. Read-only; one request per call. Needs the basic plan or higher: send your API key in the X-API-Key header (https://bormeapi.com/account).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Company registry card
daily_digestSummarise one BORME publication day: total events, counts by act type, the top 10 provinces and the day's insolvency-proceedings notices.No findings
Why it is in this group
- The description's first verb is "summarise": a word for reading.
Description, as the server wrote it Summarise one BORME publication day: total events, counts by act type, the top 10 provinces and the day's insolvency-proceedings notices. Use it for "what was published today" or a day's figures; to read the notices use search_events with date_from = date_to = that day. Returns JSON {date, total_events, by_type, top_provinces, insolvencies: [{company, province}]}. insolvencies lists the events with INSOLVENCY_DECLARATION or INSOLVENCY_STATUS (not SUSPENSION_OF_PAYMENTS, BANKRUPTCY_LEGACY or PROVISIONAL_SHEET_CLOSURE_INSOLVENCY). An INSOLVENCY_STATUS notice can record any stage, from a request for a declaration to the conclusion: before saying a company was declared insolvent, read the act's payload with search_events. A day without a gazette (weekends, holidays) returns total_events 0. Read-only; one request per call. Without an API key only days within the last 7 days; send your key in the X-API-Key header (https://bormeapi.com/account) for your plan's window.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Daily BORME digest
list_act_typesList every normalized BORME act type: the enum used by the act_types filter of search_events (act_type), its Spanish label (spanish) and its English label (english).No findings
Why it is in this group
- The name "list_act_types" says "list": a word for reading.
Description, as the server wrote it List every normalized BORME act type: the enum used by the act_types filter of search_events (act_type), its Spanish label (spanish) and its English label (english). Use it to choose act_types values or to translate act types in an answer; it reads no registry data. Returns a JSON array of {act_type, spanish, english}, sorted by act_type. Read-only, open to everyone, no key needed and not counted against a quota. The same list is the resource borme://act-types.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: List act types
recent_signalsGet a sample of the latest risk signals derived from BORME and public sources: at most 10 rows dated within the last 7 days.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get a sample of the latest risk signals derived from BORME and public sources: at most 10 rows dated within the last 7 days. Use it for "what risk signals appeared this week"; not a per-company check (use company_history) and not the full feed (the hosted API's /v1/signals). Returns JSON {count, window, sample_cap, signals: [{signal_type, date, company_slug, company_name, province, details}], full_feed}. AEAT_DEBTOR comes from the AEAT's yearly debtors list (art. 95 bis LGT): details carry listed_on, list_year, is_current_list (true for 12 months from listed_on) and debt_eur, the published total at 31 December of the prior year. Say the company was on the list published on that date; never say the debt is still outstanding. count 0 means none in the window, not that a company is risk-free; an unknown signal_type is refused with the valid list. Read-only; one request per call. Needs the risk plan: send your API key in the X-API-Key header (https://bormeapi.com/account).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Recent risk signals
search_companiesFind Spanish companies by name and return ranked company cards.No findings
Why it is in this group
- The name "search_companies" says "search": a word for reading.
Description, as the server wrote it Find Spanish companies by name and return ranked company cards. Use it first when the user gives a company name, then company_history with its company_slug; with a tax ID use company_by_nif, with a brand use brand_owner. Matches current names, former names and variants, ignoring accents, case, punctuation and the legal form. Returns JSON {query, count, total, total_is_at_least, truncated, limit, offset, companies: [{company_slug, name, legal_form, province, municipality, status, in_insolvency, last_act_date, match, matched_on}]}. match is exact, prefix, contains or fuzzy (a lead, not an identification; say so). Ranked by match, then active companies, then newest act. Read-only; one request per call; not limited by the free plan's 7 days of history. The free plan shows at most the first 5 ranked cards; hidden_by_plan counts the rest: relay its note. The NIF is on the card from the basic plan up (X-API-Key header). An empty answer is not proof that a business does not exist.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Search companies by name
search_eventsSearch BORME registry events (since 2009) across companies by publication date, province, act type and company name, newest first.No findings
Why it is in this group
- The name "search_events" says "search": a word for reading.
Description, as the server wrote it Search BORME registry events (since 2009) across companies by publication date, province, act type and company name, newest first. Use it for questions about many companies ("insolvency notices in Valencia in September"). For one known company use company_history; to find a company use search_companies; for one day's totals use daily_digest. Returns JSON {count, events: [{event_id, date, borme_id, province, company_name, company_slug, acts: [{act_type, act_type_raw, roles, payload}], registral}]}, plus company_name_match, plan_window and hidden_by_plan when they apply. No next page: when count equals limit, narrow the filters. Read-only; one request per call against your daily quota. Without an API key (X-API-Key header, https://bormeapi.com/account) only the last 7 days are searched (plan_window). For an empty page with hidden_by_plan or company_name_match (matched_companies or suggested_companies), relay its note. Invalid dates, provinces or act types are refused with a reason.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Search registry events
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:23 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.bormeapi.com/mcp: tools/list returned 18 tools to an anonymous client, including company_by_nif (write), vat_check (write), registry_stats (write)
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 2 to 3
- Nov 6, 2026
- Tools that change things, listed without credentials: 6 to 2
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
- Tools that change things, listed without credentials: 2 to 3
Tools3 added, 7 changed.+3 added~7 changedView diff
- Added:act_statsOnly reads
- Added:company_signalsOnly reads
- Added:company_snapshotOnly reads
- Changed:brand_ownerOnly readsinputSchema
- Changed:company_brandsOnly readsdescriptioninputSchema
- Changed:company_by_nifChanges thingsdescription
- Changed:company_historyOnly readsdescriptioninputSchema
- Changed:registry_statsChanges thingsdescription
- Changed:search_companiesOnly readsinputSchema
- Changed:search_eventsOnly readsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 2.View diff
- Tools that change things, listed without credentials: 6 to 2
Tools10 changed.~10 changedView diff
- Changed:brand_ownerOnly readstitledescriptioninputSchemaannotations
- Changed:company_brandsOnly readstitledescriptioninputSchemaannotations
- Changed:company_by_nifChanges thingstitledescriptioninputSchemaannotations
- Changed:company_historyOnly readstitledescriptioninputSchemaannotations
- Changed:daily_digestOnly readstitledescriptioninputSchemaannotations
- Changed:list_act_typesOnly readstitledescriptionannotations
- Changed:recent_signalsOnly readstitledescriptioninputSchemaannotations
- Changed:registry_statsChanges thingstitledescriptionannotations
- Changed:search_companiesOnly readstitledescriptioninputSchemaannotations
- Changed:search_eventsOnly readstitledescriptioninputSchemaannotations
Install
Pinned to version 2.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http borme https://mcp.bormeapi.com/mcpclaude mcp add --transport http borme https://mcp.bormeapi.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__borme__search_events",
"mcp__borme__company_history",
"mcp__borme__company_snapshot",
"mcp__borme__company_signals",
"mcp__borme__brand_owner",
"mcp__borme__company_brands",
"mcp__borme__recent_signals",
"mcp__borme__daily_digest",
"mcp__borme__act_stats",
"mcp__borme__search_companies",
"mcp__borme__list_act_types"
],
"ask": [
"mcp__borme__company_by_nif",
"mcp__borme__registry_stats"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as borme. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.bormeapi/borme-mcp/verify?hash=8ca47e026becc437aee8e028c8a4b8fad5061fb3820f42940785a646d5f2e504" | jq -e '.changed == false'Pinned hash 8ca47e026bec, from Nov 11, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.bormeapi/borme-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.bormeapi/borme-mcp)Source: MCP Registry · repository. Synced Oct 30, 2026, 03:17 UTC.
BORME API MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BORME API MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the BORME API MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the BORME API MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the BORME API MCP server have?
- 13 tools: 2 write, 11 read. company_by_nif, registry_stats, search_events, company_history, company_snapshot, company_signals, brand_owner, company_brands and 5 more.
Does the BORME API MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BORME API MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the BORME API MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.