Atlas Fda

io.github.atlasbyauroPublished by GitHub account atlasbyaurov1.0.0Updated Oct 25, 2026

FDA 510(k)s, PMAs, recalls & trials, linked: predicate search and review-time stats for AI agents.

The publisher's own server: Red Atlas Api

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote MCP server that gives AI assistants linked FDA 510(k), PMA, recall and clinical trial data, including predicate search and review-time statistics.

What you can do
Look up FDA 510(k) clearances, PMAs, recalls and clinical trials, with records linked across these sources. Search for predicate devices and compare candidates. Review clearance review-time statistics. The manifest lists no individual tools, so exact operations are not documented.
When to use it
Useful for regulatory, medical-device or research work where an assistant needs FDA clearance, recall or trial context, or help finding predicate devices and review timelines.
Requirements
A remote streamable HTTP endpoint; no local package, environment variables or headers are declared. The manifest declares no authentication, so no account or API key setup is shown.
Before you install
The manifest declares no authentication and no credentials are requested. The data is regulatory information from a third party and should be verified against official FDA sources before regulatory or compliance decisions.

Installation

In SourceWeft

  1. Open Atlas Fda in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.atlasbyauro%2Fatlas-fda/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "atlas-fda": {
      "type": "http",
      "url": "https://atlasbyauro.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Atlas integrations