Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Augmap

REMOTE · MCP.AUGMAP.AI

Make maps of places across the continental US with your AI assistant.

Available components

+3 this week 65 Trust /100

Last scanned (18 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability29
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 3765 tokens (~268/item across 14 items; 10 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 55% of tool parameters carry a description.Partial
  • Structured output schemas are declared (20% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Nov 26 0
    • Server version: 1.0.0+15576fab → 1.0.0+46b416d8 functional
  • 19 Nov 26 +1
    • Server version: 1.0.0+65224c10 → 1.0.0+15576fab functional
  • 18 Nov 26 0
    • Server version: 1.0.0+9e2aa710 → 1.0.0+65224c10 functional
  • 17 Nov 26 0
    • Server version: 1.0.0+f38010c3 → 1.0.0+9e2aa710 functional
  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 0
    • Server version: 1.0.0+7aef7f06 → 1.0.0+f38010c3 functional
  • 14 Nov 26 +1
    • Server version: 1.0.0+a38fa608 → 1.0.0+7aef7f06 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.augmap.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=augmap.ai CN=WE1,O=Google Trust Services,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 6baa87d2f9d00b713b3f563813d165c
SANs: augmap.ai, mcp.augmap.ai, *.mcp.augmap.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.augmap.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
augmap.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=2592000
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.augmap.ai/mcp Verified 200
http (plaintext) http://mcp.augmap.ai/mcp HTTPS enforced 301 https://mcp.augmap.ai/mcp
MCP tools · 10 exposed · ~1,376 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
map_create ~305

Create a map of places in the continental US. Returns map_id and map_url.

NameTypeReqDescription
app_namestring–Name shown for this app in the map sharing panel.
contextstring–Traveler preferences and planning notes, e.g. seafood and playgrounds. Stored context is limited to 10,240 UTF-8 bytes.
conversation_idstring–Your stable id for this conversation (≤64 chars, no ':', not 'user' or 'system'). With it, pending_changes lists only changes made by others.
day_nounstring–The word the map numbers its days with, when they are not days: "House" for houses to tour gives House 1, House 2. Default "Day"; "" resets it.
destinationstring–City or region in the continental US, e.g. Asheville, NC.
interestsarray––
request_idstring–Your id for this create: 1–64 letters, digits, hyphens or underscores. Signed in, a retry with the same id returns the same map; otherwise the retry is not charged twice.
route_stopsboolean–Whether plan lists draw routes and travel times between their places. Default true; false is for lists that are not journeys, such as one list per area.
titlestring–Map title.
travel_modestring––
viewobject––
NameTypeReqDescription
browser_urlstring––
draft_expires_atstring––
draft_handlestring––
map_idstringyes–
map_urlstringyes–
save_statestringyes–

No examples provided.

map_edit_lists ~162

Create, update (rename, change kind, pin a saved list to a plan list) or delete lists. A plan list's date goes in its name ("Sat, Oct 3 · Acadia"). Deleting a list moves its places to Unscheduled or to. Each op result has the list_id and kind of the list it used.

NameTypeReqDescription
conversation_idstring––
draft_handlestring–The draft_handle map_create returned; unsaved maps only.
expected_versionstring–The version you planned this edit from. If someone else has since changed what it touches, nothing is applied and the result is a conflict with their changes and the current version.
map_idstringyes–
opsarrayyes–

No output schema declared.

No examples provided.

map_edit_places ~124

Add, update, move, remove (park in rejected) or restore places. Each op result has the list_id and kind of the list it used.

NameTypeReqDescription
conversation_idstring––
draft_handlestring–The draft_handle map_create returned; unsaved maps only.
expected_versionstring–The version you planned this edit from. If someone else has since changed what it touches, nothing is applied and the result is a conflict with their changes and the current version.
map_idstringyes–
opsarrayyes–

No output schema declared.

No examples provided.

map_get_state ~126

Read a map: lists, places, save_state, version, pending_changes.

NameTypeReqDescription
conversation_idstring––
draft_handlestring–The draft_handle map_create returned; unsaved maps only.
map_idstring–The map identifier from map_create or map_list.
share_urlstring–A shared map's link (…/t/…), instead of map_id. Read-only.
sincestring–A version from an earlier response: pending_changes then lists others' changes after it. Default: since your own last change.
NameTypeReqDescription
accessstring––
browser_urlstring––
changes_truncatedboolean––
day_nounstringyes–
listsarrayyes–
map_idstring––
map_urlstringyes–
pending_changesarrayyes–
route_stopsbooleanyes–
save_statestringyes–
titlestring|nullyes–
travel_modestringyes–
versionstring––

No examples provided.

map_list ~36

List the traveler's saved maps, and maps shared with them, with their map_id and map_url.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

map_save ~44

Save a map to the traveler's account.

NameTypeReqDescription
draft_handlestring–The draft_handle map_create returned; unsaved maps only.
map_idstringyes–

No output schema declared.

No examples provided.

map_search_places ~75

Find places and street addresses in the continental US for an existing map_id. Returns places and fields_granted per query.

NameTypeReqDescription
conversation_idstring––
draft_handlestring–The draft_handle map_create returned; unsaved maps only.
map_idstringyes–
queriesarrayyes–

No output schema declared.

No examples provided.

map_set_view ~94

Pan/zoom the live map.

NameTypeReqDescription
center––Map center; provide exactly one of center or place.
conversation_idstring––
draft_handlestring–The draft_handle map_create returned; unsaved maps only.
map_idstringyes–
placestring–Existing entry_id or place name to center on; mutually exclusive with center.
zoomnumber––

No output schema declared.

No examples provided.

map_share ~160

Create, list or revoke links that let other people view a saved map or join it as editors, change a link's role, or list and manage the people who joined.

NameTypeReqDescription
labelstring–Who the link is for. create with the same label and role returns the same link.
link_idstring–Required for revoke/set_role: link_id returned by map_share list.
map_idstringyes–
member_idstring–Required for remove_member/set_member_role: member_id from list_members.
opstringyes–
rolestring–Required for set_role and set_member_role; optional for create (default viewer). viewer can look; editor invites people to edit once they sign in.

No output schema declared.

No examples provided.

map_update ~250

Change a map's title, context, travel mode, interests, day noun or whether it routes between stops.

NameTypeReqDescription
contextobject–Resulting stored context has a 10,240 UTF-8 byte limit. Retrying append repeats the text; replace is safe to retry.
conversation_idstring––
day_nounstring–The word the map numbers its days with, when they are not days: "House" for houses to tour gives House 1, House 2. Default "Day"; "" resets it.
draft_handlestring–The draft_handle map_create returned; unsaved maps only.
expected_versionstring–The version you planned this edit from. If someone else has since changed what it touches, nothing is applied and the result is a conflict with their changes and the current version.
interestsarray––
map_idstringyes–
route_stopsboolean–Whether plan lists draw routes and travel times between their places. Default true; false is for lists that are not journeys, such as one list per area.
titlestring––
travel_modestring––

No output schema declared.

No examples provided.

Install

How do I install the Augmap MCP server?

Augmap is a hosted endpoint at https://mcp.augmap.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.augmap.ai

# add to Claude Code
claude mcp add --transport http ai-augmap-maps 'https://mcp.augmap.ai/mcp'
Common questions

What is the Augmap MCP server?

Augmap is an MCP server listed in the public MCP registry as ai.augmap/maps. Make maps of places across the continental US with your AI assistant. This page covers its hosted endpoint (https://mcp.augmap.ai/mcp).

Is the Augmap MCP server safe to use?

Augmap scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Augmap MCP server expose?

Augmap exposes 10 tools: map_create, map_get_state, map_update, map_set_view, map_edit_places, and 5 more. Their descriptions and schemas cost roughly 1,376 tokens of context every time the server is loaded.

Does the Augmap MCP server require authentication?

No. We connected to Augmap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Augmap MCP server still maintained?

Augmap is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Augmap MCP server?

VerifyMCP ran 13 checks on Augmap, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.