List your agent

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

MCP server● Hosted · onlinev0.2.3

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

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: review pull requests.
All AI agents to review pull requests, ranked →

Similar tools

Listed for the same task: review pull requests

Reviews

No review yet. Used Lattice: CVE, MITRE ATT&CK and detection graph for security agents? Be the first to help others choose.

What it does

Lattice: CVE, MITRE ATT&CK and detection graph for security agents is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: security scanning. That makes it a candidate for tasks such as review pull requests or scan code for vulnerabilities.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.2.3
PriceNot in the registry
First seen04 Oct 2026
Last checked2d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 40m ago (live check)

Hosted endpoint

  • https://lattice.namiq.io/mcp streamable-http

Required: X-API-Key (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "lattice": {
      "url": "https://lattice.namiq.io/mcp",
      "headers": {
        "X-API-Key": "<your X-API-Key>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Reliability

Re-tested about every 3 days · last check 40m ago
100%Observed availability, 30 days · 10 checks
10 / 0Answers / failures, 30 days
No key neededAccess status (latest answer)
Observed test history · one mark = one check
22 Oct19 Nov
AnsweredAnswered, key requiredNo valid answer

Observed endpoint availability: the share of our conclusive checks that got an answer. A request for a key or sign-in counts as an answer (the server is up, its access is protected). Timeouts, unreachable endpoints, server errors and invalid MCP replies count as failures; rate-limited checks and checks during our own incidents are not counted. This is what we observed at each check, not continuous uptime: an outage between two checks may go unseen. The 90-day figure will appear once 90 days of checks exist (checks since 19 Oct 2026). How we measure

Tool changes

Tool tracking since 13 Nov 2026 · test history since 19 Oct 2026

No tool added or removed since tracking started. 10 tools in the latest list.

Changes are confirmed by comparing complete tool lists only, read about every 3 days, and dated by the day we saw them. A renamed tool appears as one removal and one addition.

Live check

Electra Index connected to the hosted endpoint 40m ago

ONLINE Lattice: CVE, MITRE ATT&CK and detection graph for security agents answered an MCP connection on 19 Nov 2026 and introduced itself as namiq-lattice 1.23.3 (MCP protocol 2025-06-18).

10 tools offered to AI assistants

  • 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, a
  • graph_lookup · 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
  • 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.
  • 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. O
  • 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_path · 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.
  • 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 (f
  • graph_affects · The 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 a
  • graph_exposure · The 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, addre
  • graph_answer · The 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,

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Re-tested about every 3 days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Version0.2.3DECLAREDSRC-001 Official MCP Registry2d ago
Hosted endpointhttps://lattice.namiq.io/mcpDECLAREDSRC-001 Official MCP Registry2d ago
Websitehttps://lattice.namiq.ioDECLAREDSRC-001 Official MCP Registry2d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry2d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry2d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry2d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry2d ago

Change history

  • VERSION02 Nov 2026
    0.2.2 → 0.2.3
  • VERSION02 Nov 2026
    0.2.1 → 0.2.2
  • VERSION05 Oct 2026
    0.2.0 → 0.2.1
  • NEW04 Oct 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Lattice: CVE, MITRE ATT&CK and detection graph for security agents? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Lattice: CVE, MITRE ATT&CK and detection graph for security agentsLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Lattice: CVE, MITRE ATT&CK and detection graph for security agents?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/lattice?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/lattice/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Lattice: CVE, MITRE ATT&CK and detection graph for security agents

How do I connect Lattice: CVE, MITRE ATT&CK and detection graph for security agents?

Use the hosted endpoint https://lattice.namiq.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Lattice: CVE, MITRE ATT&CK and detection graph for security agents need an API key or token?

Yes. The registry entry lists a required value: X-API-Key. Get it from the publisher.

What tools does Lattice: CVE, MITRE ATT&CK and detection graph for security agents offer?

When Electra Index connected on 19 Nov 2026, it listed 10 tools: graph_meta, graph_lookup, graph_search, graph_node, graph_neighbors, graph_path, graph_notices, graph_affects and more. The full list is in "Live check" above.

Is Lattice: CVE, MITRE ATT&CK and detection graph for security agents online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 40m ago.

What can I use Lattice: CVE, MITRE ATT&CK and detection graph for security agents for?

Based on its description, it is most relevant to: review pull requests, scan code for vulnerabilities.