KarmaDue MCP server
io.github.ashadow07/karmadueashadow07streamable-httpv1.1.3Scanned
Pre-install safety check for agents: known traps, tested fixes, malware reports. No account.
5 tools: 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 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 KarmaDue MCP server can do
The KarmaDue MCP server is published by the GitHub account ashadow07. It has 5 tools. It can create or change data (3 tools: check_install, search_recipes and report_leaf), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 3 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 1.1.3.
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.
5 tools
Changes things 3Claude Code: ask
check_installRead-only.2 findings
Why it is in this group
- The name "check_install" says "install": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...e, tools/list; never a tool call, never credentials) and KarmaDue keeps hashes of that serv..."
- Warn
The server marks "check_install" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "check_install" says "install": a word for a change.
Description, as the server wrote it Read-only. Call before npm/pnpm/yarn install, pip install, uv add, npx or uvx, or adding an MCP server, including setup commands from a README or tutorial. Returns v, enforce, why; on known traps fix (tested steps), do_not (what failed, where), test, source. enforce=block: stop. enforce=ask: ask your person first. v=fix_first: use fix, not your command. Also returns safety (OSV advisories and malicious-package reports: verdict, advisories, fixed_in). When no tested record exists, repro_request says how to queue one with request_repro 'yes' (the only case where this call records anything about you: one anonymous request). A remote MCP URL is probed read-only (server/discover or initialize, tools/list; never a tool call, never credentials) and KarmaDue keeps hashes of that server's public tool definitions to report later changes. Every successful answer has checked_at. Missing evidence is not safety clearance. Skip packages already pinned in a lockfile you are not changing.
Annotations the server declares
- readOnlyHint: true
report_leafOnly if your owner opted in: after an install finishes, report pass or fail and the command.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 Only if your owner opted in: after an install finishes, report pass or fail and the command. Reviewed before use.
Annotations the server declares
- readOnlyHint: false
search_recipesCall when an install, build or import fails, before retrying or guessing a fix.1 finding
Why it is in this group
- The name "search_recipes" says "search": a word for reading.
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "search_recipes" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "search_recipes" says "search": a word for reading.
Description, as the server wrote it Call when an install, build or import fails, before retrying or guessing a fix. Paste the key error line; returns tested fixes.
Annotations the server declares
- readOnlyHint: true
Only reads 2Show 2 read-only tools
fetchFetch one record by id from search.No findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
Description, as the server wrote it Fetch one record by id from search.
Annotations the server declares
- readOnlyHint: true
searchSearch PinTree records for packages, tools and MCP servers.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it Search PinTree records for packages, tools and MCP servers.
Annotations the server declares
- readOnlyHint: true
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 private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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 20, 2026, 19:02 UTC, unchanged since Oct 22, 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
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://karmadue--mcp.expo.app/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://karmadue.expo.app
- 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 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://karmadue--mcp.expo.app/mcp: tools/list returned 5 tools to an anonymous client, including check_install (write), search_recipes (write), report_leaf (write)
Findings
Matches of fixed checks, with the text they matched.
- Warncheck_install
The server marks "check_install" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "check_install" says "install": a word for a change.
- Warnsearch_recipes
The server marks "search_recipes" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "search_recipes" says "search": a word for reading.
- Infocheck_install
The description mentions "credentials".
What this check looks forMatched text
description: "...e, tools/list; never a tool call, never credentials) and KarmaDue keeps hashes of that serv..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:check_installChanges thingsdescriptioninputSchema
Install
Pinned to version 1.1.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http karmadue https://karmadue--mcp.expo.app/mcpclaude mcp add --transport http karmadue https://karmadue--mcp.expo.app/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__karmadue__search",
"mcp__karmadue__fetch"
],
"ask": [
"mcp__karmadue__check_install",
"mcp__karmadue__search_recipes",
"mcp__karmadue__report_leaf"
],
"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 karmadue. Review it before you use it.
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/io.github.ashadow07/karmadue/verify?hash=8904dc2ca4f6de22f7fca800a723a8cff415252186aa0a28797dc24a0cd116b5" | jq -e '.changed == false'Pinned hash 8904dc2ca4f6, from Nov 16, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.ashadow07/karmadue/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ashadow07/karmadue)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:23 UTC.
KarmaDue MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the KarmaDue MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the KarmaDue MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the KarmaDue 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 KarmaDue MCP server have?
- 5 tools: 3 write, 2 read. check_install, search_recipes, report_leaf, search and fetch.
Does the KarmaDue MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the KarmaDue MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the KarmaDue MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.