Krate MCP server
tech.krate/kratekrate.techstreamable-httpv1.0.0Scanned
Make an app by asking. Krate builds and checks it, and its link opens in any browser, phones too.
8 tools: 2 change things and 6 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Krate MCP server can do
The Krate MCP server is published by krate.tech, a domain the MCP Registry verified. It has 8 tools. It can create or change data (2 tools: build_app and build_status), but cannot delete data. 6 tools only read.
1 tool reads private data (get_krate_guide); 2 tools bring in text other people can write (get_app and get_krate_guide).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 2Claude Code: ask
build_appBuilds 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Build and publish a Krate app
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
build_statusThe state of a Krate build, by its build id: still building, failed, or published.1 finding
Why it is in this group
- The name "build_status" says "status": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "build_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "build_status" says "status": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a Krate build
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 6Show 6 read-only tools
fetchOne 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.No findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Open a Krate result
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_appOne 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 li…Reads text others writeNo findings
Why it is in this group
- The name "get_app" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "browser": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get a Krate app
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_krate_guideKrate'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.to…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_krate_guide" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
- untrusted-inputThe description's first sentence says "browser": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read the Krate app guide
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_featuredThe 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.No findings
Why it is in this group
- The name "list_featured" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Featured Krate apps
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
searchSearches Krate's public apps and Krate's guide to making an app.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search Krate
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
search_appsSearch the public Krate gallery for apps by words.No findings
Why it is in this group
- The name "search_apps" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search Krate apps
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:20 UTC, unchanged since Nov 21, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://hub.krate.tech/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://hub.krate.tech
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://hub.krate.tech/mcp: tools/list returned 8 tools to an anonymous client, including build_app (write), build_status (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnbuild_status
The server marks "build_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "build_status" says "status": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http krate https://hub.krate.tech/mcpclaude mcp add --transport http krate https://hub.krate.tech/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__krate__search_apps",
"mcp__krate__get_app",
"mcp__krate__list_featured",
"mcp__krate__get_krate_guide",
"mcp__krate__search",
"mcp__krate__fetch"
],
"ask": [
"mcp__krate__build_app",
"mcp__krate__build_status"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as krate. Review it before you use it.
Capability tags behind 2 rules
- mcp__krate__get_app untrusted-input
- mcp__krate__get_krate_guide private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/tech.krate/krate/verify?hash=5e5b7207c1e0497114e4cb60ba654ffd63a4611fc3907382c068adfe3cfe688f" | jq -e '.changed == false'Pinned hash 5e5b7207c1e0, from Nov 21, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/tech.krate/krate/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/tech.krate/krate)Source: MCP Registry · repository. Synced Nov 21, 2026, 16:18 UTC.
Krate MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Krate MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Krate MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Krate MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Krate MCP server have?
- 8 tools: 2 write, 6 read. build_app, build_status, search_apps, get_app, list_featured, get_krate_guide, search and fetch.
Does the Krate MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Krate MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Krate MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.