Home / MCP registry index / app.atlasly/atlasly

Atlasly

app.atlasly/atlasly in the official MCP registry. Endpoint https://mcp.atlasly.app/mcp.

The registry describes it as: UK site research and worldwide CAD/GIS site context (DXF, GeoJSON, SVG) for architects

We read its 35 tools on 2026-11-01. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http atlasly https://mcp.atlasly.app/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "atlasly": {
      "url": "https://mcp.atlasly.app/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"atlasly","type":"http","url":"https://mcp.atlasly.app/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

view_geojson_file open_atlasly_workspace get_location_coverage inspect_research_source prepare_site_research present_site_research export_site_boundary export_site_context search_tools get_lpa_adapter_status site_verdict compare_sites boundary_doctor analyze_site check_planning_constraints check_permitted_development prepare_biodiversity_review get_local_plan_policies estimate_planning_costs find_development_sites prepare_sequential_review prepare_heritage_review assess_planning_readiness draft_site_description generate_site_map prepare_building_regulations_review get_flood_risk get_planning_history find_precedents search_aec_knowledge plan_site_intelligence get_map_layer_plan get_official_source_adapters get_point_elevation get_nearby_mapped_places

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): 30c085ef4b7c2051. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/app-atlasly-atlasly/badge.svg)](https://lazaretto.dev/mcp-registry/app-atlasly-atlasly)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.