# ai.argushq/enforcement-database (remote · argushq.ai)

Search Argus HQ public FDA enforcement data: warning letters, recalls, approvals, 483s.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `argushq.ai`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ai-argushq-enforcement-database/api-mcp.md), [page](https://verifymcp.io/servers/ai-argushq-enforcement-database/api-mcp)

## Channel facts

- Endpoint: `https://argushq.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 304 tokens (~60/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-argushq-enforcement-database https://argushq.ai/api/mcp
```

### Codex

```toml
[mcp_servers.ai-argushq-enforcement-database]
url = "https://argushq.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-argushq-enforcement-database": {
      "type": "remote",
      "url": "https://argushq.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-argushq-enforcement-database --url https://argushq.ai/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-argushq-enforcement-database:
    url: "https://argushq.ai/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-argushq-enforcement-database": {
      "type": "http",
      "url": "https://argushq.ai/api/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-08-03 (score 70, +1)

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

### 2026-08-01 (score 69, +1)

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

### 2026-07-31 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 67, +1)

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

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (5)

### `search_enforcement` (~64 tokens)

Search FDA enforcement records

Full-text search across all 1,000+ Argus HQ FDA enforcement pages (warning letters, recalls, approvals, 483 inspections) by keyword, product name, or company name.

Input parameters:

- `query` (string, required): Search text -- company name, product, or keyword

### `get_company_history` (~68 tokens)

Get a company's full FDA enforcement history

Every FDA warning letter, recall, approval, and 483 citation Argus HQ has recorded for a given company, by its Argus HQ company slug (e.g. "pfizer-inc").

Input parameters:

- `slug` (string, required): Argus HQ company slug, e.g. "pfizer-inc"

### `get_recall_by_lot` (~43 tokens)

Look up a recall by lot number

Finds every FDA recall record that references a specific product lot number.

Input parameters:

- `lot_number` (string, required): The lot number printed on the product/packaging

### `get_warning_letter` (~83 tokens)

Look up an FDA warning letter by reference number

Direct lookup of an FDA warning letter. Accepts either the FDA reference number printed in the letter itself (e.g. "320-26-65") or the fda.gov URL slug ID for the letter.

Input parameters:

- `wl_number` (string, required): FDA warning letter reference number (e.g. "320-26-65") or fda.gov URL slug ID

### `list_recent_actions` (~46 tokens)

List recent FDA enforcement actions

The most recent published FDA warning letters, recalls, approvals, and 483 citations across all streams.

Input parameters:

- `days` (integer): How many trailing days to include (default 7)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-argushq-enforcement-database/api-mcp#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 68
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://argushq.ai/api/mcp
- Repository: https://github.com/andrewjgaber-commits/empire-distribution
- Website: https://argushq.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-argushq-enforcement-database/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-argushq-enforcement-database/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-argushq-enforcement-database/api-mcp