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.

ProbeLine

REMOTE · PROBELINE.IO

Perio diagnosis and risk, ICD-10-CM, peri-implant status, sourced implant specs. Paid via x402.

Available components

+2 this week 71 Trust /100

Last scanned (19 hours ago)

Scores higher than 56% 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 Security74
  • 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
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 1283 tokens (~142/item across 9 items; 9 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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 42% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 128 → 142 ▼ functional
    • Tool coverage: 37% → 42% ▲ functional
    • Server version: 1.0.0 → 1.1.0 functional
    • New tool “assess_peri_implant” functional
    • New tool “assess_periodontal_risk” functional
    • New tool “get_component_compatibility” functional
    • New tool “implant_complications_reference” functional
    • New tool “lookup_icd10” functional
  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 67

    First indexed and scored.

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://probeline.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=probeline.io CN=YR2,O=Let's Encrypt,C=US 9 Nov 2026 7 Feb 2027 RSA 2048 SHA256-RSA 5b344b42c77607054759cd1fc001ec38532
SANs: probeline.io
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of probeline.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
probeline.io. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://probeline.io/mcp Verified 200
http (plaintext) http://probeline.io/mcp HTTPS enforced 301 https://probeline.io/mcp
MCP tools · 9 exposed · ~1,212 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
assess_peri_implant ~175

Peri-implant status (health / mucositis / peri-implantitis) from clinical findings using 2017 World Workshop case definitions, with severity grade, ICD-10-CM suggestion and each criterion shown. Costs $0.15 USDC per call (x402, Base).

NameTypeReqDescription
baseline_pd_mmnumber–PD after prosthesis delivery, if known
bone_level_mmnumber–Radiographic bone level apical to the most coronal intraosseous part (no-baseline pathway)
bone_loss_since_baseline_mmnumber–Bone loss vs baseline radiograph, if known
bopboolean–Bleeding on gentle probing
implant_length_mmnumber––
max_pd_mmnumber––
suppurationboolean––

No output schema declared.

No examples provided.

assess_periodontal_risk ~176

Periodontal risk assessment (Lang & Tonetti PRA): six vectors banded low/moderate/high, patient risk with the rule applied, suggested maintenance interval, and tooth-level adverse prognostic factors. Costs $0.15 USDC per call (x402, Base).

NameTypeReqDescription
agenumber––
bone_loss_pctnumber–Worst-site radiographic bone loss, % of root length
bop_percentnumber–% of sites bleeding on probing
sites_pd_5_plusinteger–Number of sites with PD >= 5 mm
smokingobject––
systemicobject––
teetharray–Optional tooth-level findings for prognostic factor flags
teeth_lostinteger–Teeth lost of 28 (excluding third molars)

No output schema declared.

No examples provided.

diagnose_periodontitis ~160

Periodontal diagnosis from a de-identified 6-point chart: 2017 AAP/EFP stage, extent, grade, ICD-10-CM suggestions, rationale and documentation checklist. Clinical decision support for licensed dental professionals. Send no patient identifiers. Costs $0.25 USDC per call (x402, Base).

NameTypeReqDescription
chartarrayyesOne entry per present tooth
complexityobject––
longitudinalobject––
patientobject–Risk factors only. Never send names, DOB, record numbers or dates of service.
phenotypestring––
remaining_teethinteger–Defaults to number of teeth charted
teeth_lost_to_periointeger––

No output schema declared.

No examples provided.

get_component_compatibility ~91

Component compatibility for an implant system: its own abutment screw / multi-unit torques and driver, manufacturer-declared cross-system compatibility with sources, and similar interfaces flagged unverified. Costs $0.10 USDC per call (x402, Base).

NameTypeReqDescription
idstringyesImplant id from search_implants
platformstring–Platform name, e.g. 'NP'

No output schema declared.

No examples provided.

get_implant ~87

Full spec for one dental implant system: connection, platforms, diameters, lengths, abutment screw torque, multi-unit torque, driver, with a source URL for each value. Unknown values are null. Costs $0.05 USDC per call (x402, Base).

NameTypeReqDescription
idstringyesImplant id from search_implants, e.g. 'straumann-bl'

No output schema declared.

No examples provided.

identify_implant ~135

Rank likely dental implant systems from observed features (connection type, platform/body diameter, body shape, bone/tissue level), with reasons for each candidate. Costs $0.10 USDC per call (x402, Base).

NameTypeReqDescription
body_diameter_mmnumber––
body_shapestring––
connection_typestring–e.g. 'internal hex', 'external hex', 'conical', 'morse taper', 'tri-channel'
levelstring––
limitinteger––
manufacturer_hintstring––
platform_diameter_mmnumber––

No output schema declared.

No examples provided.

implant_complications_reference ~66

Definitions, key findings, ICD-10-CM codes and checks for dental implant complications (mucositis, peri-implantitis, early failure, screw loosening/fracture, implant fracture). Free.

NameTypeReqDescription
categorystring––
idstring––

No output schema declared.

No examples provided.

lookup_icd10 ~237

ICD-10-CM lookup for periodontal and dental implant conditions by code, free text, or structured condition (e.g. periodontitis Stage III generalized -> K05.323). Public-domain code set; no CDT. Costs $0.05 USDC per call (x402, Base).

NameTypeReqDescription
acuteboolean––
codestring–Exact ICD-10-CM code, e.g. 'K05.323'
completeboolean–tooth_loss_periodontal: complete (edentulous) vs partial
conditionstring–Structured mapping; combine with the qualifiers below
diabetes_typeinteger––
extentstring––
failure_typestring––
kennedy_classstring––
limitinteger––
molar_incisor_patternboolean––
non_plaque_inducedboolean––
qstring–Free text, e.g. 'generalized severe periodontitis' or 'peri-implantitis'
severitystring––
stagestring––

No output schema declared.

No examples provided.

search_implants ~85

List or search the dental implant database (manufacturer, line, connection, platforms, status). Free. Returns ids for get_implant.

NameTypeReqDescription
connectionstring––
manufacturerstring––
qstring–Free-text search, e.g. 'nobel active'
statusstring–e.g. 'current' or 'discontinued'

No output schema declared.

No examples provided.

Install

How do I install the ProbeLine MCP server?

ProbeLine is a hosted endpoint at https://probeline.io/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 · probeline.io

# add to Claude Code
claude mcp add --transport http ryankaye212-tech-probeline 'https://probeline.io/mcp'
Common questions

What is the ProbeLine MCP server?

ProbeLine is an MCP server listed in the public MCP registry as io.github.ryankaye212-tech/probeline. Perio diagnosis and risk, ICD-10-CM, peri-implant status, sourced implant specs. Paid via x402. This page covers its hosted endpoint (https://probeline.io/mcp).

Is the ProbeLine MCP server safe to use?

ProbeLine scores 71 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 ProbeLine MCP server expose?

ProbeLine exposes 9 tools: search_implants, implant_complications_reference, diagnose_periodontitis, get_implant, identify_implant, and 4 more. Their descriptions and schemas cost roughly 1,212 tokens of context every time the server is loaded.

Does the ProbeLine MCP server require authentication?

No. We connected to ProbeLine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ProbeLine MCP server still maintained?

ProbeLine 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 ProbeLine MCP server?

VerifyMCP ran 13 checks on ProbeLine, 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.