KnowMapped MCP server
com.knowmapped/mcpknowmapped.comstreamable-httpv1.0.1Scanned
Search, retrieve, create, and update visual knowledge maps in a user's KnowMapped account.
16 tools: 4 can delete or cancel things, 3 change things and 9 only read.
- Reads private data · 2
- Reads text others write · 3
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the KnowMapped MCP server can do
The KnowMapped MCP server is published by knowmapped.com, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (4 tools: update_knowmapped_map, set_knowmapped_map_visibility, set_knowmapped_live_view and publish_knowmapped_map) and create or change data (3 tools: preflight_knowmapped_map_creation, create_knowmapped_map and confirm_knowmapped_map_creation). 9 tools only read.
2 tools read private data (get_knowmapped_wheel_branch and export_knowmapped_map); 3 tools bring in text other people can write (set_knowmapped_map_visibility, set_knowmapped_live_view and publish_knowmapped_map); 1 tool can send data out of your system (publish_knowmapped_map). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Deletes or cancels 4Claude Code: deny
publish_knowmapped_mapPublish or republish completed edits to an already-public map when the user requests it.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "publish_knowmapped_map" says "publish": a word for a change that another call does not undo.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "publish_knowmapped_map" says "publish": it sends or publishes something to other people.
Description, as the server wrote it Publish or republish completed edits to an already-public map when the user requests it. Use the revision returned by the final edit or a fresh retrieval. Applies the same permissions, locks, moderation, and restrictions as browser publishing and generates the public preview. Reuse the same idempotency_key and identical arguments after a dropped response. Returns published revision and sync state; pending review or sync must not be reported as a fully delivered publication. On a revision conflict, retrieve the map and reconsider before retrying. To publish a private map first use set_knowmapped_map_visibility with explicit copyright acknowledgement.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
set_knowmapped_live_viewEnable or disable public live viewing for an owned published concept map or Futures Wheel.Reads text others writeNo findings
Why it is in this group
- The name "set_knowmapped_live_view" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Enable or disable public live viewing for an owned published concept map or Futures Wheel. Enable only at the user's explicit request: live viewers see ongoing saved edits, not just the published snapshot. Requires the existing account entitlement and maps:publish permission. Does not publish a private map or invite collaborators. Reuse an identical idempotency key after a dropped response.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
set_knowmapped_map_visibilityMake a map public or private at its current revision.Reads text others writeNo findings
Why it is in this group
- The name "set_knowmapped_map_visibility" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Make a map public or private at its current revision. Obtain the user's explicit permission to publish and confirmation that they have the right to publish before setting copyright_acknowledged=true; never infer it from map content. Initial publication creates a moderated public snapshot and generated preview. Making private removes the snapshot and disables live viewing. Setting an already-public map public does not publish edits: use publish_knowmapped_map. Reuse the same idempotency_key and identical arguments after a dropped response; a different request needs a new key. A pending_review result means publication has not succeeded. On a revision conflict, retrieve the map and reconsider before retrying.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
update_knowmapped_mapValidate or atomically update an editable concept map or Futures Wheel.No findings
Why it is in this group
- The name "update_knowmapped_map" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Validate or atomically update an editable concept map or Futures Wheel. For wheels use add_consequence, update_consequence, move_branch, remove_branch (confirmed cascade), set_branch_collapsed, upsert_domain, remove_domain, assign_domain and layout_wheel. Orders, causal edges and radial geometry are derived; concept operations are rejected. For concept maps: Accepted operations are update_map, add_node, update_node, remove_node, add_edge, update_edge, remove_edge, replace_edges, and layout_nodes; get_knowmapped_update_schema is the authoritative versioned contract. Use id for identifiers, title for the map title, and layout_nodes with strategy, spacing, groups, and optional flow. Node references accept IDs, earlier temp_id values, or exact unique labels. Edge references accept IDs or semantic source/target/current-relationship matches. validate_only returns a corrected executable normalized_patch, all detectable errors and warnings, layout positions and bounds, a patch summary, publication state, and current revision without changing data. On a stale write, revalidate the same patch at current_revision, then submit the returned normalized_patch.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Changes things 3Claude Code: ask
confirm_knowmapped_map_creationTransactionally confirm a preflighted creation by draft ID.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Transactionally confirm a preflighted creation by draft ID. Success definitively returns map_id and revision. A failed transaction preserves the draft for retry, and retrying a committed success returns the same result without charging again. Use get_knowmapped_map_creation_result after a timeout or malformed response.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
create_knowmapped_mapValidate or create a concept map or Futures Wheel.No findings
Why it is in this group
- The name "create_knowmapped_map" says "create": a word for a change.
Description, as the server wrote it Validate or create a concept map or Futures Wheel. Set graph.graph_type explicitly. Wheels require causal parent/order metadata and use the same radial geometry as the editor; only radial layout is allowed. Manual wheel creation is included in Free; MCP creation uses the normal MCP entitlement and credit policy. Concept maps: Specify requested layout only as top-level graph.layout_intent. When omitted, requested_layout and resolved_strategy are smart, but [0,0] placeholders are retained for the map client to lay out on first draw; layout_application is client-first-draw. Complete explicit coordinates are preserved instead. Set validate_only=true to check the exact final graph schema, layout, capacity, links, and credits without creating a map, charging credits, or reserving the idempotency key. For credit-bearing creation, show the quoted charge, then confirm the retained draft only after explicit approval.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
preflight_knowmapped_map_creationCheck eligibility and credits for concept maps or Futures Wheels (graph_type), or retain a fully validated graph as a short-lived draft.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Check eligibility and credits for concept maps or Futures Wheels (graph_type), or retain a fully validated graph as a short-lived draft. The exact creation layout field is top-level graph.layout_intent, for example left-to-right. For concept maps, omission records Smart intent and complete explicit coordinates are preserved. Futures Wheels default to radial, derive positions with the wheel renderer, and reject other intents. Fields named layout, layout_type, or strategy are rejected. Drafts do not reserve credits and can be confirmed by draft ID without resending the graph.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 9Show 9 read-only tools
export_knowmapped_mapReturn an import-ready .know JSON file for an authorized concept map or Futures Wheel.Reads private dataNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "file": it reads files.
Description, as the server wrote it Return an import-ready .know JSON file for an authorized concept map or Futures Wheel. Serialize file as UTF-8 JSON under filename. Includes every node, including collapsed branches, presentation and provenance; does not publish or create a map. Visual exports remain in the app.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_knowmapped_layout_summaryReturn layout bounds and graph statistics without returning graph content.No findings
Why it is in this group
- The name "get_knowmapped_layout_summary" says "get": a word for reading.
Description, as the server wrote it Return layout bounds and graph statistics without returning graph content.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_knowmapped_mapRetrieve an authorized map with independent node_offset, edge_offset, and page_size parameters.No findings
Why it is in this group
- The name "get_knowmapped_map" says "get": a word for reading.
Description, as the server wrote it Retrieve an authorized map with independent node_offset, edge_offset, and page_size parameters. Canonical IDs are always retained in projected nodes and edges even when include_nodes or include_edges omits id. Use summary for statistics without graph content or compact for token-efficient fields. Search results return copy-safe map references so UUIDs should not be typed manually.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_knowmapped_map_adjacencyReturn one concept and its directly connected concepts and relationships without retrieving the full graph.No findings
Why it is in this group
- The name "get_knowmapped_map_adjacency" says "get": a word for reading.
Description, as the server wrote it Return one concept and its directly connected concepts and relationships without retrieving the full graph. Provide node_id or an exact unique label.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_knowmapped_map_creation_resultRecover the definitive state of a map creation without creating a map or charging credits.No findings
Why it is in this group
- The name "get_knowmapped_map_creation_result" says "get": a word for reading.
Description, as the server wrote it Recover the definitive state of a map creation without creating a map or charging credits. Provide exactly one draft_id or the original idempotency_key. A succeeded result includes the canonical map ID and revision.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_knowmapped_publication_statusCheck public snapshot revision, moderation and delivery without loading graph content.No findings
Why it is in this group
- The name "get_knowmapped_publication_status" says "get": a word for reading.
Description, as the server wrote it Check public snapshot revision, moderation and delivery without loading graph content. Requires maps:publish and editable-map access. Revision differences mean content may have changed, since operational changes also advance revisions. After a timeout retry the original publication with the same idempotency_key; use this tool to check current delivery separately.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_knowmapped_update_schemaReturn the authoritative, versioned schema, graph_type_operations and examples for atomic KnowMapped concept-map and Futures Wheel patches.No findings
Why it is in this group
- The name "get_knowmapped_update_schema" says "get": a word for reading.
Description, as the server wrote it Return the authoritative, versioned schema, graph_type_operations and examples for atomic KnowMapped concept-map and Futures Wheel patches. Call this before constructing an update instead of guessing operation or field names.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_knowmapped_wheel_branchRead a wheel consequence, its ancestors, inherited domain and paginated descendants, including collapsed content.Reads private dataNo findings
Why it is in this group
- The name "get_knowmapped_wheel_branch" says "get": a word for reading.
What it can reach
- private-dataThe name "get_knowmapped_wheel_branch" says "get" and "branch": it reads repositories.
Description, as the server wrote it Read a wheel consequence, its ancestors, inherited domain and paginated descendants, including collapsed content. Omit the node reference to start at the central change. Compact keeps causal metadata; full adds descriptions, resources and provenance.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_knowmapped_mapsSearch maps available to the connected KnowMapped account.No findings
Why it is in this group
- The name "search_knowmapped_maps" says "search": a word for reading.
Description, as the server wrote it Search maps available to the connected KnowMapped account. Use this when a user refers to a saved map or wants to find prior concepts; existing ownership and sharing permissions are enforced server-side.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__knowmapped__publish_knowmapped_map"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.knowmapped.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://app.knowmapped.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (4 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.knowmapped.com/mcp: tools/list returned 16 tools to an anonymous client, including update_knowmapped_map (destructive), set_knowmapped_map_visibility (destructive), set_knowmapped_live_view (destructive), publish_knowmapped_map (destructive), preflight_knowmapped_map_creation (write) and 2 more
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 6 to 7
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 added, 4 changed.+3 added~4 changedView diff
- Added:export_knowmapped_mapOnly reads
- Added:get_knowmapped_wheel_branchOnly reads
- Added:set_knowmapped_live_viewDeletes or cancels
- Changed:create_knowmapped_mapChanges thingsdescriptioninputSchema
- Changed:get_knowmapped_update_schemaOnly readsdescription
- Changed:preflight_knowmapped_map_creationChanges thingsdescriptioninputSchema
- Changed:update_knowmapped_mapDeletes or cancelsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 7.View diff
- Tools that change things, listed without credentials: 6 to 7
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http knowmapped https://mcp.knowmapped.com/mcpclaude mcp add --transport http knowmapped https://mcp.knowmapped.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__knowmapped__get_knowmapped_update_schema",
"mcp__knowmapped__search_knowmapped_maps",
"mcp__knowmapped__get_knowmapped_map",
"mcp__knowmapped__get_knowmapped_map_adjacency",
"mcp__knowmapped__get_knowmapped_wheel_branch",
"mcp__knowmapped__export_knowmapped_map",
"mcp__knowmapped__get_knowmapped_layout_summary",
"mcp__knowmapped__get_knowmapped_map_creation_result",
"mcp__knowmapped__get_knowmapped_publication_status"
],
"ask": [
"mcp__knowmapped__preflight_knowmapped_map_creation",
"mcp__knowmapped__create_knowmapped_map",
"mcp__knowmapped__confirm_knowmapped_map_creation"
],
"deny": [
"mcp__knowmapped__update_knowmapped_map",
"mcp__knowmapped__set_knowmapped_map_visibility",
"mcp__knowmapped__set_knowmapped_live_view",
"mcp__knowmapped__publish_knowmapped_map"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as knowmapped. Review it before you use it.
Capability tags behind 5 rules
- mcp__knowmapped__get_knowmapped_wheel_branch private-data
- mcp__knowmapped__export_knowmapped_map private-data
- mcp__knowmapped__set_knowmapped_map_visibility untrusted-input
- mcp__knowmapped__set_knowmapped_live_view untrusted-input
- mcp__knowmapped__publish_knowmapped_map untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.knowmapped/mcp/verify?hash=2251698da4fd6e9539e0451f04515b4a97e6c6810497d815e5620db65bd56e69" | jq -e '.changed == false'Pinned hash 2251698da4fd, from Nov 13, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.knowmapped/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.knowmapped/mcp)Source: MCP Registry. Synced Oct 21, 2026, 17:57 UTC.
KnowMapped MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the KnowMapped MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the KnowMapped MCP server delete data?
- Yes. 4 tools can delete, cancel or revoke something: update_knowmapped_map, set_knowmapped_map_visibility, set_knowmapped_live_view and publish_knowmapped_map.
Can the KnowMapped MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the KnowMapped MCP server have?
- 16 tools: 4 destructive, 3 write, 9 read. update_knowmapped_map, set_knowmapped_map_visibility, set_knowmapped_live_view, publish_knowmapped_map, preflight_knowmapped_map_creation, create_knowmapped_map, confirm_knowmapped_map_creation, get_knowmapped_update_schema and 8 more.
Does the KnowMapped MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the KnowMapped MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_knowmapped_map.
Has the KnowMapped MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 31, 2026. Every change is on this page and in its Atom feed.