io.github.atlasbyauro/atlas-fda
REMOTE · ATLASBYAURO.COM · SCANNED SEP 21
FDA 510(k)s, PMAs, recalls & trials, linked: predicate search and review-time stats for AI agents.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 665 tokens (~95/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.atlasbyauro/atlas-fda MCP server?
io.github.atlasbyauro/atlas-fda is a hosted endpoint at https://atlasbyauro.com/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 · atlasbyauro.com
claude mcp add --transport http atlasbyauro-atlas-fda 'https://atlasbyauro.com/mcp'
{
"mcpServers": {
"atlasbyauro-atlas-fda": {
"url": "https://atlasbyauro.com/mcp"
}
}
} {
"servers": {
"atlasbyauro-atlas-fda": {
"type": "http",
"url": "https://atlasbyauro.com/mcp"
}
}
} [mcp_servers.atlasbyauro-atlas-fda] url = "https://atlasbyauro.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"atlasbyauro-atlas-fda": {
"type": "remote",
"url": "https://atlasbyauro.com/mcp",
"enabled": true
}
}
} openclaw mcp add atlasbyauro-atlas-fda --url 'https://atlasbyauro.com/mcp' --transport streamable-http
mcp_servers:
atlasbyauro-atlas-fda:
url: "https://atlasbyauro.com/mcp" {
"McpServers": {
"atlasbyauro-atlas-fda": {
"Transport": "http",
"Url": "https://atlasbyauro.com/mcp"
}
}
} assistant mcp add atlasbyauro-atlas-fda -t streamable-http -u 'https://atlasbyauro.com/mcp'
{
"mcpServers": {
"atlasbyauro-atlas-fda": {
"type": "http",
"url": "https://atlasbyauro.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 2026 · Probed https://atlasbyauro.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=atlasbyauro.com | CN=WE1,O=Google Trust Services,C=US | 19 Aug 2026 | 17 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | e2a041a6d854136e13227f8b3307a434 |
| SANs: atlasbyauro.com, *.atlasbyauro.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of atlasbyauro.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| atlasbyauro.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://atlasbyauro.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://atlasbyauro.com/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://atlasbyauro.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://atlasbyauro.com/mcp |
| Authorisation server | https://atlasbyauro.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://atlasbyauro.com/mcp | Verified | 200 | |
| http (plaintext) | http://atlasbyauro.com/mcp | Served over HTTP | 200 |
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 →
ai_devices FDA AI-enabled device list ~150
FDA's official Artificial Intelligence-Enabled Medical Devices list (1,500+ authorizations), tracked weekly by Atlas. List recent AI device authorizations, filter by panel or year, or check whether a specific submission number is on the list. openFDA itself has no AI field - this is the joined, queryable version.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 15, max 40) |
| panel | string | – | Filter by lead panel, e.g. Radiology, Cardiovascular |
| submission_number | string | – | Check one submission, e.g. K254207 or DEN200001 |
| year | string | – | Filter by decision year, e.g. 2025 |
No output schema declared.
No examples provided.
find_predicates Find predicate candidates ~80
List predicate device candidates for a 510(k) submission: recent clearances under an FDA product code, with review times and recall indicators. The starting set for predicate research.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max candidates (default 15, max 40) |
| product_code | string | yes | Three-letter FDA product code, e.g. NBW |
No output schema declared.
No examples provided.
get_changes What changed this week ~59
New FDA clearances and recalls since a date - the monitoring feed. Use for 'what changed this week' questions.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| since | string | yes | ISO date, e.g. 2026-08-01 |
No output schema declared.
No examples provided.
get_clearance Get a 510(k) clearance ~43
Full detail for one FDA 510(k) clearance by K-number, including recalls that reference it.
| Name | Type | Req | Description |
|---|---|---|---|
| k_number | string | yes | e.g. K262116 |
No output schema declared.
No examples provided.
product_code_stats FDA review-time statistics ~42
FDA review-time statistics (median and 90th percentile days to decision), clearance count and recall count for a product code.
| Name | Type | Req | Description |
|---|---|---|---|
| product_code | string | yes | – |
No output schema declared.
No examples provided.
search_recalls Search device recalls ~105
Search FDA device recalls by product code, recalling firm, or free text. Returns recall details with links - use to vet a predicate candidate or monitor a market.
| Name | Type | Req | Description |
|---|---|---|---|
| firm | string | – | Recalling firm name (substring match) |
| limit | number | – | Max results (default 15, max 40) |
| product_code | string | – | Three-letter FDA product code, e.g. NBW |
| query | string | – | Free text matched against the recall description |
No output schema declared.
No examples provided.
search_records Search the FDA record ~70
Full-text search across 777k+ FDA 510(k) clearances, device recalls, and registered clinical trials. Returns ranked matches with links.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Optional: restrict to one record type |
| query | string | yes | Device name, manufacturer, sponsor, condition, or identifier |
No output schema declared.
No examples provided.
What is the io.github.atlasbyauro/atlas-fda MCP server?
io.github.atlasbyauro/atlas-fda is an MCP server listed in the public MCP registry as io.github.atlasbyauro/atlas-fda. FDA 510(k)s, PMAs, recalls & trials, linked: predicate search and review-time stats for AI agents. This page covers its hosted endpoint (https://atlasbyauro.com/mcp).
Is the io.github.atlasbyauro/atlas-fda MCP server safe to use?
io.github.atlasbyauro/atlas-fda scores 87 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 io.github.atlasbyauro/atlas-fda MCP server expose?
io.github.atlasbyauro/atlas-fda exposes 7 tools: search_records, find_predicates, get_clearance, product_code_stats, ai_devices, and 2 more. Their descriptions and schemas cost roughly 549 tokens of context every time the server is loaded.
Does the io.github.atlasbyauro/atlas-fda MCP server require authentication?
Yes. io.github.atlasbyauro/atlas-fda asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.atlasbyauro/atlas-fda MCP server still maintained?
io.github.atlasbyauro/atlas-fda is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.