Meridian Trace — Medical Device Registrations
com.meridiantrace/medical-device-registrations · v1.0.0
Medical device registrations across 25 markets: coverage gaps, 510(k) predicates, classification
MCPremoteAPI keyE-commerce
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 14 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 82/100
What it does: 14 tools · 12 read, 0 write · E-commerce, Health, Developer tools
Test call get_market_coverage: needs a key: rpc error: get_market_coverage needs an API key. You can run get_coverage and classify_device and find_distributors without one to check our covera (915 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +9
- Read/write annotations: 0
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://meridiantrace.com/v1/mcpTools
14 tools listed at last check
search_manufacturerResolve 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 withget_registrationsEvery 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") ratherget_registrationOne 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, mget_license_holdersThe 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 cfind_distributorsRUNS 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 anget_market_coverageTHE 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-get_registration_timelineNew 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 USfind_predicatesUS 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 onclassify_deviceRUNS 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 pubfind_similar_devicesCompeting 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. Useget_recent_registrationsRegistrations 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: thget_coverageRUNS 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 updated. Call this to verify coverage and freshness for yourself breport_data_issueTell Meridian that a record you got from this server looks WRONG — a registration, a manufacturer or a licence holder whose field disagrees with the official registry or the company's own documents. Name the record (registration_id from get_registration / get_registrations, or manufacturer_id, or recheck_issueWhere a report you filed with report_data_issue stands — Received, Looking into it, Fixed, Not changing or Already reported (with the reference it repeats) — and Meridian's reply, if any. Only the API key that filed a report (or another key on the same account) can read it. Needs an API key.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/com.meridiantrace/medical-device-registrations)