MCP servers › app.atlasly › atlasly

MCP server · registry snapshot 2026-10-30 · last tested 2026-10-30

atlasly MCP server

Registry name app.atlasly/atlasly

by atlasly.app · domain (the registry's namespace rule)Website ↗

UK site research and worldwide CAD/GIS site context (DXF, GeoJSON, SVG) for architects — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-30version 0.3.0streamable HTTP35 tools

Summary

app.atlasly/atlasly is a remote MCP server listed in the official MCP registry at version 0.3.0, under the namespace of the domain atlasly.app. On 2026-10-30 ProtocolProbe connected to it in read-only mode and read its inventory: 35 tools, 3 resources and 2 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Tools: 35
Last tested: 2026-10-30

Tool list size

47,210 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (35 tools). Counted with Anthropic's token counter on 2026-10-30, from the tool list we read on 2026-10-30. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-30 (mcp.atlasly.app), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.3.0).

Add to your client

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-30
Mode: read-only (no tool calls)
Latest version: 0.3.0, published 2026-10-29 (registry, as of the 2026-10-30 snapshot)
First listed version: 2026-10-29 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-30
Package and repository: checked 2026-10-30
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-29, listed on 2026-10-30 with version 0.3.0 (published 2026-10-29).

Source: the official MCP Registry list on 2026-10-29 and on 2026-10-30.

What it is

What does this server offer?

Observed inventory

35tools

3resources

2prompts

None of its 35 tools are described as changing anything. For 35 the reading was uncertain, so no mark is shown.

view_geojson_file
“Open a user-selected .geojson file read-only in Atlas AI.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- fileobjectrequired
open_atlasly_workspace
“Purpose: open Atlasly's interactive maps and site workspace.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- prepared_result_urlstring
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 2 required
- country_codestringrequired
- coordinatesobjectrequired
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
inspect_research_source
“Purpose: independently retrieve a supported official publishing page and compare an optional literal quotation.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
8 inputs, 1 required
- addressstring
- coordinatesobject
- country_codestring
- radius_metersinteger
- urlstringrequired
- pageinteger“PDF page number, counting from 1.”
- quotestring
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
prepare_site_research
“Purpose: prepare a site-bound research request for the current conversation.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs, 1 required
- addressstring
- coordinatesobject
- country_codestring
- radius_metersinteger
- questionstringrequired
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
present_site_research
“Purpose: present cited site research.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
9 inputs, 4 required
- addressstring
- coordinatesobject
- country_codestring
- radius_metersinteger
- questionstringrequired
- sourcesarrayrequired
- findingsarrayrequired
- gapsarrayrequired
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
export_site_boundary
“Purpose: validate and export a supplied WGS84 boundary as GeoJSON or SVG.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 2 required
- boundary_geojsonrequired
- formatstringrequired
- titlestring
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
export_site_context
“Purpose: retrieve source geometry and prepare a portable site-context file.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
11 inputs, 2 required
- addressstring
- coordinatesobject“User-supplied WGS84 point.”
- country_codestring“ISO two-letter country code.”
- layersarrayrequired
- formatstringrequired
- boundary_modestring“Defaults to retaining whole touching features.”
- boundaryobject“User-supplied simple WGS84 outline inside the search radius.”
- diagram_stylestring“SVG display preset only; exported CAD/GIS geometry is unchanged.”
- radius_metersinteger
- titlestring
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
search_toolson 113 other servers
“Discover available Atlasly tools by keyword.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- querystringrequired“Keyword to search: e.g.”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
get_lpa_adapter_status
“Purpose: inspect Atlasly top-LPA planning source adapter coverage, operational status, cache state, record counts, and geometry coverage.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
site_verdicton 1 other server
“Purpose: produce the one-call Atlasly hero appraisal for a known UK site.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
8 inputs, 2 required
- addressstring“UK site address or postcode”
- intended_usestringrequired“Intended use, for example residential, office, school, or mixed use”
- project_stagestringrequired“Project stage, for example acquisition, feasibility, concept, or planning”
- radius_metersinteger“Point-screen radius in metres; defaults to 800”
- persist_share_cardboolean“Default true creates a temporary token-accessible share-card record; false skips that record.”
- proposalstring“Optional proposal detail such as scale, height, units, or works”
- no_go_triggersarray“Explicit user rules that may justify Stop when matched by retrieved evidence”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
compare_siteson 9 other servers
“Purpose: compare exactly two UK sites for the same intended use and stage using the existing Site Verdict evidence.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
8 inputs, 4 required
- site_aobjectrequired
- site_bobjectrequired
- intended_usestringrequired“Shared intended use, for example residential, office, or mixed use”
- project_stagestringrequired“Shared decision stage, for example acquisition or feasibility”
- proposalstring“Optional shared proposal detail applied equally to both sites”
- no_go_triggersarray“Optional explicit no-go rules applied equally to both sites”
- radius_metersinteger“Point-screen radius in metres; defaults to 800”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”

Show 23 more tools

boundary_doctor
“Purpose: check a user-supplied red-line boundary before treating it as the site geometry.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 2 required
- boundary_geojsonrequired“GeoJSON Polygon, MultiPolygon, or Feature containing one.”
- source_crsstringrequired“Explicit source CRS: WGS84/CRS84 longitude-latitude, British National Grid, or Irish Transverse Mercator”
- declared_area_m2number“Optional area stated by the source, in square metres, for comparison with the coordinate-derived area”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
analyze_siteon 8 other servers
“Purpose: prepare a limited first site read.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs
- addressstring“Site address or postcode”
- radius_metersinteger“Analysis radius in metres, default 500.”
- focusstring“Optional framing for the summary”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
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 prio…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs
- addressstring“Site address or postcode”
- radius_metersinteger
- includearray
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
check_permitted_development
“Purpose: prepare an England permitted-development evidence checklist, tentative class hint and restriction samples, without confirming a legal route.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 1 required
- addressstring“Site address or postcode for constraint-aware PD screening”
- proposalstringrequired“Proposal text, e.g.”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
prepare_biodiversity_review
“Purpose: prepare an England biodiversity evidence checklist from supplied site area and habitat labels.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs, 1 required
- addressstring“Site address or postcode for ecology constraint screening”
- site_area_hanumber“Optional supplied site area in hectares; not independently measured”
- current_habitat_typestringrequired“Current habitat type, e.g.”
- proposed_habitat_typestring“Supplied post-development habitat label; no default is assumed”
- development_typestring“Optional development description for reporting context”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
get_local_plan_policies
“Purpose: review stored England local policy extract leads for a resolved authority.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 1 required
- addressstring“Site address or postcode used to resolve the local planning authority”
- development_typestringrequired“Development type, e.g.”
- topicstring“Optional policy topic to focus retrieval, e.g.”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
estimate_planning_costs
“Purpose: estimate England planning application fees, CIL coverage/liability status, and likely S106 heads for early feasibility and viability checks.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs, 1 required
- addressstring“Site address or postcode for LPA/CIL context”
- development_typestringrequired“Development type, e.g.”
- gross_floor_area_sqmnumber“Gross floor area in square metres for non-residential or change-of-use fee estimates”
- residential_unitsinteger“Number of proposed residential units for residential fee/CIL/S106 screening”
- application_typestring“Known application category; inferred from development_type if omitted”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
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 wher…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
10 inputs, 1 required
- search_areastring“English address, postcode, town, or LPA name used to resolve the local planning authority boundary”
- radius_metersinteger“Context radius for resolving the area; official candidate retrieval is LPA-boundary scoped”
- development_typestringrequired“Development brief, e.g.”
- min_site_area_hanumber“Preferred minimum published brownfield area in hectares, used in ranking rather than guaranteed exclusion”
- max_flood_zonestring“Preferred maximum flood zone used in heuristic ranking; unknown/exceeding points are flagged, not guaranteed excluded”
- require_transit_within_metersinteger“Preferred mapped stop-point distance in metres, used in ranking; access and service operation unverified”
- exclude_conservation_areaboolean“Whether to penalise candidate points flagged in conservation areas; not a guaranteed exclusion”
- exclude_listed_buildings_within_metersinteger“Distance threshold for listed-building proximity screening”
- brownfield_onlyboolean“Defaults to true because this version uses the official brownfield-land register as its candidate source”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
prepare_sequential_review
“Purpose: prepare an England sequential-test evidence checklist and bounded candidate-register sample without determining a requirement, exemption or outcome.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs, 1 required
- addressstring“Subject site address or postcode”
- development_typestringrequired“Development brief and vulnerability class context, e.g.”
- search_radius_metersinteger“Alternative-site search radius in metres; defaults to 2000 unless lpa_boundary_only is true”
- lpa_boundary_onlyboolean“If true, search the resolved LPA brownfield register without excluding candidates outside the radius”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
prepare_heritage_review
“Purpose: review a bounded source inventory of listed buildings and conservation areas.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs
- addressstring“Site address or postcode for the heritage radius search”
- proposed_height_mnumber“Optional supplied height in metres; heritage impact remains unassessed”
- radius_metersinteger“Search radius in metres; defaults to 500”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
assess_planning_readiness
“Purpose: check planning evidence readiness for a proposal at a resolved England location.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs, 1 required
- addressstring“Site address or postcode for the planning-history search”
- development_typestringrequired“Development brief, e.g.”
- proposed_unitsinteger“Proposed residential unit count, used only with supplied site area for residential density”
- proposed_height_mnumber“Proposed height in metres, recorded in the evidence payload”
- site_area_hanumber“Site area in hectares, used with proposed_units to calculate dwellings per hectare”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
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 too…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 1 required
- addressstring“Site address or postcode for the grounded draft”
- development_typestringrequired“Development category, e.g.”
- proposed_descriptionstring“Optional proposal description, e.g.”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs
- addressstring“Site address or postcode for the composed map”
- layersarray“Requested layers; defaults to flood, heritage, planning_history, transport, constraints, and precedents”
- radius_metersinteger“Search radius for layer source tools”
- titlestring“Optional map title shown in the encoded map configuration”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
prepare_building_regulations_review
“Purpose: prepare an England building-control review checklist without determining applicable requirements or compliance.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
10 inputs, 1 required
- addressstring“Site address or postcode for context and Atlasly logging”
- development_typestringrequired“Proposal description, e.g.”
- proposed_height_mnumber“Supplied measured height in metres; specify height_basis.”
- proposed_storeysinteger“Explicit supplied count; relevant storey definitions remain unverified”
- height_basisstring“Declared measurement basis; ground-level/top-floor convention still needs verification”
- works_typestring“Explicit works scope; missing scope is not assumed new build”
- proposed_unitsinteger“Number of proposed residential units where relevant”
- proposed_gfa_sqmnumber“Proposed gross floor area in square metres”
- use_classstring“Planning/building use class where known, e.g.”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
get_flood_riskon 2 other servers
“Purpose: retrieve reported flood point evidence with source-state and coverage limits.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
- addressstring“Site address or postcode”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
get_planning_historyon 1 other server
“Purpose: retrieve a bounded national planning-application sample for a resolved England site.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs
- addressstring“Site address or postcode”
- radius_metersinteger
- limitinteger
- outcome_filterstring
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
find_precedents
“Purpose: retrieve explicitly decided records from a bounded national planning-application sample for a resolved England site.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs
- addressstring“Site address or postcode”
- proposal_textstring“Optional proposal description used to bias the precedent search”
- radius_metersinteger
- limitinteger
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
search_aec_knowledge
“Search the Atlasly AEC knowledge graph: official data source registry, jurisdiction planning frameworks, technical standards, calculation tools, and domain records.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
15 inputs
- querystring“Search text, such as NPPF, daylight, fire, India, ADA, or U-value”
- kindstring
- jurisdictionstring“Optional country or jurisdiction filter”
- countrystring“Optional country/code filter, e.g.”
- categorystring“Optional category/domain filter, e.g.”
- authority_levelstring
- verified_onlyboolean“When true, return only official verified registry/dataset results”
- include_candidatesboolean“Include unverified source candidates as labelled background context”
- include_calculatorsboolean
- include_standardsboolean
- include_domainsboolean
- top_kinteger
- debugboolean“Include ranking/debug metadata in structured output”
- limitinteger
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
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 rese…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs
- addressstring“Site address or postcode”
- questionstring“The site-analysis question to route”
- categoriesarray“Optional requested domains such as planning, flood, heritage, ecology, transport, terrain, climate”
- radius_metersinteger
- include_candidatesboolean“Include unverified candidates as labelled background context in route diagnostics”
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
8 inputs
- addressstring“Site address or postcode”
- questionstring“Map request, e.g.”
- categoriesarray“Optional requested domains such as planning, flood, heritage, ecology, transport, terrain, climate”
- radius_metersinteger
- include_candidatesboolean“Include unverified candidates in diagnostics; they are never rendered as compliance evidence”
- show_onlyboolean“Isolate requested evidence layers and hide other custom layers”
- outputstring
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
get_official_source_adapters
“List Atlasly registered official-source adapters for USA/EU/global site intelligence.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs
- countrystring“Country or region code, e.g.”
- categorystring“Category such as flood, terrain, heritage, environment, transport, source-discovery, jurisdiction”
- dataset_keystring“Single Atlas dataset key”
- dataset_keysarray“Atlas dataset keys to inspect”
- adapter_keystring“Specific adapter key”
- source_keystring“Source registry key”
- limitinteger
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
get_point_elevation
“Purpose: read one contextual elevation worldwide from Copernicus GLO-30 surface data, or an operator-configured Open Topo Data-compatible service.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs
- addressstring
- country_codestring
- coordinatesobject
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”
get_nearby_mapped_places
“Purpose: find mapped nearby schools, shops and services worldwide.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
7 inputs
- addressstring
- coordinatesobject
- country_codestring
- personastring
- categoriesarray“Optional explicit mapped categories, for example school or hospital.”
- radius_metersinteger
- site_refobject“Canonical site_ref returned by any previous Atlasly tool.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-30.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 70% of 198
Tools with a description: 100% of 35
Typical description length: 995 characters

The tool set

Counted from the listing

Tools: 35
Size of the list: about 69,274 tokens for an agent to load (characters ÷ 4)
Naming: 35 of 35 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 35 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-30 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://mcp.atlasly.app/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

{
  "servers": {
    "atlasly": {
      "type": "http",
      "url": "https://mcp.atlasly.app/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

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

Claude Code

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

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "atlasly": {
      "type": "streamableHttp",
      "url": "https://mcp.atlasly.app/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

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

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.atlasly]
url = "https://mcp.atlasly.app/mcp"

Zed · Zed settings file (command: zed: open settings file)

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.atlasly.app/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint mcp.atlasly.app/mcp	Session opened	matches	our test · 2026-10-30
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-30

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-30. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about app.atlasly/atlasly

Answered from the data above

Who publishes app.atlasly/atlasly?

The registry ties the namespace app.atlasly to the domain atlasly.app; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does app.atlasly/atlasly need an API key or sign-in?

It opened a session without any credential on 2026-10-30. The registry entry declares no required credential; no declaration is not a guarantee.

Has app.atlasly/atlasly been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-30

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-30, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
1,953 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 35 tools, 3 resources, 2 prompts.
12,819 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in a later update

listed 2026-10-30; not classified yet

Pricing modelAI-classified

pending: added in a later update

the website is not read yet

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-30

MCP capability

prompts, resources, tools

our test · 2026-10-30

Transport

streamable HTTP

registry · 2026-10-30

Required credentials

none declared

registry · 2026-10-30 · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-30

Lifecycle status

active

registry · 2026-10-30

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type · 2026-10-30

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “app.atlasly/atlasly: MCP server record.” Data checked 2026-10-30. https://protocolprobe.com/mcp/servers/app.atlasly/atlasly

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/app.atlasly/atlasly)](https://protocolprobe.com/mcp/servers/app.atlasly/atlasly)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology