ai.argushq/enforcement-database
REMOTE · ARGUSHQ.AI
Search Argus HQ public FDA enforcement data: warning letters, recalls, approvals, 483s.
Available components
Last scanned (14 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 16 Oct 2026.
Category Health and Science
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (2)
- HTTPS
- Transport
Checks we could not complete (9)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- DNSSEC in Endpoint SecurityDNSSEC not yet verified: we couldn't validate it against a resolver.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://argushq.ai/api/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of argushq.ai. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| argushq.ai. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://argushq.ai/api/mcp | Unreachable | ||
| http (plaintext) | http://argushq.ai/api/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_company_history Get a company's full FDA enforcement history ~68
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").
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Argus HQ company slug, e.g. "pfizer-inc" |
No output schema declared.
No examples provided.
get_recall_by_lot Look up a recall by lot number ~43
Finds every FDA recall record that references a specific product lot number.
| Name | Type | Req | Description |
|---|---|---|---|
| lot_number | string | yes | The lot number printed on the product/packaging |
No output schema declared.
No examples provided.
get_warning_letter Look up an FDA warning letter by reference number ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| wl_number | string | yes | FDA warning letter reference number (e.g. "320-26-65") or fda.gov URL slug ID |
No output schema declared.
No examples provided.
list_recent_actions List recent FDA enforcement actions ~46
The most recent published FDA warning letters, recalls, approvals, and 483 citations across all streams.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many trailing days to include (default 7) |
No output schema declared.
No examples provided.
search_enforcement Search FDA enforcement records ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search text -- company name, product, or keyword |
No output schema declared.
No examples provided.
How do I install the ai.argushq/enforcement-database MCP server?
ai.argushq/enforcement-database is a hosted endpoint at https://argushq.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · argushq.ai
claude mcp add --transport http ai-argushq-enforcement-database 'https://argushq.ai/api/mcp'
What is the ai.argushq/enforcement-database MCP server?
ai.argushq/enforcement-database is an MCP server listed in the public MCP registry as ai.argushq/enforcement-database. Search Argus HQ public FDA enforcement data: warning letters, recalls, approvals, 483s. This page covers its hosted endpoint (https://argushq.ai/api/mcp).
Is the ai.argushq/enforcement-database MCP server safe to use?
ai.argushq/enforcement-database scores 0 out of 100 on VerifyMCP. 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 ai.argushq/enforcement-database MCP server expose?
ai.argushq/enforcement-database exposes 5 tools: search_enforcement, get_company_history, get_recall_by_lot, get_warning_letter, list_recent_actions. Their descriptions and schemas cost roughly 304 tokens of context every time the server is loaded.
Does the ai.argushq/enforcement-database MCP server require authentication?
Its publisher declares no required credentials for ai.argushq/enforcement-database. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the ai.argushq/enforcement-database MCP server still maintained?
ai.argushq/enforcement-database has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ai.argushq/enforcement-database MCP server?
VerifyMCP ran 2 checks on ai.argushq/enforcement-database, covering HTTPS and Transport. 9 items could not be completed, a gap on our side rather than a finding about ai.argushq/enforcement-database: TLS certificate, Authorization, HSTS header, DNSSEC and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.