KnowMapped MCP server

• Registry namecom.knowmapped/mcpverified in the MCP registry

The registry name sits under knowmapped.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-21
• Tools13
• Server calls itselfKnowMapped
• Server version1.29.0
• Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 222 ms.

• Its tools do Map concepts and label how they connect, but not Turn uploaded documents into editable starting concept maps.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score63 of 100answers 100 · does the job 50 · definitions 84 · context 68 · connects 100 · lowered by the warning signs below
• What an agent can do with it1 of 2 use cases
• Answered100% of days7 of 7 daily checks
• Median first answer236 ms
• Space in an agent's context≈ 9,735 tokensthe definitions of all its tools (16), which an agent carries on every turn
• Tool definitionsB · 84 of 100
• Typed results16 of 16 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 15 of 16

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_knowmapped_update_schema

  Return the authoritative, versioned schema and examples for atomic KnowMapped map patches. Call this before constructing an update instead of guessing operation or field names.

• search_knowmapped_maps

  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.

• get_knowmapped_map

  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…

• get_knowmapped_map_adjacency

  Return one concept and its directly connected concepts and relationships without retrieving the full graph. Provide node_id or an exact unique label.

• get_knowmapped_layout_summary

  Return layout bounds and graph statistics without returning graph content.

• preflight_knowmapped_map_creation

  Check eligibility and credits, 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. If omitted, Smart is the intent but [0,0] placeholders…

• create_knowmapped_map

  Validate or create a KnowMapped graph. 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…

• confirm_knowmapped_map_creation

  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…

• get_knowmapped_map_creation_result

  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.

• update_knowmapped_map

  Validate or atomically update an editable map with one mixed patch. 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…

• set_knowmapped_map_visibility

  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…

• publish_knowmapped_map

  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…

• get_knowmapped_publication_status

  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…