# KnowMapped (remote · mcp.knowmapped.com)

Search, retrieve, create, and update visual knowledge maps in a user's KnowMapped account.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `mcp.knowmapped.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-knowmapped-mcp/mcp.md), [page](https://verifymcp.io/servers/com-knowmapped-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.knowmapped.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_knowmapped_map).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1202 tokens (~120/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 13% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the KnowMapped MCP server?

KnowMapped is a hosted endpoint at https://mcp.knowmapped.com/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.

### Claude

```bash
claude mcp add --transport http com-knowmapped-mcp 'https://mcp.knowmapped.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-knowmapped-mcp": {
      "url": "https://mcp.knowmapped.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-knowmapped-mcp": {
      "type": "http",
      "url": "https://mcp.knowmapped.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-knowmapped-mcp]
url = "https://mcp.knowmapped.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-knowmapped-mcp": {
      "type": "remote",
      "url": "https://mcp.knowmapped.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-knowmapped-mcp --url 'https://mcp.knowmapped.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-knowmapped-mcp:
    url: "https://mcp.knowmapped.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-knowmapped-mcp": {
      "Transport": "http",
      "Url": "https://mcp.knowmapped.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-knowmapped-mcp -t streamable-http -u 'https://mcp.knowmapped.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-knowmapped-mcp": {
      "type": "http",
      "url": "https://mcp.knowmapped.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 77, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-23 (score 77, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-22 (score 76, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-21 (score 76, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-20 (score 75, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-19 (score 75, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-18 (score 74, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-17 (score 74, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (10)

### `get_knowmapped_update_schema` (~42 tokens)

Get the 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` (~62 tokens)

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.

Input parameters:

- `limit` (integer)
- `query` (string)

### `get_knowmapped_map` (~168 tokens)

Get a 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 without graph content or compact for token-efficient fields. Search results return copy-safe map references so UUIDs should not be typed manually.

Input parameters:

- `edge_offset` (integer): Zero-based offset for the independently paginated edge collection.
- `include` (string)
- `include_edges` (string)
- `include_nodes` (string)
- `map_id` (string, required)
- `node_offset` (integer): Zero-based offset for the independently paginated node collection.
- `page_size` (integer): Maximum nodes and maximum edges returned in this page (1-200).

### `get_knowmapped_map_adjacency` (~73 tokens)

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.

Input parameters:

- `exact_label`
- `limit` (integer)
- `map_id` (string, required)
- `node_id`
- `offset` (integer)

### `get_knowmapped_layout_summary` (~31 tokens)

Get KnowMapped layout summary

Return layout bounds and graph statistics without returning graph content.

Input parameters:

- `map_id` (string, required)

### `preflight_knowmapped_map_creation` (~138 tokens)

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 remain until the map client detects them and applies Smart on first draw; the response reports layout_application=client-first-draw. Complete explicit coordinates are preserved. 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.

Input parameters:

- `graph`
- `idempotency_key`

### `create_knowmapped_map` (~168 tokens)

Create a 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 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.

Input parameters:

- `confirm_credit_use` (boolean)
- `graph` (object, required)
- `idempotency_key` (string, required)
- `validate_only` (boolean)

### `confirm_knowmapped_map_creation` (~88 tokens)

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 again. Use get_knowmapped_map_creation_result after a timeout or malformed response.

Input parameters:

- `confirm_credit_use` (boolean)
- `draft_id` (string, required)

### `get_knowmapped_map_creation_result` (~67 tokens)

Get a 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.

Input parameters:

- `draft_id`
- `idempotency_key`

### `update_knowmapped_map` (~239 tokens)

Update a 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 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.

Input parameters:

- `expected_revision` (integer, required)
- `idempotency_key` (string, required)
- `map_id` (string, required)
- `operations` (array, required): One atomic patch. Node references accept IDs, declared temp IDs, or {"label":"Exact unique label"}.
- `validate_only` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-knowmapped-mcp/mcp#diagnostics

## Score history

- 2026-09-24: 77
- 2026-09-23: 77
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 71
- 2026-09-10: 71
- 2026-09-09: 70
- 2026-09-08: 70
- 2026-09-07: 69
- 2026-09-06: 69
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 67
- 2026-09-02: 67
- 2026-09-01: 66
- 2026-08-31: 66
- 2026-08-30: 65
- 2026-08-29: 65
- 2026-08-28: 65
- 2026-08-27: 64
- 2026-08-26: 64

## Common questions

### What is the KnowMapped MCP server?

KnowMapped is an MCP server listed in the public MCP registry as com.knowmapped/mcp. Search, retrieve, create, and update visual knowledge maps in a user's KnowMapped account. This page covers its hosted endpoint (https://mcp.knowmapped.com/mcp).

### Is the KnowMapped MCP server safe to use?

KnowMapped scores 77 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 KnowMapped MCP server expose?

KnowMapped exposes 10 tools: get_knowmapped_update_schema, search_knowmapped_maps, get_knowmapped_map, get_knowmapped_map_adjacency, get_knowmapped_layout_summary, and 5 more. Their descriptions and schemas cost roughly 1,076 tokens of context every time the server is loaded.

### Does the KnowMapped MCP server require authentication?

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

### Is the KnowMapped MCP server still maintained?

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

## Links

- Remote endpoint: https://mcp.knowmapped.com/mcp
- Website: https://knowmapped.com/integrations/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-knowmapped-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-knowmapped-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-knowmapped-mcp/mcp