Lattice: CVE, MITRE ATT&CK and detection graph for security agents
CVE, KEV, MITRE ATT&CK, CWE and detection graph for AI agents; every link names its source.
Connect Remote server
claude mcp add --transport http lattice https://lattice.namiq.io/mcp --header "X-API-Key: <X_API_KEY>"
{
"mcpServers": {
"lattice": {
"url": "https://lattice.namiq.io/mcp",
"headers": {
"X-API-Key": "<X_API_KEY>"
}
}
}
}
{
"servers": {
"lattice": {
"type": "http",
"url": "https://lattice.namiq.io/mcp",
"headers": {
"X-API-Key": "<X_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://lattice.namiq.io/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 10 found in our last check
graph_metaDescribe 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 a…
graph_lookupStart 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_searchList 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.
graph_nodeOne 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…
graph_neighborsDirectly 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.
graph_pathAnswer 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), c…
graph_noticesReturn 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 sha…
graph_affectsThe CISA-exploited CVEs that one product and version may concern, each with a verdict: in-range, outside-range or undetermined. Ask about ONE item per call. A result is a lead for a person to read: names are matched, versions are compared as upstream numbers, and a distribution…
graph_exposureThe ATT&CK techniques a posture signal may point to, for a person to read. Ask about ONE signal per call. A technique is a lead, not proof that anything happened; no technique does not mean safe. The signal is not tied to you: no key, address or time of day is kept with it, and…
graph_answerThe same answer the Lattice Analyst page gives for ONE CVE: the verdict, the facts behind it (CISA listing and dates, ransomware use as recorded, score, product, fixed versions) and the graph ids it rests on. Written in code from the graph, no model. One exact CVE id per call; n…
Headers
| Name | Description |
|---|---|
X-API-KeyRequired, secret | Key. A person requests one at https://namiq.io/lattice; an AI agent can POST https://namiq.io/api/v1/lattice/agent-keys. Shown once, and emailed. |
Details
| Endpoint | https://lattice.namiq.io/mcp (Streamable HTTP) |
| First published | 2 Nov 2026 |
| Last updated | 2 Nov 2026 |
| Registry name | io.namiq/lattice |
More security servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
