Aerset · normativa de drones en España
REMOTE · MCP.AERSET.COM
Normativa española de drones con fuente y fecha por regla: pasajes citables, zonas UAS, requisitos.
Available components
Last scanned (21 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Maps and Location
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 Security80
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1405 tokens (~281/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://mcp.aerset.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aerset.com | CN=WR3,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | RSA 2048 | SHA256-RSA | ffbabe28c5db3ac40aa96233bf366eae |
| SANs: aerset.com, *.aerset.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.aerset.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aerset.com. | 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 |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.aerset.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.aerset.com/mcp | HTTPS enforced |
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 →
flight_requirements Trámites que exige un vuelo ~325
Calcula, con el motor determinista de Aerset, qué trámites exige la normativa para volar en un punto de España, en una fecha y con una aeronave concreta: qué régimen de la categoría abierta aplica por peso y marcado de clase, qué zonas UAS publica ENAIRE sobre el punto, qué espacios protegidos constan en MITECO y quién autoriza cada cosa, con el plazo que el catálogo atribuye a cada trámite. Cada línea nombra la autoridad que la exige y la fuente con su fecha de revisión. NO concede permisos, no tramita nada y no afirma que la operación pueda realizarse: el campo `not_covered` enumera las fuentes que esta respuesta no consulta (NOTAM, terreno, obstáculos, meteo). La decisión es del operador y se consulta con AESA. · Runs Aerset's deterministic permit engine over a point, a date and an aircraft in Spain and returns the requirement list: the open-category regime for that weight and class marking, the UAS zones ENAIRE publishes over the point, the protected areas MITECO records, and who demands each item with the lead time our catalogue attributes to it. It grants nothing and files nothing; `not_covered` names the sources it does not consult, and the decision stays with the operator and the authority.
| Name | Type | Req | Description |
|---|---|---|---|
| class_marking | – | – | – |
| date | – | – | – |
| drone_weight_g | – | – | – |
| environment | string | – | – |
| lat | number | yes | – |
| lon | number | yes | – |
| night | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | – |
| available | boolean | – | – |
| checked_at | string | – | – |
| covered | boolean | – | – |
| disclaimer | string | – | – |
| for_date | – | – | – |
| invalid_arguments | – | – | – |
| judged_at_height_m | – | – | – |
| lat | number | – | – |
| lon | number | – | – |
| nearest_aerodrome_km | – | – | – |
| not_covered | array | – | – |
| note | – | – | – |
| protected_areas | array | – | – |
| protected_available | boolean | – | – |
| regime | – | – | – |
| requirements | array | – | – |
| viewer_url | – | – | – |
| zones | array | – | – |
| zones_available | boolean | – | – |
No examples provided.
rules_catalogue Catálogo de trámites ~214
Devuelve el catálogo completo de trámites que Aerset mantiene para volar un dron en España, regla a regla: su código, su título, la autoridad que la exige, las condiciones en las que aplica, el plazo que le atribuimos y si ese plazo está comprobado contra la fuente o no, más la URL de la fuente y la fecha en que se revisó. Es el conjunto sobre el que trabaja `flight_requirements`, publicado para poder citarlo entero. Una regla sin `reviewed_at` no dice nada, y con `lead_time_verified: false` el plazo NO está comprobado. · Returns Aerset's whole catalogue of Spanish drone paperwork, rule by rule: code, title, the authority that demands it, the conditions under which it applies, the lead time we attribute to it and whether that lead time has been checked against the source, plus the source URL and the review date. It is the set `flight_requirements` evaluates, published so it can be cited whole.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | – |
| available | boolean | – | – |
| checked_at | string | – | – |
| disclaimer | string | – | – |
| invalid_arguments | – | – | – |
| licence | – | – | – |
| licence_url | – | – | – |
| note | – | – | – |
| reviewed_through | – | – | – |
| rules | array | – | – |
No examples provided.
search_regulation Buscar en la normativa ~211
Busca en el corpus normativo de drones de España: BOE, Reglamento (UE) 2019/947, guías de AESA y EASA, y MITECO. Devuelve PASAJES literales con el título del documento, su URL y su fecha — no un resumen y no una conclusión. Úsalo para citar la norma con su fuente y su fecha. Lo que no consta en estas fuentes se cita como «en nuestras fuentes no consta X», nunca como una ausencia en el mundo. Para saber qué trámites exige un vuelo concreto, usa `flight_requirements`. · Searches Aerset's sourced corpus of Spanish drone regulation and returns literal passages, each with its document title, URL and vintage. Retrieval only: nothing is summarised and no conclusion is drawn. Quote a passage with its source and its date; an absence from the corpus is an absence from our sources and says nothing about the world.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | – |
| available | boolean | – | – |
| checked_at | string | – | – |
| corpus_documents | integer | – | – |
| disclaimer | string | – | – |
| invalid_arguments | – | – | – |
| note | – | – | – |
| passages | array | – | – |
| query | string | – | – |
No examples provided.
spots_near Puntos de vuelo cerca ~270
Busca puntos de vuelo cerca de una coordenada, de la comunidad de pilotos de Aerset: nombre, coordenada, tipo de dron al que va bien y la dificultad que se le comprobó, con la fecha de esa comprobación. Es conocimiento de la comunidad y NO una fuente oficial: dice adónde va la gente, no qué exige la norma. Que un punto figure aquí no dice nada sobre el espacio aéreo de hoy — la dificultad es la del día en que se comprobó y no se recalcula—, así que los trámites los contesta `flight_requirements` y la última palabra la tienen AESA y el visor oficial de ENAIRE. · Finds flying spots near a coordinate from Aerset's pilot community, with the difficulty each one was checked at and the date of that check. Community knowledge, not an official source: it says where people go and nothing about what the regulation demands. A spot appearing here says nothing about today's airspace — its difficulty is the day it was checked and is never recomputed — so ask `flight_requirements` for the paperwork, and the authority and ENAIRE's official viewer have the last word.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
| radius_km | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | – |
| checked_at | string | – | – |
| disclaimer | string | – | – |
| invalid_arguments | – | – | – |
| note | – | – | – |
| note_on_verdicts | string | – | – |
| spots | array | – | – |
No examples provided.
uas_zones Zonas UAS de ENAIRE en un rectángulo ~235
Devuelve los polígonos de las zonas geográficas UAS que ENAIRE publica dentro de un rectángulo, con el tipo de cada una, sus límites vertical inferior y superior y la fecha en que ENAIRE la actualizó. Es la capa que pinta un mapa, no un veredicto sobre un punto: para eso está `flight_requirements`. Una lista vacía significa que la consulta a ENAIRE no devolvió ninguna zona para ese rectángulo, y `available: false` significa que no se pudo consultar — ni la una ni la otra describen el cielo. El visor oficial de ENAIRE tiene la última palabra. · Returns the UAS geographical zones ENAIRE publishes inside a bounding box, each with its kind, its vertical limits and ENAIRE's own update date. It is a map layer and not a verdict about a point. An empty list means our query to ENAIRE returned nothing for that rectangle; `available: false` means the query did not happen. ENAIRE's official viewer has the last word.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | – |
| available | boolean | – | – |
| checked_at | string | – | – |
| disclaimer | string | – | – |
| invalid_arguments | – | – | – |
| note | – | – | – |
| truncated | boolean | – | – |
| viewer_url | – | – | – |
| zones | array | – | – |
No examples provided.
How do I install the Aerset · normativa de drones en España MCP server?
Aerset · normativa de drones en España is a hosted endpoint at https://mcp.aerset.com/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.aerset.com
claude mcp add --transport http com-aerset-normativa-drones-espana 'https://mcp.aerset.com/mcp'
What is the Aerset · normativa de drones en España MCP server?
Aerset · normativa de drones en España is an MCP server listed in the public MCP registry as com.aerset/normativa-drones-espana. Normativa española de drones con fuente y fecha por regla: pasajes citables, zonas UAS, requisitos. This page covers its hosted endpoint (https://mcp.aerset.com/mcp).
Is the Aerset · normativa de drones en España MCP server safe to use?
Aerset · normativa de drones en España scores 83 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 Aerset · normativa de drones en España MCP server expose?
Aerset · normativa de drones en España exposes 5 tools: search_regulation, flight_requirements, uas_zones, spots_near, rules_catalogue. Their descriptions and schemas cost roughly 1,255 tokens of context every time the server is loaded.
Does the Aerset · normativa de drones en España MCP server require authentication?
No. We connected to Aerset · normativa de drones en España without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Aerset · normativa de drones en España MCP server still maintained?
Aerset · normativa de drones en España is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.