es.atareao/blog
REMOTE · ATAREAO.ES
Consulta pública y de solo lectura del contenido publicado en atareao.es.
Available components
Last scanned (4 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 178 tokens (~59/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Server version: 1.19.0 → 1.22.0 functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 71
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 5 Nov 2026 · Probed https://atareao.es/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=atareao.es | CN=YR1,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | RSA 4096 | SHA256-RSA | 615bcc84e506e3dc5713b1dc74474fbc81b |
| SANs: atareao.es, www.atareao.es | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of atareao.es. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| es. | present | 4901, 54404 | 8, 8 | Verified |
| atareao.es. | 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 | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self' https:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://atareao.es https://umami.atareao.es; style-src 'self' 'unsafe-inline'; font-src 'self' data: https://atareao.es; connect-src 'self' https://umami.atareao.es; img-src 'self' data: https://atareao.es https://secure.gravatar.com; worker-src 'self' blob:; frame-src 'self' https: blob:; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://atareao.es/mcp | Verified | 200 | |
| http (plaintext) | http://atareao.es/mcp | HTTPS enforced | 301 | https://atareao.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_latest_posts ~60
Devuelve las últimas entradas publicadas y públicas del blog (solo lectura).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Número máximo de entradas a devolver (1-50). |
| post_type | string | – | Restringe los resultados a un tipo de contenido público. |
No output schema declared.
No examples provided.
get_post ~37
Devuelve una entrada publicada y pública por su ID (solo lectura).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The unique ID of the post to retrieve. |
No output schema declared.
No examples provided.
search_posts ~81
Busca entradas publicadas y públicas por texto (solo lectura).
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Página solicitada (>=1). |
| per_page | integer | – | Resultados por página (1-50). |
| post_type | string | – | Restringe los resultados a un tipo de contenido público. |
| query | string | yes | The search term or query string. |
No output schema declared.
No examples provided.
How do I install the es.atareao/blog MCP server?
es.atareao/blog is a hosted endpoint at https://atareao.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 · atareao.es
claude mcp add --transport http es-atareao-blog 'https://atareao.es/mcp'
What is the es.atareao/blog MCP server?
es.atareao/blog is an MCP server listed in the public MCP registry as es.atareao/blog. Consulta pública y de solo lectura del contenido publicado en atareao.es. This page covers its hosted endpoint (https://atareao.es/mcp).
Is the es.atareao/blog MCP server safe to use?
es.atareao/blog scores 73 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 es.atareao/blog MCP server expose?
es.atareao/blog exposes 3 tools: get_latest_posts, get_post, search_posts. Their descriptions and schemas cost roughly 178 tokens of context every time the server is loaded.
Does the es.atareao/blog MCP server require authentication?
No. We connected to es.atareao/blog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the es.atareao/blog MCP server still maintained?
es.atareao/blog is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.