Atlas (urbankitstudio) MCP Server

@urbankitstudio/mcp-atlas npm v0.2.1

Published by @urbankitstudio — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Query 155 verified US county parcel ArcGIS REST endpoints for owner, APN, and address lookup via the Model Context Protocol (MCP).

View on npm ↗ Repository ↗ Raw report (JSON) ↗

Trust grade

96/100

Last scanned 2026-09-07 get badge →

Trust

A · 96/100

Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.

Capability

Moderate

Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.

Coverage

Source

How much the scan could actually inspect. Shallow coverage is stated, never hidden.

A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

Points	Adoption-risk factor
−3	capability blast radius (moderate) — client exposure if the model is manipulated
−1	publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 4

Each tool and what it can reach — statically extracted from the published source.

build_owner_queryingests untrusted input
find_countyno sensitive capability
get_parcel_endpointno sensitive capability
list_countiesno sensitive capability

What this scan could not see

Tools were statically extracted from the published source (4 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Versions 3

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

Version	Score	Engine	Scanned
`v0.2.1` latest	A 96/100	1.13.0	2026-09-07
`v0.1.6`	A 96/100	1.13.0	2026-09-01
`v0.1.5`	A 96/100	1.12.1	2026-08-05

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

Markdown (GitHub README)

[![MCP Trust Score](https://mcptrustchecker.com/registry/urbankitstudio-mcp-atlas/badge.svg)](https://mcptrustchecker.com/registry/urbankitstudio-mcp-atlas)

HTML

<a href="https://mcptrustchecker.com/registry/urbankitstudio-mcp-atlas"><img src="https://mcptrustchecker.com/registry/urbankitstudio-mcp-atlas/badge.svg" alt="MCP Trust Score" height="20"></a>

Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/urbankitstudio-mcp-atlas/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @urbankitstudio/mcp-atlas --online

Use the free API → How scoring works

Other implementations of Atlas 6

Independent packages implementing the same tool, scanned with the same engine. Compare all 7 side by side →

Atlas (cyanheads) npm

atlas-mcp-server

ATLAS (Adaptive Task & Logic Automation System): An MCP server enabling LLM agents to manage projects, tasks, and knowledge via a Neo4j-backed, three-tier architecture. Facilitates complex workflow automation and project management through LLM Agents.

AI, Memory & Reasoning Score 99/100 0 findings 75/wk Cap. Minimal

Atlas (moxellabs) npm

@moxellabs/atlas

Local-first documentation ingestion, retrieval, and MCP/server access for multi-repo engineering docs.

Learning & Documentation Score 99/100 0 findings 14/wk Cap. Minimal

Atlas (sidmanale643) npm

atlas-mcp

Brain-inspired semantic memory system and MCP server

AI, Memory & Reasoning Score 96/100 0 findings 15/wk Cap. Moderate

Atlas (latellu) npm

@latellu/atlas-mcp

MCP (Model Context Protocol) server for Atlas CMS - enables AI agents to manage content