MCP servers observed by Lowdown
app.atlasly/atlasly MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 43 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; no tool definition change in 3 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.atlasly/atlasly
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.atlasly/atlasly?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 3 compared days.
What tools does it list?
43 tools on 2026-11-18:
analyze_siteassess_planning_readinessboundary_doctorcheck_permitted_developmentcheck_planning_constraintscompare_design_optionscompare_sitescreate_project_from_sitedraft_site_descriptionenable_site_watchestimate_planning_costsexport_site_boundaryexport_site_contextfind_development_sitesfind_precedentsgenerate_site_briefgenerate_site_mapget_flood_riskget_job_statusget_local_plan_policiesget_location_coverageget_lpa_adapter_statusget_map_layer_planget_nearby_mapped_placesget_official_source_adaptersget_planning_historyget_point_elevationinspect_research_sourcelist_developmentsopen_atlasly_workspaceplan_site_intelligenceprepare_biodiversity_reviewprepare_building_regulations_reviewprepare_heritage_reviewprepare_sequential_reviewprepare_site_researchpresent_site_researchrun_site_packagesearch_aec_knowledgesearch_development_mentionssearch_toolssite_verdictview_geojson_file
MCP Registry declaration
- Registry name:
app.atlasly/atlasly - Declared version: 0.3.0
- Status: active
- Declared hosts:
mcp.atlasly.app
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:app.atlasly/atlasly", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.atlasly/atlasly?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).