Servidor MCP de Atlasly

• Nombre en el registroapp.atlasly/atlaslyverificado en el registro MCP

El nombre en el registro está bajo atlasly.app. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-30
• Herramientas35
• El servidor se llamaatlasly-mcp
• Versión del servidor0.3.0
• Versión del protocolo2025-06-18

El 2026-10-30 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 895 ms.

• Sus herramientas hacen todos los casos de uso comprobados: check flood zone and conservation area status for a site; review listed buildings and planning constraints near a site.
• Comprobado 5 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 5 hasta ahora
• Qué puede hacer un agente con él2 de 2 casos de uso
• Respondiómidiendo5 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta768 ms
• Espacio en el contexto del agente≈ 30.294 tokenslas definiciones de todas sus herramientas (35), que el agente lleva en cada turno
• Definiciones de herramientasA · 92 de 100
• Resultados tipados35 de 35 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin tipo: en 2 de 35
• Parámetros sin descripción: en 14 de 35

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• view_geojson_file

  Open a user-selected .geojson file read-only in Atlas AI. Host resource access required; bounded WGS84 geometry, no source fetch, legal parcel verification or file edits.

• open_atlasly_workspace

  Purpose: open Atlasly's interactive maps and site workspace. When to use: when the user wants to explore Atlasly tasks or open its workspace; call the specific evidence tool directly for a specific question. Returns: a task chooser with…

• get_location_coverage

  Check registered context/place routes and selected official research references for a supplied global WGS84 point and country before choosing a task. No geocoding, dataset retrieval or source health probe. Separates community geometry…

• inspect_research_source

  Purpose: independently retrieve a supported official publishing page and compare an optional literal quotation. When to use: check a cited source passage after conversation research. Returns: bounded plain-text excerpt, retrieval time…

• prepare_site_research

  Purpose: prepare a site-bound research request for the current conversation. When to use: when a user asks to research a global site question. Returns: a reviewable request and reusable site_ref, with no researched findings. Limitations…

• present_site_research

  Purpose: present cited site research. When to use: after conversation research, or to show unavailable search and gaps. Returns: Atlas AI UI, a JSON evidence register and a self-contained printable HTML pack. The HTML can be printed to…

• export_site_boundary

  Purpose: validate and export a supplied WGS84 boundary as GeoJSON or SVG. When to use: when the user provides a Polygon, MultiPolygon or Feature and wants a portable boundary file. Returns: actual file contents, filename, MIME type…

• export_site_context

  Purpose: retrieve source geometry and prepare a portable site-context file. When to use: when the user wants OpenStreetMap buildings, roads, water, green space and land use worldwide or available UK flood/heritage geometry around a…

• search_tools

  Discover available Atlasly tools by keyword. Call this first when unsure which tool to use. Returns tool names, one-line summaries, and required parameters. Chaining: every response returns site_ref; pass it unchanged into another Atlasly…

• get_lpa_adapter_status

  Purpose: inspect Atlasly top-LPA planning source adapter coverage, operational status, cache state, record counts, and geometry coverage. When to use: use when inspecting local-adapter registrations and reported operational state…

• site_verdict

  Purpose: produce the one-call Atlasly hero appraisal for a known UK site. When to use: use first for acquisition, feasibility, concept, or planning-stage questions that need a clear Proceed, Investigate, or Stop screen rather than…

• compare_sites

  Purpose: compare exactly two UK sites for the same intended use and stage using the existing Site Verdict evidence. When to use: use after appraising one or two candidate sites, or when an architect/developer needs a shortlist decision…

• boundary_doctor

  Purpose: check a user-supplied red-line boundary before treating it as the site geometry. When to use: run after receiving a GeoJSON Polygon or MultiPolygon, especially before Site Verdict or focused constraint checks. Returns: closure…

• analyze_site

  Purpose: prepare a limited first site read. When to use: use for an initial resolved England address before selecting further evidence tools. Returns: reported flood point evidence, a bounded national application sample with explicit…

• check_planning_constraints

  Check first-pass UK planning constraints at a site: flood zone, listed buildings, World Heritage Sites, registered parks and gardens, scheduled monuments, registered battlefields, archaeological priority areas, conservation areas, Article…

• check_permitted_development

  Purpose: prepare an England permitted-development evidence checklist, tentative class hint and restriction samples, without confirming a legal route. When to use: use for architect questions like "is this rear extension PD?", "can I…

• prepare_biodiversity_review

  Purpose: prepare an England biodiversity evidence checklist from supplied site area and habitat labels. When to use: identify missing surveys and metric inputs before a BNG review. Returns: supplied inputs, missing information and null…

• get_local_plan_policies

  Purpose: review stored England local policy extract leads for a resolved authority. When to use: early planning statement research, with source links where available. Returns: a bounded extract sample, unknown…

• estimate_planning_costs

  Purpose: estimate England planning application fees, CIL coverage/liability status, and likely S106 heads for early feasibility and viability checks. When to use: use when a user asks for planning fees, CIL, S106, planning obligations, or…

• find_development_sites

  Purpose: find and rank official English brownfield-register development-site candidates for an area, then enrich the shortlist with Atlasly flood, heritage, conservation-area, and transit checks where requested. When to use: use for…

• prepare_sequential_review

  Purpose: prepare an England sequential-test evidence checklist and bounded candidate-register sample without determining a requirement, exemption or outcome. When to use: for flood sequential/exception questions and authority-review…

• prepare_heritage_review

  Purpose: review a bounded source inventory of listed buildings and conservation areas. When to use: prepare heritage evidence and identify gaps before a proposal-specific assessment. Returns: named source records, published grades, point…

• assess_planning_readiness

  Purpose: check planning evidence readiness for a proposal at a resolved England location. When to use: prepare proposal evidence and identify decision references to verify before policy and design appraisal. Returns: bounded…

• draft_site_description

  Purpose: draft grounded site description, constraints, accessibility, planning history, and policy-context sections for a Design & Access Statement or feasibility note using Atlasly source-backed tool outputs. When to use: use when the…

• generate_site_map

  Purpose: compose multiple Atlasly source-backed site layers into one shareable map URL for feasibility reports, client decks, and planning context review. When to use: use when the user wants a single map with flood, heritage, planning…

• prepare_building_regulations_review

  Purpose: prepare an England building-control review checklist without determining applicable requirements or compliance. When to use: use during feasibility/RIBA Stage 1-2 for fire, structure, ventilation, energy, access, overheating and…

• get_flood_risk

  Purpose: retrieve reported flood point evidence with source-state and coverage limits. When to use: first-pass flood evidence before authority/site-specific review. Returns: UK reported zone/native SEPA likelihood and gaps; US native FEMA…

• get_planning_history

  Purpose: retrieve a bounded national planning-application sample for a resolved England site. When to use: for first-pass record research with direct local-portal verification. Returns: references, source decision text, known/unknown…

• find_precedents

  Purpose: retrieve explicitly decided records from a bounded national planning-application sample for a resolved England site. When to use: to locate application references for manual decision and policy verification. Returns: known…

• search_aec_knowledge

  Search the Atlasly AEC knowledge graph: official data source registry, jurisdiction planning frameworks, technical standards, calculation tools, and domain records. kind=sources returns official datasets by jurisdiction…

• plan_site_intelligence

  Resolve a site into a structured data-source route: which Atlas warehouse datasets apply, which official sources are verified for this jurisdiction, which categories have coverage gaps, and what research fallback applies for uncovered…

• get_map_layer_plan

  Return structured map actions, source-backed evidence layers, missing layers, citations, coverage status, and warnings for Atlasly site-intelligence map customization requests. Chaining: every response returns site_ref; pass it unchanged…

• get_official_source_adapters

  List Atlasly registered official-source adapters for USA/EU/global site intelligence. Use to inspect source endpoint readiness, token requirements, and health-check queue instructions before relying on unsupported-location research…

• get_point_elevation

  Purpose: read one contextual elevation worldwide from Copernicus GLO-30 surface data, or an operator-configured Open Topo Data-compatible service. When to use: when a user asks about elevation at a known worldwide point. Returns: finite…

• get_nearby_mapped_places

  Purpose: find mapped nearby schools, shops and services worldwide. When to use: compare local place context around a known site, or prepare mapped points for QGIS. Returns: selected OpenStreetMap point categories from fixed regional…