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.

Medius Docs

REMOTE · MEDIUS.K4TECH.NET · SCANNED SEP 20

Medius docs: the binary control protocol, device behavior, and the medius Rust library.

+1 this week 81 Trust /100
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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 225 tokens (~45/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (40% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Medius Docs MCP server?

Medius Docs is a hosted endpoint at https://medius.k4tech.net/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 · medius.k4tech.net

# add to Claude Code
claude mcp add --transport http net-k4tech-docs 'https://medius.k4tech.net/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "net-k4tech-docs": {
      "url": "https://medius.k4tech.net/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "net-k4tech-docs": {
      "type": "http",
      "url": "https://medius.k4tech.net/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.net-k4tech-docs]
url = "https://medius.k4tech.net/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-k4tech-docs": {
      "type": "remote",
      "url": "https://medius.k4tech.net/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add net-k4tech-docs --url 'https://medius.k4tech.net/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  net-k4tech-docs:
    url: "https://medius.k4tech.net/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "net-k4tech-docs": {
      "Transport": "http",
      "Url": "https://medius.k4tech.net/mcp"
    }
  }
}
# add to Vellum
assistant mcp add net-k4tech-docs -t streamable-http -u 'https://medius.k4tech.net/mcp'
// mcp.json
{
  "mcpServers": {
    "net-k4tech-docs": {
      "type": "http",
      "url": "https://medius.k4tech.net/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 17 Sept 26 +1
    • DNSSEC: fail → pass security
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 23 Aug 26 +1

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

  • 11 Aug 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
  • 6 Aug 26 0
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Schema quality: unverified → fail functional
    • Tool coverage: unverified → 100 functional
    • Schema quality: unverified → fair functional
    • Schema quality: unverified → pass functional
    • First check of Tool coverage: 40 functional
    • First check of Tool coverage: 100 functional
    • New tool “fetch” functional
    • New tool “get_page” functional
    • New tool “list_pages” functional
    • New tool “search” functional
    • New tool “search_docs” functional
  • 31 Jul 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
  • 30 Jul 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 20 Sept 2026 · Probed https://medius.k4tech.net/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=k4tech.net CN=WE1,O=Google Trust Services,C=US 20 Aug 2026 18 Nov 2026 ECDSA 256 ECDSA-SHA256 106dfaee16da09c4134b86296bac668b
SANs: k4tech.net, *.k4tech.net
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of medius.k4tech.net. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
k4tech.net. present 2371 13 Verified
medius.k4tech.net. Verified address RRset verified with the apex keys
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=86400

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://medius.k4tech.net/mcp Verified 200
http (plaintext) http://medius.k4tech.net/mcp HTTPS enforced 301 https://medius.k4tech.net/mcp
MCP tools · 5 exposed · ~225 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
fetch ~41

Fetch the full Markdown of one documentation page by its id (the id returned by search).

NameTypeReqDescription
idstringyesThe page id returned by search (its path).
NameTypeReqDescription
idstringyes
metadataobject
textstringyes
titlestringyes
urlstringyes

No examples provided.

get_page ~56

Return the full Markdown of one documentation page by its path, e.g. "/library/clip" or "/native/commands/inject".

NameTypeReqDescription
pathstringyesPage path, with or without a leading slash or .md suffix.

No output schema declared.

No examples provided.

list_pages ~30

List every Medius documentation page (path, title, section). Start here to see what the docs cover.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search ~39

Search the Medius documentation and return matching pages. Use the returned id with the fetch tool to read a page.

NameTypeReqDescription
querystringyesSearch terms.
NameTypeReqDescription
resultsarrayyes

No examples provided.

search_docs ~59

Full-text search the Medius docs. Returns ranked pages with a snippet; follow up with get_page for the full Markdown.

NameTypeReqDescription
limitnumberMaximum results (default 10, max 50).
querystringyesSearch terms.

No output schema declared.

No examples provided.

Common questions

What is the Medius Docs MCP server?

Medius Docs is an MCP server listed in the public MCP registry as net.k4tech/docs. Medius docs: the binary control protocol, device behavior, and the medius Rust library. This page covers its hosted endpoint (https://medius.k4tech.net/mcp).

Is the Medius Docs MCP server safe to use?

Medius Docs scores 81 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 Medius Docs MCP server expose?

Medius Docs exposes 5 tools: list_pages, get_page, search_docs, search, fetch. Their descriptions and schemas cost roughly 225 tokens of context every time the server is loaded.

Does the Medius Docs MCP server require authentication?

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

Is the Medius Docs MCP server still maintained?

Medius Docs is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.