com.meridiantrace/medical-device-registrations

MCPcommunautéen ligne
v1.0.0com.meridiantraceUnknownMis à jour il y a 1 mois

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

État de l’endpointen ligne
vérifié il y a 8 jours · 422 ms
100 % des dernières 5 vérifications ont atteint cet endpoint
Fonctionne dans
ClaudeCursorCopilotChatGPTGemini

Déduit des transports déclarés par cette annonce (streamable-http). Un client absent de cette liste n’est pas écarté pour autant — c’est simplement quelque chose que Forge ne peut pas confirmer.

Indexé automatiquement depuis des sources publiques. Pas encore vérifié par son développeur sur Forge.Revendiquer cette annonce →
il y a 1 moisDernière mise à jour
Paquet
Auteurcom.meridiantrace
LicenceUnknown
Version1.0.0
Sourcemcp-registry
Statut de confiance
B
60/100Bon
Endpoint hébergé uniquement : cette évaluation porte sur qui le publie et s’il répond, pas sur le code qui tourne derrière. Aucune analyse de CVE, de dépendances ou de code source ne s’applique ; rien ici ne garantit donc que ce code est sain.
✓Listé dans l’index Forge+10/10
—Identité de l’éditeur vérifiée+0/30
→ Éditeur : aucune référence de dépôt n’est enregistrée pour cette annonce, `forge publish` ne peut donc pas vérifier la propriété automatiquement. Utilisez « Revendiquer cette annonce » ci-dessus — Forge les examine à la main.
—Vérification de domaine+0/10
→ Actuellement indisponible pour ce type d’annonce — la vérification de domaine ne s’exécute aujourd’hui que pour les paquets adossés à npm, cette ligne ne peut donc pas encore être obtenue ici, quel que soit le contenu hébergé sur le domaine.
✓Analyse d’injection de prompt · propre+30/30
✓Analyse d’obfuscation / exfiltration · propre+20/20
StatutIndexé par la communauté
ÉditeurNon vérifié
SignatureNon signé
Domaine—
Provenance—
DépendancesNon audité
Surface d’outils12 outils · aucun privilégié
Analyse de sécurité✓ Proprevlive · il y a 8 jQuelle est l’efficacité de cette analyse ?
ÉvaluationsAucune
Indexé25 août 2026

La vérification confirme l’identité de l’éditeur (la propriété du dépôt), pas la sûreté du code. L’analyse de sécurité couvre les CVE connues et les scripts d’installation suspects.

Outils

12 outils · aucun privilégié
Observé en direct depuis l’endpoint du fournisseur8d ago

Lu depuis un véritable échange MCP initialize → tools/list contre l’endpoint déclaré. Aucun outil n’a été invoqué — tools/list est l’appel d’introspection en lecture seule que le protocole prévoit pour cela. Cela reflète ce que le serveur annonçait à cet instant ; un endpoint hébergé n’est figé sur aucune version et peut changer sans préavis.

  • https://meridiantrace.com/v1/mcp12 outils · 422 ms
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 wit…

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 wit…

ParamètreTypeDescription
name*stringCompany name to search for
countrystringOptional ISO2 or full country name to narrow results (e.g. "SG" or "Singapore")
get_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") rathe…

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") rathe…

ParamètreTypeDescription
manufacturer_id*string—
marketstringFilter to a single market — ISO2 code (e.g. "SG") or full name (e.g. "Singapore")
statusstringFilter by lifecycle state: "active", "expired", "cancelled" or "pending". These are applied as RULES, not string matching — a market that publishes no status (…
pagenumberPage number (default 1)
limitnumberResults per page (default 50, max 200)
get_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,…

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,…

ParamètreTypeDescription
registration_id*stringRegistration id from get_registrations, find_similar_devices or get_recent_registrations.
get_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…

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…

ParamètreTypeDescription
manufacturer_id*string—
find_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 a…

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 a…

ParamètreTypeDescription
market*stringISO2 code or market name, e.g. "TH" or "Thailand". One market per call.
device_typestringOptional clinical area or device category in plain words, e.g. "orthopaedic implants", "in vitro diagnostics", "cardiology". Partial matches count. Omit it to…
limitnumber1-25 (default 10). Capped to 3 without a paid key.
get_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…

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…

ParamètreTypeDescription
manufacturer_idstringThe Meridian Trace manufacturer _id, from search_manufacturer
namestringCompany name, as an alternative to manufacturer_id. Resolves the same way search_manufacturer does and uses the best match.
tickerstringListed 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 out…
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 U…

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 U…

ParamètreTypeDescription
manufacturer_idstringFrom search_manufacturer
namestringCompany name, as an alternative to manufacturer_id
tickerstringListed ticker, e.g. "SYK" (US-listed coverage)
from_yearnumberFirst year to include (default: 10 years ago)
to_yearnumberLast year to include (default: current year)
marketstringRestrict to one market (ISO2 or full name)
find_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 o…

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 o…

ParamètreTypeDescription
k_numberstringA 510(k) number, e.g. "K191275"
product_codestringAn FDA product code, e.g. "LIT"
limitnumberMax rows per list (default 20, max 50)
classify_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 pu…

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 pu…

ParamètreTypeDescription
gmdn_codestringGMDN code, e.g. "44727"
device_typestringA 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…
fda_product_codestringFDA product code, e.g. "DZE"
find_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. Use…

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…

ParamètreTypeDescription
registration_idstringThe _id of a registration, from get_registrations
device_namestringA product name, as an alternative to registration_id — the closest registration is used as the reference device
marketstringWith device_name, restrict the reference lookup to one market (ISO2)
limitnumberMax results (default 15)
get_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: t…

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: t…

ParamètreTypeDescription
daysnumberLook-back window, 1-180 (default 30)
marketsarrayISO2 codes, e.g. ["TH","ID"]
risk_levelstringLow | Medium | High
device_typestringResolved GMDN device type
limitnumberMax results (default 50, max 100)
get_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 crawled. Call this to verify coverage and freshness for yourself…

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…

Aucun schéma d’entrée n’a été publié pour cet outil.

12 outils sur 12 ont publié une description.

Les noms et descriptions d’outils sont écrits par l’éditeur et affichés tels quels, comme du texte inerte. Ce sont les chaînes qu’un client MCP transmet à un modèle, alors Forge y recherche des motifs d’injection de prompt — tout constat apparaît avec l’analyse de sécurité ci-dessus. « Privilégié » est une correspondance de mot-clé sur le nom de l’outil, pas un audit de ce qu’il fait : un nom anodin peut tout de même tout faire.

À propos

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

Mots-clés
mcp
Alternatives
Comparaison des surfaces d’outils…

Aucune couverture des dépendances

Cette entrée ne publie aucun paquet npm : Forge n'a donc pas d'arbre de dépendances pour elle. C'est une lacune de couverture — pas une affirmation qu'elle n'a aucune dépendance.

Thèmes

Apparentés dans health & fitness