Can I grant read-only access to the RecallRadar MCP server?

Not documented. We found no scope list to read.

Can the RecallRadar MCP server be self-hosted?

Not from the registry record. No installable package is declared, so the vendor-hosted endpoint is the only documented option.

Vendor-published

RecallRadar MCP server

Search U.S. FDA, USDA FSIS, and CPSC recalls, fetch one, or diff since a date. API key or x402.

RecallRadar (`app.withglint.recallradar/recallradar`, v1.0.0) is published by the vendor. It exposes a hosted endpoint over streamable-http, and no self-hostable package. It accepted a connection with no credentials when we checked. 4 of 4 enterprise control criteria are undocumented. Last checked 2026-09-19.

Add to comparison Vendor documentation

Identity and maintenance

Publisher and version information
Registry name	app.withglint.recallradar/recallradar
Publisher domain	withglint.app
Maintainer type	Vendor-published namespace app.withglint.recallradar -> withglint.app; host recallradar.withglint.app is within withglint.app
Latest version seen	1.0.0
Last checked	2026-09-19
Last changed	2026-09-19 Separate from “last checked”: we check far more often than anything changes.

Enterprise evaluation

Every row below exists whether or not we found an answer. Expand any row to see the exact source and the date. Unknown means undocumented, never unsupported.

Enterprise evaluation criteria for RecallRadar
Access and authentication
Authentication required Whether the hosted endpoint accepted a connection with no credentials when we checked.	No We checked checked 2026-09-19 POST initialize without credentials -> HTTP 200; the server responded and did not require credentials Unauthenticated connection attempt — https://recallradar.withglint.app/mcp
OAuth 2.1 authorization Whether the server publishes OAuth discovery metadata a client can follow automatically.	Not documented We checked checked 2026-09-19 no OAuth discovery document at either well-known location OAuth discovery metadata — https://recallradar.withglint.app/mcp
Dynamic client registration Without it, an IdP administrator must register a client by hand before anyone can connect.	Could not reach source We checked checked 2026-09-19 no authorization-server metadata document found Authorization server metadata — https://recallradar.withglint.app/mcp
Documented scopes	Not checked
Read and write are separate scopes A single opaque scope means read-only access cannot be granted: approving access approves everything.	Not checked
Deployment and transport
Streamable HTTP transport	Yes Registry checked 2026-09-19 "type": "streamable-http", "url": "https://recallradar.withglint.app/mcp" MCP Registry record — https://registry.modelcontextprotocol.io/v0/servers?search=app.withglint.recallradar%2Frecallradar&version=latest
SSE transport	No Registry checked 2026-09-19 no sse remote declared MCP Registry record — https://registry.modelcontextprotocol.io/v0/servers?search=app.withglint.recallradar%2Frecallradar&version=latest
Vendor-hosted endpoint Data leaves your network. Where it goes is a question for the vendor's documentation.	Yes Registry checked 2026-09-19 1 remote endpoint(s) declared MCP Registry record — https://registry.modelcontextprotocol.io/v0/servers?search=app.withglint.recallradar%2Frecallradar&version=latest
Self-hostable package A published npm, PyPI, container or bundle artifact you can run inside your own perimeter.	No Registry checked 2026-09-19 no installable package declared MCP Registry record — https://registry.modelcontextprotocol.io/v0/servers?search=app.withglint.recallradar%2Frecallradar&version=latest
Supply chain
Public source repository	No Registry checked 2026-09-19 no repository declared in the registry record MCP Registry record — https://registry.modelcontextprotocol.io/v0/servers?search=app.withglint.recallradar%2Frecallradar&version=latest
Open-source license	Not checked
Repository actively maintained	Not checked
Package deprecated	Not checked
Secret inputs marked as secret Credential-shaped inputs the publisher did not flag as secret may be logged by a client.	Yes Registry checked 2026-09-19 1 credential input(s), all marked isSecret MCP Registry record — https://registry.modelcontextprotocol.io/v0/servers?search=app.withglint.recallradar%2Frecallradar&version=latest
Documented controls
Audit logging documented	Not documented
Access controls documented	Not documented
Data residency documented	Not documented
Data retention documented	Not documented

Tools exposed without credentials

This endpoint answered an unauthenticated tools/list, so the inventory below is what any client can enumerate before authenticating. We listed the names; we did not call anything.

diff_since
get_recall
list_agencies
search_recalls

What remains unknown

11 of 18 criteria are undocumented. These are the questions to put to the vendor — not conclusions about the product.

OAuth 2.1 authorization — no OAuth discovery document at either well-known location
Dynamic client registration — no authorization-server metadata document found
Documented scopes — no source found
Read and write are separate scopes — no source found
Open-source license — no source found
Repository actively maintained — no source found
Package deprecated — no source found
Audit logging documented — no source found
Access controls documented — no source found
Data residency documented — no source found
Data retention documented — no source found

Turn these into a vendor questionnaire

How we checked

One unauthenticated initialize request, plus the two OAuth discovery documents. Nothing was installed or executed. The exact request headers are below so you can reproduce the result — endpoint behaviour can depend on them.

POST https://recallradar.withglint.app/mcp
user-agent: mcpcompare.ai/1.0 (+https://mcpcompare.ai/methodology/probe; probe@mcpcompare.ai)
content-type: application/json
accept: application/json, text/event-stream
mcp-protocol-version: 2025-06-18

-> HTTP 200  (open)
   checked 2026-09-19T17:17:08.928Z

Questions people ask

Does the RecallRadar MCP server require authentication?: No. It accepted a connection with no credentials when we checked on 2026-09-19.
Can I grant read-only access to the RecallRadar MCP server?: Not documented. We found no scope list to read.
Can the RecallRadar MCP server be self-hosted?: Not from the registry record. No installable package is declared, so the vendor-hosted endpoint is the only documented option.