Mapa Societario — Spanish Company Registry (BORME)
REMOTE · MCP.MAPASOCIETARIO.ES
Spanish company registry (BORME): companies, directors, how they connect. Needs a free work account.
Available components
Last scanned (6 hours ago)
Scores higher than 30% of remote servers
Reachable. Last reached 23 Oct 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 +14
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- Transport: fail → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: pass security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://mcp.mapasocietario.es/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mapasocietario.es | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 72e340e1c16e336c0e26256ef529fa7d |
| SANs: mapasocietario.es, mcp.mapasocietario.es, *.mcp.mapasocietario.es | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.mapasocietario.es. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| es. | present | 54404 | 8 | Verified |
| mapasocietario.es. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.mapasocietario.es/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.mapasocietario.es/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.mapasocietario.es/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://mcp.mapasocietario.es/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.mapasocietario.es/mcp |
| Authorisation server | https://clerk.mapasocietario.es |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.mapasocietario.es/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.mapasocietario.es/mcp | HTTPS enforced | 301 | https://mcp.mapasocietario.es/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_company ~301
Get the BORME registry profile of one Spanish company: status, incorporation, current and former officers, sole shareholder (BORME records only sole-shareholder ownership), and — where available — NIF, share capital and registered address. NIF is never in BORME, and capital/address are missing for entities last amended before 2009; such values may be filled by web search and are flagged `*_external: true` (verify before relying on them). Officers are capped at the 25 most relevant (board/management before apoderados) with `*_officers_total` counts and an `officers_truncated` flag — large companies register hundreds of apoderados. Includes a mapasocietario.es link to cite. Resolves to exactly one entity by its current OR former name (company renames are handled) and returns not-found rather than a near-miss — if unsure of the exact name, call search_companies first. `name` is always the company's CURRENT name; if you queried an old name (or the result's name looks unrelated to your query), check `former_names` — it lists every prior registered name (registry-recorded 'Cambio de denominación social') before assuming this is the wrong company.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Company name (fuzzy-resolved to one entity). |
| slug | string | – | A mapasocietario /empresa slug, e.g. 'acme-sl'. |
No output schema declared.
No examples provided.
get_company_network ~197
Show companies directly connected to one Spanish company: via a shared board/management officer (shared_officer — apoderados and representatives are excluded as low-signal), via being owned by it (owns), or via owning it (owned_by). Answers 'is there a relationship between company X and company Y?'. shared_officer edges carry `status`: 'active' means the shared officer still holds the seat at the connected company, 'ceased' means the registry has inscribed their cessation there — a ceased edge is a HISTORICAL link, do not report it as a current one. Active edges are listed first, so a truncated list keeps the live relationships. Resolves to one entity by current or former name (renames handled). Each connection links to mapasocietario.es.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Company name (fuzzy-resolved). |
| slug | string | – | A mapasocietario /empresa slug. |
No output schema declared.
No examples provided.
search_companies ~143
Search Spanish companies by name in the BORME registry. Returns ranked matches (fuzzy — tolerant of typos) with status and a mapasocietario.es/empresa link to cite. A hit's `name` is always its CURRENT registered name; when the entity has been renamed, `former_names` lists its prior name(s) — a hit whose `name` differs from your query is not necessarily a wrong match, check `former_names` first. Use this first to resolve a company before get_company.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (1-25, default 10). |
| query | string | yes | Company name or partial name. |
No output schema declared.
No examples provided.
search_officers ~322
Find a person (administrator/director/apoderado) in the BORME registry and list the companies they are linked to. Answers 'is officer Z present in other companies?'. Returns ONE row per company, with `roles` listing every post held there. `status` (per row and per role) is 'active' when the appointment is still in force and 'ceased' once the registry has inscribed the cessation — never describe a ceased role as a current directorship. Each role also carries `date` where the registry recorded one: the APPOINTMENT date for an active role, the CESSATION date for a ceased one — read it against that role’s status, never as a single “since”. When the officer held the seat before that (a revoke-and-reappoint, common in Spanish registries), the role also carries `first_appointed` — cite THAT for “since when”, not `date` — and `history`, every published act newest-first. Companies where the person is still in office come first, so a truncated list keeps the live ones. `companies_total`/`companies_active` count COMPANIES and `seats_total` counts appointment rows — cite the company figures when asked how many companies someone sits on. `counts_are_lower_bound: true` means more companies exist than could be read. Each row links to mapasocietario.es/empresa.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max rows (1-25, default 10). |
| name | string | yes | Person name or partial name. |
No output schema declared.
No examples provided.
How do I install the Mapa Societario — Spanish Company Registry (BORME) MCP server?
Mapa Societario — Spanish Company Registry (BORME) is a hosted endpoint at https://mcp.mapasocietario.es/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.mapasocietario.es
claude mcp add --transport http es-mapasocietario-borme 'https://mcp.mapasocietario.es/mcp'
What is the Mapa Societario — Spanish Company Registry (BORME) MCP server?
Mapa Societario — Spanish Company Registry (BORME) is an MCP server listed in the public MCP registry as es.mapasocietario/borme. Spanish company registry (BORME): companies, directors, how they connect. Needs a free work account. This page covers its hosted endpoint (https://mcp.mapasocietario.es/mcp).
Is the Mapa Societario — Spanish Company Registry (BORME) MCP server safe to use?
Mapa Societario — Spanish Company Registry (BORME) scores 37 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mapa Societario — Spanish Company Registry (BORME) MCP server expose?
Mapa Societario — Spanish Company Registry (BORME) exposes 4 tools: search_companies, get_company, search_officers, get_company_network. Their descriptions and schemas cost roughly 963 tokens of context every time the server is loaded.
Does the Mapa Societario — Spanish Company Registry (BORME) MCP server require authentication?
Yes. Mapa Societario — Spanish Company Registry (BORME) asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Mapa Societario — Spanish Company Registry (BORME) MCP server still maintained?
Mapa Societario — Spanish Company Registry (BORME) is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.