mcp-registry/es.mapasocietario/borme · v1.0.0
Also listed as glama/anbrme/mapa-societario
As of 2026-10-19 13:58 UTC, the Mapasocietario Borme MCP server is up (it requires sign-in) with a Glimind reliability score of 72/100 (grade C). Over the last 30 days it answered 97.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 74.4 hours.
Spanish company registry (BORME): companies, directors, links. Needs a free work-email account.
Claude Code
claude mcp add --transport http mapasocietario-borme-mcp-server https://mcp.mapasocietario.es/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"mapasocietario-borme-mcp-server": {
"type": "http",
"url": "https://mcp.mapasocietario.es/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Reachable 97.9% of the time over the last 30 days; median recovery 4465 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~1,988 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fes.mapasocietario%2Fborme/fixes
{
"name": "get_company",
"description": "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/managem",
"inputSchema": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Company name (fuzzy-resolved to one entity)."
},
"slug": {
"type": "string",
"description": "A mapasocietario /empresa slug, e.g. 'acme-sl'."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_company_network",
"description": "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, and 'superseded'",
"inputSchema": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Company name (fuzzy-resolved)."
},
"slug": {
"type": "string",
"description": "A mapasocietario /empresa slug."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "search_companies",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"limit": {
"type": "number",
"description": "Max results (1-25, default 10)."
},
"query": {
"type": "string",
"description": "Company name or partial name."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/es.mapasocietario/borme"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/es.mapasocietario/borme"}) over MCP.
get_company ~212 tokenssearch_officers ~209 tokensget_company_network ~206 tokenssearch_companies ~198 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fes.mapasocietario%2Fborme?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fes.mapasocietario%2Fborme?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fes.mapasocietario%2Fborme.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fes.mapasocietario%2Fborme.svg :target: https://glimind.com/server/mcp-registry%2Fes.mapasocietario%2Fborme?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1a61c050d4794e9c…, first seen 2026-10-17, included at leaf 12651 of 27,254. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 13:58 UTC, the Mapasocietario Borme MCP server is up (it requires sign-in) with a Glimind reliability score of 72/100 (grade C). Over the last 30 days it answered 97.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 74.4 hours.
Mapasocietario Borme MCP server advertises 4 tools, including get_company, get_company_network, search_companies, search_officers.
Point your MCP client at this streamable-http endpoint: https://mcp.mapasocietario.es/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.