# Meridian Trace — Medical Device Registrations (remote · meridiantrace.com)

Medical device registrations across 25 markets: coverage gaps, 510(k) predicates, classification

- Trust score: 77/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `meridiantrace.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-meridiantrace-medical-device-registrations/v1-mcp.md), [page](https://verifymcp.io/servers/com-meridiantrace-medical-device-registrations/v1-mcp)

## Channel facts

- Endpoint: `https://meridiantrace.com/v1/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3527 tokens (~293/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Meridian Trace — Medical Device Registrations MCP server?

Meridian Trace — Medical Device Registrations is a hosted endpoint at https://meridiantrace.com/v1/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.

### Claude

```bash
claude mcp add --transport http com-meridiantrace-medical-device-registrations 'https://meridiantrace.com/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-meridiantrace-medical-device-registrations": {
      "url": "https://meridiantrace.com/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-meridiantrace-medical-device-registrations": {
      "type": "http",
      "url": "https://meridiantrace.com/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-meridiantrace-medical-device-registrations]
url = "https://meridiantrace.com/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-meridiantrace-medical-device-registrations": {
      "type": "remote",
      "url": "https://meridiantrace.com/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-meridiantrace-medical-device-registrations --url 'https://meridiantrace.com/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-meridiantrace-medical-device-registrations:
    url: "https://meridiantrace.com/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-meridiantrace-medical-device-registrations": {
      "Transport": "http",
      "Url": "https://meridiantrace.com/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-meridiantrace-medical-device-registrations -t streamable-http -u 'https://meridiantrace.com/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-meridiantrace-medical-device-registrations": {
      "type": "http",
      "url": "https://meridiantrace.com/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 77, +1)

- [security improvement] Stability: fail → pass

### 2026-09-19 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 94.

### 2026-09-16 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 84.

### 2026-09-14 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 74 to 77.

### 2026-09-13 (score 73, +1)

- [security regression] Stability: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100

### 2026-09-12 (score 72, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-10 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 64.

### 2026-09-08 (score 71, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 2990 → 3527
- [functional] New tool “find_distributors”

## MCP tools (12)

### `search_manufacturer` (~150 tokens)

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 to the parent that owns them. Returns up to 5 candidates with a confidence rating and their market footprint. A plain web search cannot do this: a manufacturer's Asian registrations are filed under local-script names that never appear alongside the English one.

Input parameters:

- `country` (string): Optional ISO2 or full country name to narrow results (e.g. "SG" or "Singapore")
- `name` (string, required): Company name to search for

### `get_registrations` (~354 tokens)

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 class as a RANK on that market's own scale ("3 of 4") rather than a label that means different things in different markets, the resolved device type, the clinical area with the number of signals that agreed on it, the FDA product code, country of origin, brand and intended use. Each row carries a `provenance` block naming any field Meridian derived (inferred, classified, translated) with a confidence band where one applies; every field NOT listed there is the registry's own value, unmodified. Use that to lean on verbatim fields and hedge on derived ones. Use get_market_coverage instead when the question is which markets a company is in.

Input parameters:

- `limit` (number): Results per page (default 50, max 200)
- `manufacturer_id` (string, required)
- `market` (string): Filter to a single market — ISO2 code (e.g. "SG") or full name (e.g. "Singapore")
- `page` (number): Page number (default 1)
- `status` (string): Filter by lifecycle state: "active", "expired", "cancelled" or "pending". These are applied as RULES, not string matching — a market that publishes no status (Israel, Mexico, China) is resolved from…

### `get_registration` (~153 tokens)

Get one registration in full

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 EUDAMED device attributes (implantable, sterile, reusable, measuring, latex, tissue origin, legislation), and the manufacturer address — none of which fit a list row. `sourceUrl` links the authority's own record so you can check us. Reading one device exhaustively costs the same as seeing it in a list, and re-reading it is free.

Input parameters:

- `registration_id` (string, required): Registration id from get_registrations, find_similar_devices or get_recent_registrations.

### `get_license_holders` (~95 tokens)

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 party rather than the OEM, so this is the only way to see who controls market access for a product, who a competitor is partnered with, and whether a manufacturer uses one partner or many.

Input parameters:

- `manufacturer_id` (string, required)

### `find_distributors` (~323 tokens)

RUNS WITHOUT AN API KEY (anonymous callers see the top 3 per market and are told how many more matched). WHO COULD SELL A DEVICE IN A MARKET — the question a company entering a market actually has. Give it a market and, optionally, a device type or clinical area; it returns the local distributors and importers who hold registrations there, what clinical areas they cover, how many markets they operate in, and a sample of the lines they already carry. Strongest across Asia, where the registry names the local partner rather than the manufacturer and this relationship is not published anywhere else: Singapore, Malaysia, Thailand, Indonesia, Vietnam, the Philippines, Japan, Korea, Taiwan, India and Hong Kong. This is the INVERSE of get_license_holders, which starts from a manufacturer you can already name. Regulatory consultants and authorised representatives are excluded — they hold licences as a service and do not sell — as are manufacturers' own in-country subsidiaries. Read the `caveats` in the response before quoting any number from it.

Input parameters:

- `device_type` (string): Optional clinical area or device category in plain words, e.g. "orthopaedic implants", "in vitro diagnostics", "cardiology". Partial matches count. Omit it to see the whole channel in that market.
- `limit` (number): 1-25 (default 10). Capped to 3 without a paid key.
- `market` (string, required): ISO2 code or market name, e.g. "TH" or "Thailand". One market per call.

### `get_market_coverage` (~321 tokens)

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 markets absent from their footprint — which is the gap a market-access team is usually looking for ("registered in Indonesia and Thailand, missing in the Philippines"). Prefer this over get_registrations when the question is about market presence rather than individual products. A `marketAccess` block may also appear. It is NOT a registration and is excluded from marketCount and every count in this response: it reports market access held on another basis — currently PMDA foreign manufacturer accreditation, which licenses a manufacturing SITE to make devices for Japan, precedes product approval and outlives individual products. When it is present alongside Japan in `absent`, both are true and the distinction matters: the company can supply the market but has no Japanese product approval visible to us. Do not describe that as being registered in Japan, and do not add it to a market count.

Input parameters:

- `manufacturer_id` (string): The Meridian Trace manufacturer _id, from search_manufacturer
- `name` (string): Company name, as an alternative to manufacturer_id. Resolves the same way search_manufacturer does and uses the best match.
- `ticker` (string): Listed ticker (e.g. "MDT"), as an alternative to manufacturer_id or name. Covers US-listed registrants; many large device makers are private or listed only outside the US and cannot be reached this w…

### `get_registration_timeline` (~224 tokens)

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 reaches back as far as the registry publishes (56 years for the US). Every market carries a historyQuality flag: complete_archive and retains_lapsed series are safe to trend, current_state_only markets publish only today's position and undercount anything since withdrawn. Use for entry velocity, launch cadence, and comparing two competitors' expansion over time.

Input parameters:

- `from_year` (number): First year to include (default: 10 years ago)
- `manufacturer_id` (string): From search_manufacturer
- `market` (string): Restrict to one market (ISO2 or full name)
- `name` (string): Company name, as an alternative to manufacturer_id
- `ticker` (string): Listed ticker, e.g. "SYK" (US-listed coverage)
- `to_year` (number): Last year to include (default: current year)

### `find_predicates` (~193 tokens)

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 predicate — the reverse direction shows whose clearances rest on your device and how contested a space is. By product_code: the predicates that code leans on most, ranked by how often they are cited, plus recent clearances. Use when choosing a predicate, assessing substantial equivalence, or mapping who is clearing devices in a classification.

Input parameters:

- `k_number` (string): A 510(k) number, e.g. "K191275"
- `limit` (number): Max rows per list (default 20, max 50)
- `product_code` (string): An FDA product code, e.g. "LIT"

### `classify_device` (~350 tokens)

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 to with how many devices carry each, and — the part not published anywhere — how the SAME device type is actually risk-classed market by market, with the sample size behind each. Risk class is not portable: a device type can be modal High in Canada and modal Medium in the EU and Singapore, which changes submission route, evidence burden and timeline. Observed practice, not a regulatory determination. Takes a plain device name ("bone screw", "hip implant"), a GMDN code, or an FDA product code. A name is resolved by how many real devices carry each GMDN term rather than by string matching, and `resolution` reports which term was chosen, how many others matched and what they were — call again with `gmdn_code` to classify one of those instead.

Input parameters:

- `device_type` (string): A device name in plain words ("insulin pump", "orthopaedic plate") or a GMDN term. US and British spellings both resolve. Name the device, not the brand or the use — "infusion pump", not "PumpMaster…
- `fda_product_code` (string): FDA product code, e.g. "DZE"
- `gmdn_code` (string): GMDN code, e.g. "44727"

### `find_similar_devices` (~184 tokens)

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 the competitive set. Each result carries a match band. Use for competitive landscape, classification precedent in other markets, and finding how the same device type is described elsewhere. Get a registration_id from get_registrations.

Input parameters:

- `device_name` (string): A product name, as an alternative to registration_id — the closest registration is used as the reference device
- `limit` (number): Max results (default 15)
- `market` (string): With device_name, restrict the reference lookup to one market (ISO2)
- `registration_id` (string): The _id of a registration, from get_registrations

### `get_recent_registrations` (~197 tokens)

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 rather than by approval date. US PMA supplements are excluded: they are labeling and site changes against an existing approval, not new registrations. Filtering by market is much faster — unfiltered across all markets can take up to 15 seconds, a market or two returns in about a second.

Input parameters:

- `days` (number): Look-back window, 1-180 (default 30)
- `device_type` (string): Resolved GMDN device type
- `limit` (number): Max results (default 50, max 100)
- `markets` (array): ISO2 codes, e.g. ["TH","ID"]
- `risk_level` (string): Low | Medium | High

### `get_coverage` (~95 tokens)

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 crawled. Call this to verify coverage and freshness for yourself before relying on other tools, or to answer "do you cover market X, and how current is it?". No arguments.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-meridiantrace-medical-device-registrations/v1-mcp#diagnostics

## Score history

- 2026-09-24: 77
- 2026-09-23: 77
- 2026-09-22: 77
- 2026-09-21: 77
- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 75
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 73
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 71
- 2026-09-08: 71
- 2026-09-07: 71
- 2026-09-06: 70
- 2026-09-05: 70
- 2026-09-04: 69
- 2026-09-03: 69
- 2026-09-02: 68
- 2026-09-01: 68
- 2026-08-31: 67
- 2026-08-30: 67
- 2026-08-29: 66
- 2026-08-28: 66
- 2026-08-27: 65
- 2026-08-26: 65

## Common questions

### What is the Meridian Trace — Medical Device Registrations MCP server?

Meridian Trace — Medical Device Registrations is an MCP server listed in the public MCP registry as com.meridiantrace/medical-device-registrations. Medical device registrations across 25 markets: coverage gaps, 510(k) predicates, classification. This page covers its hosted endpoint (https://meridiantrace.com/v1/mcp).

### Is the Meridian Trace — Medical Device Registrations MCP server safe to use?

Meridian Trace — Medical Device Registrations scores 77 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 Meridian Trace — Medical Device Registrations MCP server expose?

Meridian Trace — Medical Device Registrations exposes 12 tools: search_manufacturer, get_registrations, get_registration, get_license_holders, find_distributors, and 7 more. Their descriptions and schemas cost roughly 2,639 tokens of context every time the server is loaded.

### Does the Meridian Trace — Medical Device Registrations MCP server require authentication?

No. We connected to Meridian Trace — Medical Device Registrations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Meridian Trace — Medical Device Registrations MCP server still maintained?

Meridian Trace — Medical Device Registrations is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://meridiantrace.com/v1/mcp
- Authorisation metadata: https://meridiantrace.com/.well-known/oauth-protected-resource/v1/mcp
- Website: https://meridiantrace.com/agents.html
- Changelog RSS feed: https://verifymcp.io/servers/com-meridiantrace-medical-device-registrations/v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-meridiantrace-medical-device-registrations/v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-meridiantrace-medical-device-registrations/v1-mcp