# Krate (remote · hub.krate.tech)

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

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `hub.krate.tech`: 66/100 (this document), [markdown](https://verifymcp.io/servers/tech-krate-krate/hub.md), [page](https://verifymcp.io/servers/tech-krate-krate/hub)

## Channel facts

- Endpoint: `https://hub.krate.tech/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## 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.

### Claude

```bash
claude mcp add --transport http tech-krate-krate 'https://hub.krate.tech/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-krate-krate": {
      "url": "https://hub.krate.tech/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-krate-krate": {
      "type": "http",
      "url": "https://hub.krate.tech/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-krate-krate]
url = "https://hub.krate.tech/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-krate-krate": {
      "type": "remote",
      "url": "https://hub.krate.tech/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-krate-krate --url 'https://hub.krate.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-krate-krate:
    url: "https://hub.krate.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-krate-krate": {
      "Transport": "http",
      "Url": "https://hub.krate.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-krate-krate -t streamable-http -u 'https://hub.krate.tech/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tech-krate-krate": {
      "type": "http",
      "url": "https://hub.krate.tech/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 66)

First indexed and scored.

## MCP tools (8)

### `search_apps` (~135 tokens)

Search Krate apps

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.

Input parameters:

- `category` (string): Only apps on this shelf
- `limit` (integer): How many results, at most 20 (default 10)
- `query` (string, required): Words to look for, e.g. "markdown editor"

Output parameters:

- `category` (string|null)
- `query` (string)
- `results` (array)

### `get_app` (~125 tokens)

Get a Krate app

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.

Input parameters:

- `id_or_link` (string, required): A Krate app link, or its id

Output parameters:

- `app` (object)
- `found` (boolean)
- `message` (string)
- `notice` (string): The removal notice, when removed
- `removed` (boolean): The app was taken down from the registry

### `list_featured` (~50 tokens)

Featured Krate apps

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.

Output parameters:

- `newest` (array)
- `newest_label` (string)
- `start_here` (array)

### `get_krate_guide` (~89 tokens)

Read the Krate app guide

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.

Output parameters:

- `characters` (integer): The guide's length; the guide itself is the text content
- `next` (string)

### `search` (~62 tokens)

Search Krate

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.

Input parameters:

- `query` (string, required): Words to look for, e.g. "markdown editor"

Output parameters:

- `results` (array)

### `fetch` (~66 tokens)

Open a Krate result

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.

Input parameters:

- `id` (string, required): A result's id, an app's link, or krate-guide

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

### `build_app` (~218 tokens)

Build and publish a Krate app

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.

Input parameters:

- `files` (array, required): Every file of the app, with paths relative to the app folder
- `name` (string, required): The app's name, as a person would say it

Output parameters:

- `app_id` (string)
- `browser_link` (string): Opens the app in a browser on any device, nothing to install
- `build_id` (string)
- `detail` (string): What went wrong, in the check's own words
- `fix` (string): How to fix it, in the check's own words
- `link` (string): The app's own link; it opens the newest version
- `message` (string)
- `name` (string)
- `stage` (string): Where Krate's check stopped, on a failure
- `status` (string)

### `build_status` (~106 tokens)

Check a Krate build

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.

Input parameters:

- `build_id` (string, required): The build id a build answered with

Output parameters:

- `app_id` (string)
- `browser_link` (string): Opens the app in a browser on any device, nothing to install
- `build_id` (string)
- `detail` (string): What went wrong, in the check's own words
- `fix` (string): How to fix it, in the check's own words
- `link` (string): The app's own link; it opens the newest version
- `message` (string)
- `name` (string)
- `stage` (string): Where Krate's check stopped, on a failure
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-krate-krate/hub#diagnostics

## Score history

- 2026-11-21: 66

## 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.

## Links

- Remote endpoint: https://hub.krate.tech/mcp
- Repository: https://github.com/incyashraj/krate
- Website: https://krate.tech/docs/pages/make-an-app-with-claude.html
- Changelog RSS feed: https://verifymcp.io/servers/tech-krate-krate/hub.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-krate-krate/hub/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tech-krate-krate/hub.json
- HTML version of this page: https://verifymcp.io/servers/tech-krate-krate/hub
