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.

Krate

REMOTE · HUB.KRATE.TECH

Make an app by asking. Krate builds and checks it, and its link opens in any browser, phones too.

Available components

66 Trust /100

Last scanned (6 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

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 Security63
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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 Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1081 tokens (~135/item across 8 items; 8 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (11)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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 66

    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://hub.krate.tech/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=krate.tech CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 3c8f1e0c89ec5c040ed34ecaf236eb5c
SANs: krate.tech, hub.krate.tech, *.hub.krate.tech
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 hub.krate.tech. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
tech. DS published 2185 13 Verified
krate.tech. 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://hub.krate.tech/mcp Verified 200
http (plaintext) http://hub.krate.tech/mcp Inconclusive 405
MCP tools · 8 exposed · ~851 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
build_app ~218

Builds a real app the person keeps: one small file that runs natively on Windows, macOS and Linux and opens from a link in any browser, phones included. A Krate app keeps its own data on the device and works offline; with the person's permission it can print to a printer they pick with no print dialog, talk to serial and USB devices, read and write Excel files, serve other devices on the local network, and use the camera, microphone and location. Compiles the app's files (Cargo.toml, src/lib.rs, manifest.toml and any assets), checks it uses only Krate's API and runs it once, then publishes it unlisted to the signed-in person's Krate account with its link. Answers a build id at once; a build takes a few minutes. Needs the person to sign in to Krate.

NameTypeReqDescription
filesarrayyesEvery file of the app, with paths relative to the app folder
namestringyesThe app's name, as a person would say it
NameTypeReqDescription
app_idstring––
browser_linkstring–Opens the app in a browser on any device, nothing to install
build_idstringyes–
detailstring–What went wrong, in the check's own words
fixstring–How to fix it, in the check's own words
linkstring–The app's own link; it opens the newest version
messagestringyes–
namestring––
stagestring–Where Krate's check stopped, on a failure
statusstringyes–

No examples provided.

build_status ~106

The state of a Krate build, by its build id: still building, failed, or published. A failed build's answer has Krate's check in its own words: the stage, what went wrong and how to fix it. A published build's answer has the app's link and a browser link that opens it on any device, nothing to install. Needs the person to sign in to Krate.

NameTypeReqDescription
build_idstringyesThe build id a build answered with
NameTypeReqDescription
app_idstring––
browser_linkstring–Opens the app in a browser on any device, nothing to install
build_idstringyes–
detailstring–What went wrong, in the check's own words
fixstring–How to fix it, in the check's own words
linkstring–The app's own link; it opens the newest version
messagestringyes–
namestring––
stagestring–Where Krate's check stopped, on a failure
statusstringyes–

No examples provided.

fetch ~66

One Krate app or Krate's guide in full, by the id a result carries: an app's details and permissions in plain words, or the whole guide to making an app.

NameTypeReqDescription
idstringyesA result's id, an app's link, or krate-guide
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_app ~125

One public Krate app's details, from its link or id: what it does, what it is allowed to do in plain words, its versions, size, publisher and signature, its link and its browser link. Accepts a hub link (https://hub.krate.tech/a/..., /run/...), the app's own id (v followed by 11 hex characters), a short id, or a full hash. An app removed from the registry answers with its removal notice only.

NameTypeReqDescription
id_or_linkstringyesA Krate app link, or its id
NameTypeReqDescription
appobject––
foundbooleanyes–
messagestring––
noticestring–The removal notice, when removed
removedbooleanyesThe app was taken down from the registry

No examples provided.

get_krate_guide ~89

Krate's reference for writing a Krate app (a native app for Windows, macOS and Linux that also opens in a browser): the files an app is made of (Cargo.toml, src/lib.rs, manifest.toml), the API it may use, the permissions it may declare, the mistakes that fail a first build, and worked examples. No sign-in needed.

Input schema present but exposes no named parameters.

NameTypeReqDescription
charactersintegeryesThe guide's length; the guide itself is the text content
nextstringyes–

No examples provided.

list_featured ~50

The Krate gallery's front shelves: the apps picked to start with, and the newest apps, each with its link, what it is allowed to do in plain words, its size and its publisher.

Input schema present but exposes no named parameters.

NameTypeReqDescription
newestarrayyes–
newest_labelstringyes–
start_herearrayyes–

No examples provided.

search ~62

Searches Krate's public apps and Krate's guide to making an app. Each result has an id, a title and a link; the guide's id is krate-guide.

NameTypeReqDescription
querystringyesWords to look for, e.g. "markdown editor"
NameTypeReqDescription
resultsarrayyes–

No examples provided.

search_apps ~135

Search the public Krate gallery for apps by words. Results are ranked by how well the words match the app's name, then its description and publisher. Each result has the app's link (opens in Krate), a link that opens it in a browser tab, what it is allowed to do in plain words, its size, and whether its publisher is verified and the app signed.

NameTypeReqDescription
categorystring–Only apps on this shelf
limitinteger–How many results, at most 20 (default 10)
querystringyesWords to look for, e.g. "markdown editor"
NameTypeReqDescription
categorystring|nullyes–
querystringyes–
resultsarrayyes–

No examples provided.

Install

How do I install the Krate MCP server?

Krate is a hosted endpoint at https://hub.krate.tech/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 · hub.krate.tech

# add to Claude Code
claude mcp add --transport http tech-krate-krate 'https://hub.krate.tech/mcp'
Common questions

What is the Krate MCP server?

Krate is an MCP server listed in the public MCP registry as tech.krate/krate. Make an app by asking. Krate builds and checks it, and its link opens in any browser, phones too. This page covers its hosted endpoint (https://hub.krate.tech/mcp).

Is the Krate MCP server safe to use?

Krate scores 66 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 Krate MCP server expose?

Krate exposes 8 tools: search_apps, get_app, list_featured, get_krate_guide, search, and 3 more. Their descriptions and schemas cost roughly 851 tokens of context every time the server is loaded.

Does the Krate MCP server require authentication?

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

Is the Krate MCP server still maintained?

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

VerifyMCP ran 11 checks on Krate, covering TLS certificate, Authorization, HSTS header, DNSSEC and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Krate: HTTPS and Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.