mcpbeat Sign in

Lattice: CVE, MITRE ATT&CK and detection graph for security agents MCP Server

answering

Lattice: CVE, MITRE ATT&CK and detection graph for security agents is answering right now. Last checked 4 min ago. It exposes 7 tools.

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

Uptime history 12 days of history · worst day 98%
12 days agonow
100.0%
Uptime 24h
92 of 92 checks
7
Tools
read from the server
541 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Lattice: CVE, MITRE ATT&CK and detection graph for security agents every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add lattice --transport http https://lattice.namiq.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "lattice": {
      "url": "https://lattice.namiq.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.lattice]
url = "https://lattice.namiq.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "lattice": {
      "url": "https://lattice.namiq.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "lattice": {
      "url": "https://lattice.namiq.io/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

graph
graph_lookup
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.
graph_meta
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_neighbors
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.
graph_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.
graph_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.
graph_path
Answer a fixed multi-hop question from an external id. Templates: cve-context (start: CVE), cve-to-defense (start: CVE), technique-coverage (start: Technique), weakness-chain (start: Weakness), actor-ttps (start: ThreatActor/Malware/Campaign). cve-to-defense gives the techniques a CVE enables and the detections and procedures for them.
graph_search
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.

Endpoints

URLTransportStateLatencyChecked
https://lattice.namiq.io/mcp streamable-http answering 538 ms 4 min ago

Alternatives to Lattice: CVE, MITRE ATT&CK and detection graph for security agents

same job, measured the same way
Agent Security
by mdfifty50-boop

Security scanning and threat detection for AI agents

45 installs/wk local only
Changegamer
by beneb89

Agent-first resource directory for AI agents: protocols, security, RAG, memory, evals, and more.

14 tools answering
APSA mobile app security audit
by ictechgy

Local, evidence-graded Android/iOS security audits of source, APK, AAB and IPA for AI agents.

2 396 installs/wk local only
Promptrejectormcp
by revsmoke

Security gateway for AI agents: detects prompt injections, jailbreaks, and common vulnerabilities.

29 installs/wk local only
Security Intel MCP
by datakoot

CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.

5 tools answering
Shellward
by jnmetacode

AI agent security: 7 MCP tools for injection detection, PII scanning, command safety, DLP.

224 installs/wk local only
Shadowgate MCP
by josephibra

Security firewall for AI agents — scans MCP calls for injection, secrets, and risks.

answering
Zekra
by fadymondy

Long-term memory and a knowledge graph for AI agents: recall, notes, secrets and data sources.

answering

Lattice: CVE, MITRE ATT&CK and detection graph for security agents — questions

Answers built from our own checks of this server.

What can Lattice: CVE, MITRE ATT&CK and detection graph for security agents do?
It exposes 7 tools, read directly from the server on our last check. Among them: graph_lookup, graph_meta, graph_neighbors, graph_node, graph_notices, graph_path and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Lattice: CVE, MITRE ATT&CK and detection graph for security agents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 541 ms. The bar chart above shows every period we have measured.
How do I connect Lattice: CVE, MITRE ATT&CK and detection graph for security agents?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Lattice: CVE, MITRE ATT&CK and detection graph for security agents need an API key?
No. Lattice: CVE, MITRE ATT&CK and detection graph for security agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Lattice: CVE, MITRE ATT&CK and detection graph for security agents?
It answers our handshake in 541 ms on average, which is faster than 21% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.