# Naag (npm · @pipeworx/mcp-naag)

State attorney-general multistate enforcement, from the National Association of Attorneys General…

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

## Components

- remote · `gateway.pipeworx.io`: 86/100, [markdown](https://verifymcp.io/servers/pipeworx-io-naag/naag-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-naag/naag-mcp)
- npm · `@pipeworx/mcp-naag`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-naag/pipeworx-mcp-naag.md), [page](https://verifymcp.io/servers/pipeworx-io-naag/pipeworx-mcp-naag)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-naag`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-07.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-naag).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1029 tokens (~257/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Naag MCP server?

Naag runs locally as an npm package, launched with npx -y @pipeworx/mcp-naag. 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 pipeworx-io-naag -- npx -y @pipeworx/mcp-naag
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-naag": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-naag"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-naag": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-naag"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-naag -- npx -y @pipeworx/mcp-naag
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-naag": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-naag"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-naag --command npx --arg -y --arg @pipeworx/mcp-naag
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-naag:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-naag"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-naag": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-naag"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-naag -t stdio -c npx -a -y @pipeworx/mcp-naag
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-naag": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-naag"
      ]
    }
  }
}
```

## 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-07 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

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

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −13)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-02 (score 79, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `naag_multistate_cases` (~430 tokens)

Search the National Association of Attorneys General database of MULTISTATE enforcement cases — lawsuits and investigations that coalitions of US state attorneys general brought together, largely antitrust and consumer protection: price-fixing, bid rigging, merger challenges, monopolization. Answers "which states sued this company together", "what multistate antitrust actions were filed this year", and "how were they resolved". Each case returns the case name, filing date, the participating and lead states, case and relief type, industry, resolution status, any federal co-plaintiff (DOJ, FTC) and a summary of the complaint.

Input parameters:

- `case_type` (string): Conduct at issue, e.g. "price-fixing", "merger-review", "bid-rigging", "monopolization", "market-allocation-agreement".
- `federal_partner` (string): Federal agency that joined as co-plaintiff: "usdoj" or "ftc".
- `filed_from` (string): Earliest date the case record carries, YYYY-MM-DD.
- `filed_to` (string): Latest date the case record carries, YYYY-MM-DD.
- `industry` (string): Industry the defendants operate in, e.g. "pharmaceuticals", "insurance", "hospitals", "dairy".
- `lead_state` (string): A state that led the case as named plaintiff — two-letter code or full name.
- `limit` (number): Cases to return, 1-50 (default 20).
- `offset` (number): Cases to skip, for paging (default 0).
- `query` (string): Free text over case names and complaint summaries, e.g. a defendant ("Amazon", "Paramount") or a practice ("generic drug").
- `resolution` (string): How it ended, e.g. "settled", "pending", "consent-decree", "dismissed", "final-judgment".
- `state` (string): A state that joined the coalition — two-letter code or full name ("NY", "New York").

### `naag_case_detail` (~118 tokens)

The full NAAG record for one multistate attorney-general case, given its numeric id or naag.org URL from naag_multistate_cases. Returns the complete complaint summary rather than a truncated one, plus every classification the record carries: participating states, lead plaintiff states, conduct type, civil or criminal, relief sought, resolution status, industry and any federal co-plaintiff.

Input parameters:

- `case` (string, required): Numeric case id (e.g. "48390") or the naag.org/multistate-case/... URL.

### `naag_policy_letters` (~208 tokens)

Multistate coalition policy letters — the comment letters and formal positions that groups of state attorneys general send jointly to Congress, federal agencies and companies, on subjects like robocalls, AI, opioids and consumer data. Answers "have state AGs written to the FCC about this" and "which states signed that coalition letter". Returns the letter title, date, signing states and a summary, sourced from NAAG.

Input parameters:

- `limit` (number): Letters to return, 1-50 (default 20).
- `offset` (number): Letters to skip (default 0).
- `query` (string): Free text over letter titles and bodies, e.g. "robocall", "artificial intelligence", "Know Your Customer".
- `sent_from` (string): Earliest letter date, YYYY-MM-DD.
- `sent_to` (string): Latest letter date, YYYY-MM-DD.
- `state` (string): A state that signed — two-letter code or full name.

### `naag_press_releases` (~221 tokens)

Announcements and analysis published by the National Association of Attorneys General: press releases on coalition actions state AGs have just taken, and Attorney General Journal articles on consumer protection, antitrust, cybersecurity, public health and criminal law. Answers "what did state attorneys general announce recently" on a topic. Returns headline, date, topic category, summary and the naag.org link.

Input parameters:

- `limit` (number): Items to return, 1-50 (default 20).
- `offset` (number): Items to skip (default 0).
- `published_from` (string): Earliest publication date, YYYY-MM-DD.
- `published_to` (string): Latest publication date, YYYY-MM-DD.
- `query` (string): Free text over headlines and summaries, e.g. "robocall", "opioid settlement", "data breach".
- `topic` (string): Topic category, e.g. "consumer-protection", "antitrust", "cybersecurity-and-privacy", "public-health", "criminal-law", "opioids".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-naag/pipeworx-mcp-naag#diagnostics

## Score history

- 2026-11-07: 83
- 2026-11-06: 82
- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 66
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Naag MCP server?

Naag is an MCP server listed in the public MCP registry as io.github.pipeworx-io/naag. State attorney-general multistate enforcement, from the National Association of Attorneys General… This page covers its npm package (@pipeworx/mcp-naag).

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

Naag scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Naag MCP server expose?

Naag exposes 4 tools: naag_multistate_cases, naag_case_detail, naag_policy_letters, naag_press_releases. Their descriptions and schemas cost roughly 977 tokens of context every time the server is loaded.

### Is the Naag MCP server still maintained?

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

### What licence is the Naag MCP server under?

Naag declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Naag MCP server?

VerifyMCP ran 16 checks on Naag, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-naag
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-naag
- Repository: https://github.com/pipeworx-io/mcp-naag
- Website: https://pipeworx.io/packs/naag
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-naag/pipeworx-mcp-naag.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-naag/pipeworx-mcp-naag/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-naag/pipeworx-mcp-naag.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-naag/pipeworx-mcp-naag