Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Meridian Trace — Medical Device Registrations

REMOTE · MERIDIANTRACE.COM

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

−7 this week 76 Trust /100

Last scanned (13 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5592 tokens (~372/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 14 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 98% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 15 Nov 26 −7
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.1.0 ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_distributors” rewrote its description, which is the text the model reads security
    • Tool “get_market_coverage” rewrote its description, which is the text the model reads security
    • Schema quality: 316 → 372 ▼ functional
    • “check_issue” added a required parameter “reason”, so existing callers break ▼ functional
    • “check_issue” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “classify_device” added a required parameter “reason”, so existing callers break ▼ functional
    • “classify_device” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “find_distributors” added a required parameter “reason”, so existing callers break ▼ functional
    • “find_distributors” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “find_predicates” added a required parameter “reason”, so existing callers break ▼ functional
    • “find_predicates” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “find_similar_devices” added a required parameter “reason”, so existing callers break ▼ functional
    • “find_similar_devices” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “get_coverage” added a required parameter “reason”, so existing callers break ▼ functional
    • “get_coverage” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “get_license_holders” added a required parameter “reason”, so existing callers break ▼ functional
    • “get_license_holders” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “get_market_coverage” added a required parameter “reason”, so existing callers break ▼ functional
    • “get_market_coverage” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “get_recent_registrations” added a required parameter “reason”, so existing callers break ▼ functional
    • “get_recent_registrations” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “get_registration” added a required parameter “reason”, so existing callers break ▼ functional
    • “get_registration” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “get_registration_timeline” added a required parameter “reason”, so existing callers break ▼ functional
    • “get_registration_timeline” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “get_registrations” added a required parameter “reason”, so existing callers break ▼ functional
    • “get_registrations” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “report_data_issue” added a required parameter “reason”, so existing callers break ▼ functional
    • “report_data_issue” added a required parameter “user_intent”, so existing callers break ▼ functional
    • “search_manufacturer” added a required parameter “reason”, so existing callers break ▼ functional
    • “search_manufacturer” added a required parameter “user_intent”, so existing callers break ▼ functional
    • New tool “report_outcome” functional
  • 13 Nov 26 +6
    • Authorization: unverified → partial ▲ security
    • Server version: 1.0.0 → 1.1.0 functional
    • Tool “check_issue” changed its title: Check a reported problem cosmetic
    • Tool “classify_device” changed its title: Classify a device type cosmetic
    • Tool “find_distributors” changed its title: Find distributors in a market cosmetic
    • Tool “find_predicates” changed its title: Find 510(k) predicates cosmetic
    • Tool “find_similar_devices” changed its title: Find similar devices cosmetic
    • Tool “get_coverage” changed its title: Data coverage cosmetic
    • Tool “get_license_holders” changed its title: Licence holders cosmetic
    • Tool “get_market_coverage” changed its title: Market coverage and gaps cosmetic
    • Tool “get_recent_registrations” changed its title: Recent registrations cosmetic
    • Tool “get_registration_timeline” changed its title: Registration timeline cosmetic
    • Tool “get_registrations” changed its title: List registrations cosmetic
    • Tool “report_data_issue” changed its title: Report a data problem cosmetic
    • Tool “search_manufacturer” changed its title: Find a manufacturer cosmetic
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://meridiantrace.com/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=meridiantrace.com CN=YE2,O=Let's Encrypt,C=US 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA384 634fa35804ca892ba622d799535844ad92b
SANs: meridiantrace.com, www.meridiantrace.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of meridiantrace.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
meridiantrace.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://meridiantrace.com/v1/mcp Verified 200
http (plaintext) http://meridiantrace.com/v1/mcp HTTPS enforced 301 https://meridiantrace.com/v1/mcp
MCP tools · 15 exposed · ~4,504 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_issue ~150

Where 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.

NameTypeReqDescription
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
refstringyesThe reference report_data_issue returned, e.g. MT-1042
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

classify_device ~405

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.

NameTypeReqDescription
device_typestring–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_codestring–FDA product code, e.g. "DZE"
gmdn_codestring–GMDN code, e.g. "44727"
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

find_distributors ~608

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, Japanese captive importers and companies whose own registrations show they make what they register. TWO COUNTS, NEVER ONE: `matching` is the distributors that hold registrations in the market; `matchingLicenceOrTenderOnly` is the ones known only from a licence list or a tender award, with no registrations of their own in our data. Those are still potential distributors (often sub-distributors) and are returned too, each row marked `basis: "licence_or_tender_only"`; they rank after registered holders, so pass holder_basis "licence_or_tender_only" to list them. In Singapore a row may carry `classAListedModels`: Class A models it lists with HSA as the dealer — self-declared, not verified by HSA, not registrations, never in registrationCount or the order. Read the `caveats` in the response before quoting any number from it.

NameTypeReqDescription
device_typestring–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.
holder_basisstring–Which distributors to LIST (counts always report both): "all" (default; registered holders rank first), "registrations" (hold registrations here), or "licence_or_tender_only" (known from a licence li…
limitnumber–1-25 (default 10). Capped to 3 without a paid key.
marketstringyesISO2 code or market name, e.g. "TH" or "Thailand". One market per call.
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

find_predicates ~248

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.

NameTypeReqDescription
k_numberstring–A 510(k) number, e.g. "K191275"
limitnumber–Max rows per list (default 20, max 50)
product_codestring–An FDA product code, e.g. "LIT"
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

find_similar_devices ~239

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.

NameTypeReqDescription
device_namestring–A product name, as an alternative to registration_id — the closest registration is used as the reference device
limitnumber–Max results (default 15)
marketstring–With device_name, restrict the reference lookup to one market (ISO2)
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
registration_idstring–The _id of a registration, from get_registrations
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

get_coverage ~149

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 updated. 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.

NameTypeReqDescription
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

get_license_holders ~150

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.

NameTypeReqDescription
manufacturer_idstringyes–
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

get_market_coverage ~502

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. A `singaporeClassAListings` block may also appear: self-declared Class A listings in Singapore, not registrations; HSA does not verify them (Class A is exempt from registration). Its count is of LISTED MODELS; it is never in marketCount or `registered`, carries no dates (nothing in it is new), and its `attribution` must be quoted with any figure from it. A `notJudged` block lists markets that register only decree-listed categories (Chile): a company with no rows there is NOT missing there — most devices need no registration — so never report it as a gap.

NameTypeReqDescription
manufacturer_idstring–The Meridian Trace manufacturer _id, from search_manufacturer
namestring–Company name, as an alternative to manufacturer_id. Resolves the same way search_manufacturer does and uses the best match.
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
tickerstring–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…
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

get_recent_registrations ~301

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. Records that arrived in a bulk load (a registry's history or a first load) are excluded too and named in meta.basis.bulkLoadsExcluded; meta.basis.note says what was left out — repeat it rather than calling the list complete. 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.

NameTypeReqDescription
daysnumber–Look-back window, 1-180 (default 30)
device_typestring–Resolved GMDN device type
limitnumber–Max results (default 50, max 100)
marketsarray–ISO2 codes, e.g. ["TH","ID"]
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
risk_levelstring–Low | Medium | High
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

get_registration ~208

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.

NameTypeReqDescription
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
registration_idstringyesRegistration id from get_registrations, find_similar_devices or get_recent_registrations.
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

get_registration_timeline ~279

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.

NameTypeReqDescription
from_yearnumber–First year to include (default: 10 years ago)
manufacturer_idstring–From search_manufacturer
marketstring–Restrict to one market (ISO2 or full name)
namestring–Company name, as an alternative to manufacturer_id
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
tickerstring–Listed ticker, e.g. "SYK" (US-listed coverage)
to_yearnumber–Last year to include (default: current year)
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

get_registrations ~409

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.

NameTypeReqDescription
limitnumber–Results per page (default 50, max 200)
manufacturer_idstringyes–
marketstring–Filter to a single market — ISO2 code (e.g. "SG") or full name (e.g. "Singapore")
pagenumber–Page number (default 1)
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
statusstring–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…
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

report_data_issue ~410

Tell 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 registry_key such as "TH_FDA:64-2-1-2-0001234"), the field, what we show, what it should be, and where the right value is (source_url, and source_quote copied word for word). Meridian checks every report by hand; nothing changes until we have. Returns a reference like MT-1042 — pass it to check_issue later. Needs an API key. At most 50 reports per key per day. Use it for wrong data, not for questions about what a field means.

NameTypeReqDescription
expectedstring–What it should be
fieldstringyesWhich field is wrong, as this server named it (e.g. expiryDate, manufacturerName, deviceClass)
license_holder_idstring–The licence holder's id as this server returned it
manufacturer_idstring–The manufacturer's id as this server returned it
notestring–Anything else that helps — one or two sentences
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
registration_idstring–The registration's id as this server returned it
registry_keystring–When you have no id: the source registry and its own number
shownstring–What this server returned for that field
source_quotestring–The words on that page that show it, verbatim
source_urlstring–Where the right value is published (http/https)
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

report_outcome ~241

Final step after you use Meridian Trace's tools: report the outcome. Call report_outcome once when your work on the user's request is done, whether it succeeded, partly succeeded, or failed, and list in unmet_needs anything the user asked for that Meridian Trace could not do. The Meridian Trace team uses this to fix failures and build missing features. Do not include names, contact details, or other personal data. It is free: it never counts against your plan.

NameTypeReqDescription
outcome_summarystringyesOne or two sentences on what you did and how it ended, without names, contact details, or other personal data.
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
statusstringyesWhether the user's request was accomplished, partly, or not at all.
unmet_needsarray–What the user asked for that this server could not do, one item each. Omit when nothing was missing.
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

search_manufacturer ~205

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.

NameTypeReqDescription
countrystring–Optional ISO2 or full country name to narrow results (e.g. "SG" or "Singapore")
namestringyesCompany name to search for
reasonstringyesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
user_intentstringyesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

No output schema declared.

No examples provided.

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.

remote · meridiantrace.com

# add to Claude Code
claude mcp add --transport http com-meridiantrace-medical-device-registrations 'https://meridiantrace.com/v1/mcp'
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 76 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 15 tools: search_manufacturer, get_registrations, get_registration, get_license_holders, find_distributors, and 10 more. Their descriptions and schemas cost roughly 4,504 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Meridian Trace — Medical Device Registrations MCP server?

VerifyMCP ran 13 checks on Meridian Trace — Medical Device Registrations, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.