{"attribution":"MCP Queen — the evidence layer for MCP (https://mcpqueen.com)","license":"CC BY 4.0 — free to use with attribution and a link to mcpqueen.com","methodology":"https://mcpqueen.com/registry#methodology","docs":"https://mcpqueen.com/api","generated_at":"2026-10-06T14:41:49.439Z","server":{"name":"com.meridiantrace/medical-device-registrations","title":"Meridian Trace — Medical Device Registrations","description":"Medical device registrations across 25 markets: coverage gaps, 510(k) predicates, classification","version":"1.0.0","remote_url":"https://meridiantrace.com/v1/mcp","repo_url":null},"operational_grade":{"grade":"A","score":97,"provisional":0,"reachable":1,"auth_state":"open","latency_ms":334,"tool_count":12,"probed_at":"2026-09-28T03:30:27.766Z","evidence":[{"criterion":"reachability","points":25,"max":25,"evidence":"HTTP 200, initialize accepted in 334ms"},{"criterion":"protocol","points":15,"max":15,"evidence":"valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo meridian-trace-medical-devices@1.0.0"},{"criterion":"tooling","points":35,"max":35,"evidence":"tools/list OK: 12 tools e.g. \"search_manufacturer\"; 12/12 described, 12/12 fully-typed schemas, median description 581 chars"},{"criterion":"latency","points":10,"max":10,"evidence":"initialize round-trip 334ms"},{"criterion":"provenance","points":12,"max":15,"evidence":"description present; no repository URL; version 1.0.0; namespace com.meridiantrace matches endpoint/repo"}],"protocol_access":"open"},"field_semantics":{"auth_state":"Deprecated name retained for compatibility. It means protocol handshake/discovery access only, not tool-level data entitlement.","protocol_access":"Preferred name for auth_state."},"audit_state":"observations_published","observations":[{"dimension":"citation_quality","metric":"citation_capability_advertised","status":"unverified","value_text":null,"evidence":"Metadata/tool descriptions advertise citation or evidence capability: find_predicates US 510(k) predicate lineage, from the predicates actually cited in each clearance's own summary document — not a similarity guess | 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. No response-level citation benchmark has verified this claim yet.","source_type":"live_probe","sample_size":null,"observed_at":"2026-09-28T03:30:27.766Z","methodology_version":"trust-v1"},{"dimension":"security","metric":"authentication_boundary","status":"observed","value_text":"open","evidence":"Live protocol probe observed auth_state=open. This describes discovery/access behavior; it is not by itself a vulnerability finding.","source_type":"live_probe","sample_size":null,"observed_at":"2026-09-28T03:30:27.766Z","methodology_version":"trust-v1"}],"response_benchmarks":[],"reviewed_field_reports":[],"interpretation":"Dimensions are independent; missing evidence is not a pass; field reports are qualitative, moderated and never votes."}