# Lattice: CVE, MITRE ATT&CK and detection graph for security agents (remote · lattice.namiq.io)

CVE, KEV, MITRE ATT&CK, CWE and detection graph for AI agents; every link names its source.

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `lattice.namiq.io`: 83/100 (this document), [markdown](https://verifymcp.io/servers/io-namiq-lattice/lattice.md), [page](https://verifymcp.io/servers/io-namiq-lattice/lattice)

## Channel facts

- Endpoint: `https://lattice.namiq.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.3`

## 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-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1915 tokens (~273/item across 7 items; 7 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 Lattice: CVE, MITRE ATT&CK and detection graph for… MCP server?

Lattice: CVE, MITRE ATT&CK and detection graph for… is a hosted endpoint at https://lattice.namiq.io/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 io-namiq-lattice 'https://lattice.namiq.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-namiq-lattice": {
      "url": "https://lattice.namiq.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-namiq-lattice": {
      "type": "http",
      "url": "https://lattice.namiq.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-namiq-lattice]
url = "https://lattice.namiq.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-namiq-lattice --url 'https://lattice.namiq.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-namiq-lattice:
    url: "https://lattice.namiq.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-namiq-lattice": {
      "Transport": "http",
      "Url": "https://lattice.namiq.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-namiq-lattice -t streamable-http -u 'https://lattice.namiq.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-namiq-lattice": {
      "type": "http",
      "url": "https://lattice.namiq.io/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-11-05 (score 83, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Stability: pass → 0.97

### 2026-11-04 (score 83, +1)

- [security improvement] Stability: fail → pass

### 2026-11-02 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 84 to 88.

### 2026-10-31 (score 81, +2)

- [security improvement] Judged manipulation: unverified → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “graph_lookup” rewrote its description, which is the text the model reads
- [security] Tool “graph_path” rewrote its description, which is the text the model reads

### 2026-10-29 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 71 to 74.

### 2026-10-27 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 64 to 68.

### 2026-10-25 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 58 to 61.

### 2026-10-23 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 51 to 54.

## MCP tools (7)

### `graph_meta` (~174 tokens)

Describe the graph

Describe the graph this server reads, without looking up any fact in it.

        Returns the snapshot id and creation time, the schema version with notable schema changes, the node labels (types), the relationship verbs, the contributing sources, and the path templates that graph_path accepts.

        When to call it: once at the start of a session, to learn the valid values for the label argument of graph_lookup, graph_search and graph_neighbors, the verb values for graph_neighbors and the template names for graph_path; and when you report a finding, to cite the snapshot id it came from.

        What it is not for: it returns no CVEs, techniques, groups or detections. Use graph_lookup to find those. It takes no arguments, only reads, and gives the same answer to every caller of a snapshot.

### `graph_lookup` (~200 tokens)

Look up an id

Start here when a CVE, ATT&CK technique or CWE id appears in your task. Find nodes by exact external id, e.g. CVE-2021-44228, T1059.001, CWE-79. Returns each match with its source (a CVE has a kev node if CISA lists it as exploited, and an nvd node) and a uid for graph_node and graph_neighbors. An empty items list means the graph has no such id.

Input parameters:

- `id` (string, required): Exact external id, for example CVE-2021-44228, T1059.001 or CWE-79. Case-insensitive; prefixes and free text do not match (use graph_search for a prefix).
- `label`: Optional node label (type) to restrict the answer to, for example CVE, Technique or Detection. The valid labels are listed by graph_meta; an unknown label is refused with the valid ones.

### `graph_search` (~209 tokens)

Search ids by prefix

List nodes whose external id starts with a prefix (e.g. CVE-2024-1, T105). Ids only, not free text. If the answer has truncated: true, pass its next_cursor as cursor to continue; a list without truncated is complete.

Input parameters:

- `cursor`: Continuation token: pass the next_cursor from a previous answer that had truncated: true to get the next page. Omit it for the first page.
- `id_prefix` (string, required): Start of an external id, at least a few characters, for example CVE-2024-1 or T105. Not free text.
- `label`: Optional node label (type) to restrict the answer to, for example CVE, Technique or Detection. The valid labels are listed by graph_meta; an unknown label is refused with the valid ones.
- `limit` (integer): Maximum items to return. The server clamps it to its own maximum; the answer reports applied_limit and limit_clamped.

### `graph_node` (~114 tokens)

Read a node

One node's properties (long text is clipped). uid comes from graph_lookup or graph_search. On a kev node: date_added, due_date, known_ransomware_use (Known or Unknown; Unknown means not recorded), required_action, vendor_project, product. On an nvd node: description and metadata (cvss_score, affected_products). A cvss_score of 0 means not scored yet.

Input parameters:

- `uid` (string, required): The uid of a node, as returned by graph_lookup, graph_search or graph_neighbors.

### `graph_neighbors` (~250 tokens)

List linked nodes

Directly connected nodes with each link's verb, source, confidence and whether it is declared or inferred. Declared and cross-source links come first. If the answer has truncated: true, pass its next_cursor as cursor to continue.

Input parameters:

- `cursor`: Continuation token: pass the next_cursor from a previous answer that had truncated: true to get the next page. Omit it for the first page.
- `direction` (string): Which links to follow: out (from this node), in (to this node) or both.
- `label`: Optional node label (type) to restrict the answer to, for example CVE, Technique or Detection. The valid labels are listed by graph_meta; an unknown label is refused with the valid ones.
- `limit` (integer): Maximum links to return. The server clamps it to its own maximum; the answer reports applied_limit and limit_clamped.
- `uid` (string, required): The uid of the node whose links to list, from graph_lookup, graph_search or graph_node.
- `verb`: Optional upper-case relationship verb to keep, for example EXPLOITS, DETECTS or USES. The valid verbs are listed by graph_meta.

### `graph_path` (~256 tokens)

Answer a multi-hop question

Answer a multi-hop question from an external id in one call instead of several lookups: for a CVE, the attack techniques it enables and the detections and response procedures for them. Needs a key; without one the error says how to get one. Templates: cve-context (start: CVE), cve-to-defense (start: CVE), technique-coverage (start: Technique), weakness-chain (start: Weakness), actor-ttps (start: ThreatActor/Malware/Campaign). Use cve-to-defense when asked what to detect or do about a CVE: it gives the techniques the CVE enables and the detections and procedures for them.

Input parameters:

- `id` (string, required): External id to start from; it must be of a kind the template starts from (see the template list in the tool description).
- `label`: Optional node label (type) to restrict the answer to, for example CVE, Technique or Detection. The valid labels are listed by graph_meta; an unknown label is refused with the valid ones.
- `template` (string, required): Name of the path template, one of: cve-context, cve-to-defense, technique-coverage, weakness-chain, actor-ttps.

### `graph_notices` (~225 tokens)

Get licence notices

Return the licence and attribution notices for the data sources behind an answer.

        Other tools list notice ids with their answers. Pass those ids here to get, for each notice, its title, what it applies to, the obligation it places on you (for example attribution wording or a share-alike condition) and the notice text. Long texts are cut and flagged text_truncated, with text_url pointing to the full text.

        When to call it: before you quote, republish or build on anything the graph returned, and then quote what the obligation requires. Unknown ids are reported in unknown rather than failing.

        What it is not for: it returns no security facts, and it is source licence information, not legal advice. It only reads and gives the same answer each time for a snapshot.

Input parameters:

- `ids`: Notice ids to fetch, as listed in the notice list of other answers, at most 10 per call. Omit to get the notices the server holds (up to 10). Ids it does not know come back in the unknown list.

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 79
- 2026-10-29: 79
- 2026-10-28: 78
- 2026-10-27: 78
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72
- 2026-10-14: 72
- 2026-10-13: 71
- 2026-10-12: 71
- 2026-10-10: 70
- 2026-10-07: 68
- 2026-10-05: 68
- 2026-10-04: 71

## Common questions

### What is the Lattice: CVE, MITRE ATT&CK and detection graph for… MCP server?

Lattice: CVE, MITRE ATT&CK and detection graph for… is an MCP server listed in the public MCP registry as io.namiq/lattice. CVE, KEV, MITRE ATT&CK, CWE and detection graph for AI agents; every link names its source. This page covers its hosted endpoint (https://lattice.namiq.io/mcp).

### Is the Lattice: CVE, MITRE ATT&CK and detection graph for… MCP server safe to use?

Lattice: CVE, MITRE ATT&CK and detection graph for… scores 83 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 Lattice: CVE, MITRE ATT&CK and detection graph for… MCP server expose?

Lattice: CVE, MITRE ATT&CK and detection graph for… exposes 7 tools: graph_meta, graph_lookup, graph_search, graph_node, graph_neighbors, and 2 more. Their descriptions and schemas cost roughly 1,428 tokens of context every time the server is loaded.

### Does the Lattice: CVE, MITRE ATT&CK and detection graph for… MCP server require authentication?

No. We connected to Lattice: CVE, MITRE ATT&CK and detection graph for… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Lattice: CVE, MITRE ATT&CK and detection graph for… MCP server still maintained?

Lattice: CVE, MITRE ATT&CK and detection graph for… is still listed as active in the MCP registry. We last reached this channel on 5 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 Lattice: CVE, MITRE ATT&CK and detection graph for… MCP server?

VerifyMCP ran 13 checks on Lattice: CVE, MITRE ATT&CK and detection graph for…, 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.

## Links

- Remote endpoint: https://lattice.namiq.io/mcp
- Authorisation metadata: https://lattice.namiq.io/.well-known/oauth-protected-resource/mcp
- Website: https://lattice.namiq.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-namiq-lattice/lattice.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-namiq-lattice/lattice/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-namiq-lattice/lattice.json
- HTML version of this page: https://verifymcp.io/servers/io-namiq-lattice/lattice