Meridian Trace — Medical Device Registrations is an MCP server with 11 tools an agent can call, among them classify_device, find_predicates, find_similar_devices. It answers at https://meridiantrace.com/v1/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 9 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Medical device registrations across 25 markets: coverage gaps, 510(k) predicates, classification
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
classify_device | RUNS WITHOUT AN API KEY (anonymous callers see the top 3 FDA product codes and the full per-market risk table — a free key unlocks the rest). Classification view of a device type: the GMDN hierarchy it sits in, the FDA product codes it maps Inputs: gmdn_code, device_type, fda_product_code |
find_predicates | US 510(k) predicate lineage, from the predicates actually cited in each clearance's own summary document — not a similarity guess. 64,567 clearances, 1992-2026. By k_number: what that device cited, AND which later devices cited IT as a pred Inputs: k_number, product_code, limit |
find_similar_devices | Competing and comparable devices for a registration, matched on resolved device type (GMDN) rather than product-name text, and spread across markets so the answer is not all one country. Excludes the same manufacturer, so what comes back is Inputs: registration_id, device_name, market, limit |
get_coverage | RUNS WITHOUT AN API KEY — call it right now to check us before signing up for anything. What Meridian Trace actually holds: every source registry, the market it covers, how many registrations are on file from it, and when it was last crawle |
get_license_holders | The local entities that actually hold a foreign manufacturer's registrations — the importers, distributors and regulatory consultants named on the licence in each market. In Malaysia, Indonesia and Thailand the registry names this local par Inputs: manufacturer_id |
get_market_coverage | THE cross-market question, answered in one call: every market where this manufacturer IS registered and every market where they are NOT. Returns per-market registration and active-registration counts and the source registries, plus the mark Inputs: manufacturer_id, name, ticker |
get_recent_registrations | Registrations newly added to Meridian in the last N days, optionally filtered by market, risk class or device type — the competitor-monitoring feed. Ordered by when we first saw the record, so it surfaces market entries as they appear rathe Inputs: days, markets, risk_level, device_type, limit |
get_registration | One registration, complete. Everything get_registrations returns for that row, plus the registry's own market-specific fields under `registryFields` — Korea's renewal window, Australia's intended purpose, Saudi's authorisation pathway, the Inputs: registration_id |
get_registration_timeline | New registrations per year for a manufacturer, split by market — the pace at which a company is entering markets and launching products, years before it appears in reported revenue. Built from each registry's own approval date, so it reache Inputs: manufacturer_id, name, ticker, from_year, to_year, market |
get_registrations | Every individual registration held by a manufacturer — product name, registration number, status, dates, risk class and source registry — filterable by market and status. Each row also carries an `enrichment` block Meridian derived: device Inputs: manufacturer_id, market, status, page, limit |
search_manufacturer | Resolve a company name to a Meridian manufacturer entity — the entry point for every other tool. Names are unified across spelling variants and scripts, so "Medtronic", "Медтроник" and "美敦力" reach the same entity, and subsidiaries resolve t Inputs: name, country |
Every block below points at https://meridiantrace.com/v1/mcp. Pick your client and copy.
claude mcp add --transport http meridian-trace-medical-device-re https://meridiantrace.com/v1/mcp
{
"mcpServers": {
"meridian-trace-medical-device-re": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://meridiantrace.com/v1/mcp"]
}
}
}{
"mcpServers": {
"meridian-trace-medical-device-re": {
"url": "https://meridiantrace.com/v1/mcp"
}
}
}{
"servers": {
"meridian-trace-medical-device-re": {
"type": "http",
"url": "https://meridiantrace.com/v1/mcp"
}
}
}{
"context_servers": {
"meridian-trace-medical-device-re": {
"url": "https://meridiantrace.com/v1/mcp"
}
}
}{
"mcpServers": {
"meridian-trace-medical-device-re": {
"serverUrl": "https://meridiantrace.com/v1/mcp"
}
}
}{
"mcpServers": {
"meridian-trace-medical-device-re": {
"url": "https://meridiantrace.com/v1/mcp"
}
}
}name: Meridian Trace — Medical Device Registrations
version: 0.0.1
schema: v1
mcpServers:
- name: Meridian Trace — Medical Device Registrations
type: streamable-http
url: https://meridiantrace.com/v1/mcp{
"mcpServers": {
"meridian-trace-medical-device-re": {
"httpUrl": "https://meridiantrace.com/v1/mcp"
}
}
}{
"mcpServers": {
"meridian-trace-medical-device-re": {
"type": "http",
"url": "https://meridiantrace.com/v1/mcp"
}
}
}{
"mcpServers": {
"meridian-trace-medical-device-re": {
"url": "https://meridiantrace.com/v1/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmeridiantrace.com%2Fv1%2Fmcp&type=streamable_http&id=meridian-trace-medical-device-re&name=Meridian%20Trace%20%E2%80%94%20Medical%20Device%20Registrations
It answered our last check on 18 October 2026 in 329 ms. Over 10 checks since 5 September 2026 it answered 9. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by meridiantrace.com and served from meridiantrace.com, the vendor's own domain: https://meridiantrace.com/v1/mcp.
11, as returned by the server's own tools/list on 31 August 2026: classify_device, find_predicates, find_similar_devices, get_coverage, get_license_holders, get_market_coverage, get_recent_registrations, get_registration, and 3 more.
It answered our last check on 18 October 2026 in 329 ms. Over 10 checks since 5 September 2026 it answered 9.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://meridiantrace.com/v1/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.meridiantrace. Endpoint host: meridiantrace.com. ARD identifier: urn:air:com.meridiantrace:mcp:medical-device-registrations.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.