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.

pracht docs

REMOTE · PRACHT.RESYNAPSE.DEV

Search and read the pracht framework documentation: guides, recipes, and API reference.

+4 this week 76 Trust /100

Last scanned (15 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

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 Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 320 tokens (~106/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 (100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

  • 21 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.

  • 19 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

    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.

  • 15 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.

  • 13 Nov 26 +1

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

  • 12 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 71

    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://pracht.resynapse.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=resynapse.dev CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 37c5963f7e05549213f5ab0fefe57576
SANs: resynapse.dev, pracht.resynapse.dev, *.pracht.resynapse.dev
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 insecure

Validation of pracht.resynapse.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
resynapse.dev. 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
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pracht.resynapse.dev/mcp Verified 200
http (plaintext) http://pracht.resynapse.dev/mcp HTTPS enforced 301 https://pracht.resynapse.dev/mcp
MCP tools · 3 exposed · ~282 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
docs_list ~38

The table of contents of the pracht documentation: every page with its path, title, URL, and one-line summary, grouped like the site navigation.

Input schema present but exposes no named parameters.

NameTypeReqDescription
groupsarrayyes–

No examples provided.

docs_read ~139

Return one page of the pracht documentation as Markdown, or only one section of it. `page` accepts a path (/docs/capabilities), a slug (capabilities, recipes/auth), or a page URL. A whole-page read lists the page's anchors in `sections`. An unknown page or section answers found: false with the closest matches.

NameTypeReqDescription
pagestringyesPage path, slug, or URL, e.g. /docs/capabilities.
sectionstring–Heading anchor from docs_search or `sections`, e.g. remote-mcp-tools-for-agents-without-a-browser. Empty or omitted reads the whole page.
NameTypeReqDescription
foundbooleanyes–
markdownstringyes–
messagestringyes–
pagestringyes–
sectionstringyes–
sectionsarrayyes–
suggestionsarrayyes–
titlestringyes–
truncatedbooleanyes–
urlstringyes–

No examples provided.

docs_search ~105

Full-text search over the pracht framework documentation at https://pracht.resynapse.dev. Returns the best-matching page sections, each with its page path, section anchor, URL, and a snippet. Pass a result's `page` and `section` to docs_read for the full text.

NameTypeReqDescription
limitinteger–Maximum number of results.
querystringyesWords to look for, e.g. `remote mcp oauth` or `defineApp agents`.
NameTypeReqDescription
messagestringyesWhy there are no results, when there are none; otherwise empty.
resultsarrayyes–

No examples provided.

Install

How do I install the pracht docs MCP server?

pracht docs is a hosted endpoint at https://pracht.resynapse.dev/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 · pracht.resynapse.dev

# add to Claude Code
claude mcp add --transport http jovidecroock-pracht-docs 'https://pracht.resynapse.dev/mcp'
Common questions

What is the pracht docs MCP server?

pracht docs is an MCP server listed in the public MCP registry as io.github.JoviDeCroock/pracht-docs. Search and read the pracht framework documentation: guides, recipes, and API reference. This page covers its hosted endpoint (https://pracht.resynapse.dev/mcp).

Is the pracht docs MCP server safe to use?

pracht docs 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 pracht docs MCP server expose?

pracht docs exposes 3 tools: docs_search, docs_read, docs_list. Their descriptions and schemas cost roughly 282 tokens of context every time the server is loaded.

Does the pracht docs MCP server require authentication?

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

Is the pracht docs MCP server still maintained?

pracht docs 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 pracht docs MCP server?

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