Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Datos: Spanish Open Data

REMOTE · DATOS.AUTOMATE-IT-ALL.WIN · SCANNED SEP 20

BOE, Spanish public tenders and INE statistics behind one MCP server.

0 this week 18 Trust /100
Trust breakdown (7 categories)

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 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.

Install

How do I install the Datos: Spanish Open Data MCP server?

Datos: Spanish Open Data is a hosted endpoint at https://datos.automate-it-all.win/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 · datos.automate-it-all.win

# add to Claude Code
claude mcp add --transport http win-automate-it-all-datos 'https://datos.automate-it-all.win/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "win-automate-it-all-datos": {
      "url": "https://datos.automate-it-all.win/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "win-automate-it-all-datos": {
      "type": "http",
      "url": "https://datos.automate-it-all.win/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.win-automate-it-all-datos]
url = "https://datos.automate-it-all.win/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "win-automate-it-all-datos": {
      "type": "remote",
      "url": "https://datos.automate-it-all.win/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add win-automate-it-all-datos --url 'https://datos.automate-it-all.win/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  win-automate-it-all-datos:
    url: "https://datos.automate-it-all.win/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "win-automate-it-all-datos": {
      "Transport": "http",
      "Url": "https://datos.automate-it-all.win/mcp"
    }
  }
}
# add to Vellum
assistant mcp add win-automate-it-all-datos -t streamable-http -u 'https://datos.automate-it-all.win/mcp'
// mcp.json
{
  "mcpServers": {
    "win-automate-it-all-datos": {
      "type": "http",
      "url": "https://datos.automate-it-all.win/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 19 Sept 26 −52
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.37 → unverified security
    • Tool safety: pass → unverified security
    • Authorization: fail → unverified security
    • Transport: pass → fail security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
  • 18 Sept 26 +52
    • Authorization: unverified → fail security
    • Injection markers: unverified → pass security
    • Transport: fail → pass security
    • Endpoint reachability: not serving MCP → reachable functional
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.37 functional
  • 16 Sept 26 −50
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.27 → unverified security
    • Tool safety: pass → unverified security
    • Authorization: fail → unverified security
    • Transport: pass → fail security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
  • 14 Sept 26 +50
    • Authorization: unverified → fail security
    • Injection markers: unverified → pass security
    • Transport: fail → pass security
    • Endpoint reachability: not serving MCP → reachable functional
    • Tool coverage: unverified → 100 functional
    • Stability: unverified → 0.23 functional
    • MCP protocol: unverified → pass functional
  • 10 Sept 26 −48
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.07 → unverified security
    • Tool safety: pass → unverified security
    • Authorization: fail → unverified security
    • Transport: pass → fail security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
  • 9 Sept 26 +48
    • Authorization: unverified → fail security
    • Injection markers: unverified → pass security
    • Transport: fail → pass security
    • Endpoint reachability: not serving MCP → reachable functional
    • Tool coverage: unverified → 100 functional
    • Stability: unverified → 0.07 functional
    • MCP protocol: unverified → pass functional
  • 8 Sept 26 −47
    • Endpoint reachability: reachable → not serving MCP security
    • Tool safety: pass → unverified security
    • Authorization: fail → unverified security
    • Transport: pass → fail security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 7 Sept 26 65

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Probed https://datos.automate-it-all.win/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=automate-it-all.win CN=WE1,O=Google Trust Services,C=US 5 Sept 2026 4 Dec 2026 ECDSA 256 ECDSA-SHA256 752515d0e66b260e0e3a7d9a30cafcef
SANs: automate-it-all.win, *.automate-it-all.win
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 datos.automate-it-all.win. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
win. present 29737 8 Verified
automate-it-all.win. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 530
Header Value
x-frame-options SAMEORIGIN
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://datos.automate-it-all.win/mcp HTTP error 530
http (plaintext) http://datos.automate-it-all.win/mcp Inconclusive 530
MCP tools · 5 exposed · ~185 tokens

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 →

Tool Tokens
boe_day ~37

Every BOE item published on ymd (YYYYMMDD).

NameTypeReqDescription
limitinteger
ymdstringyes

No output schema declared.

No examples provided.

boe_search ~34

Full-text search over BOE item titles and text.

NameTypeReqDescription
limitinteger
querystringyes

No output schema declared.

No examples provided.

ine_series ~29

Latest values of one INE series by code (see series.txt).

NameTypeReqDescription
codestringyes

No output schema declared.

No examples provided.

info ~14

Contact and scope of this server.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tenders_search ~71

Search public tenders by text, CPV prefix, budget range, deadline.

NameTypeReqDescription
cpvstring
deadline_afterstring
limitinteger
max_budgetnumber
min_budgetnumber
querystring

No output schema declared.

No examples provided.

Common questions

What is the Datos: Spanish Open Data MCP server?

Datos: Spanish Open Data is an MCP server listed in the public MCP registry as win.automate-it-all/datos. BOE, Spanish public tenders and INE statistics behind one MCP server. This page covers its hosted endpoint (https://datos.automate-it-all.win/mcp).

Is the Datos: Spanish Open Data MCP server safe to use?

Datos: Spanish Open Data scores 18 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 Datos: Spanish Open Data MCP server expose?

Datos: Spanish Open Data exposes 5 tools: info, boe_search, boe_day, tenders_search, ine_series. Their descriptions and schemas cost roughly 185 tokens of context every time the server is loaded.

Does the Datos: Spanish Open Data MCP server require authentication?

No. We connected to Datos: Spanish Open Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Datos: Spanish Open Data MCP server still maintained?

Datos: Spanish Open Data is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.