Is 483 Risk Radar down?

pulsemcp/483-risk-radar · v0.5.3

Also listed as awesome/thehealthai/fda-risk-radar-mcp, glama/thehealthai/constat-483-risk-radar

healthy
Last checked 2026-10-20 00:00 UTC · handshake 517ms

As of 2026-10-20 00:00 UTC, 483 Risk Radar is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 9 minutes.

uptime (30d checks)
100%
checks observed
3,877
outages (90d)
1
tools
14

FDA & NHTSA regulatory risk intelligence for AI agents: compliance, 510(k) evidence, postmarket surveillance, and reimbursement data.

Install 483 Risk Radar

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http 483-risk-radar https://radar.healthai.com/api/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "483-risk-radar": {
      "type": "http",
      "url": "https://radar.healthai.com/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (94/100)

A (94/100): 0 error(s), 2 warning(s) across 14 tool(s); ~3,404 tokens of tool definitions.
Scores higher than 79% of 15,380 MCP servers Glimind has audited.
Its tool list costs an agent ~3,404 tokens per session — more than 55% of servers.
94 → 94 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions75
Safety hints100
Token cost100
Client compatibility100
Protocol100
Reliability85
Stability100

What to fix (2)

6 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: evidence_search, postmarket_search, reimbursement_search

Handshake + tools/list takes ~1,829 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["pulsemcp/483-risk-radar"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "pulsemcp/483-risk-radar"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/pulsemcp%2F483-risk-radar.svg)](https://glimind.com/server/pulsemcp%2F483-risk-radar?ref=badge)
HTML 
<a href="https://glimind.com/server/pulsemcp%2F483-risk-radar?ref=badge"><img src="https://glimind.com/v1/readiness/badge/pulsemcp%2F483-risk-radar.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/pulsemcp%2F483-risk-radar.svg
   :target: https://glimind.com/server/pulsemcp%2F483-risk-radar?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:38442fdc46c66e8e…, first seen 2026-10-17, included at leaf 1849 of 29,557. Version history · verify what your client received.

Tools (14)

Compare: most reliable data servers · most reliable knowledge servers · most reliable search servers · most reliable retrieval servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is 483 Risk Radar down right now?

As of 2026-10-20 00:00 UTC, 483 Risk Radar is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 9 minutes.

How many tools does 483 Risk Radar provide?

483 Risk Radar advertises 14 tools, including cohort_postmarket_stats, device_evidence_lookup, device_postmarket_lookup, device_risk_lookup, evidence_cohort_stats.

How do I install 483 Risk Radar?

Point your MCP client at this streamable_http endpoint: https://radar.healthai.com/api/mcp

Is 483 Risk Radar safe to connect to an AI agent?

Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of 483 Risk Radar?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve