io.github.cdonoyan/shuka
NPM · @SHUKASHAKE/MCP · SCANNED SEP 20
Universal trust attestation for AI agents. Create, verify, and negotiate trust proofs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 213 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 474 tokens (~118/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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
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
How do I install the io.github.cdonoyan/shuka MCP server?
io.github.cdonoyan/shuka runs locally as an npm package, launched with npx -y @shukashake/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @shukashake/mcp
claude mcp add cdonoyan-shuka -- npx -y @shukashake/mcp
{
"mcpServers": {
"cdonoyan-shuka": {
"command": "npx",
"args": [
"-y",
"@shukashake/mcp"
]
}
}
} {
"servers": {
"cdonoyan-shuka": {
"command": "npx",
"args": [
"-y",
"@shukashake/mcp"
]
}
}
} codex mcp add cdonoyan-shuka -- npx -y @shukashake/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cdonoyan-shuka": {
"type": "local",
"command": [
"npx",
"-y",
"@shukashake/mcp"
],
"enabled": true
}
}
} openclaw mcp add cdonoyan-shuka --command npx --arg -y --arg @shukashake/mcp
mcp_servers:
cdonoyan-shuka:
command: "npx"
args: ["-y", "@shukashake/mcp"] {
"McpServers": {
"cdonoyan-shuka": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@shukashake/mcp"
]
}
}
} assistant mcp add cdonoyan-shuka -t stdio -c npx -a -y @shukashake/mcp
{
"mcpServers": {
"cdonoyan-shuka": {
"command": "npx",
"args": [
"-y",
"@shukashake/mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/@shukashake/mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_attestation ~162
Create a verifiable Shuka attestation for any claim or data. Use this when you need to: - Prove a claim is true with cryptographic certainty - Create an audit trail for data being shared - Attest to compliance, consent, or authorization - Generate a portable proof that other agents can verify Returns a proof token (shk_v1.xxx.yyy) that anyone can verify.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What you are attesting to. Be specific and clear. |
| industry | string | – | The industry context for this attestation |
| jurisdiction | string | – | The legal jurisdiction (e.g., 'US', 'UK', 'EU') |
| metadata | object | – | Additional structured metadata to include in the attestation |
No output schema declared.
No examples provided.
negotiate_trust ~146
Perform agent-to-agent trust negotiation with Shuka as the arbiter. Use this when: - Another agent presents a proof and you need Shuka to vouch for it - You need a recommendation on whether to proceed with a data exchange - You want detailed validation evidence before trusting external data Returns a recommendation: safe_to_proceed, proceed_with_caution, additional_verification_recommended, or do_not_proceed.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Your agent identifier (optional, for audit trail) |
| proof_token | string | yes | The proof token to verify |
| purpose | string | – | Why you need to verify this (provides context for the trust decision) |
No output schema declared.
No examples provided.
verify_proof ~124
Verify a Shuka proof token and get details about the attestation. Use this when you: - Receive a proof token and need to confirm it's valid - Want to check the trust score before proceeding - Need to see what was attested and when - Want to verify claims before acting on data Proof tokens look like: shk_v1.YWJjMTIz.a1b2c3 or ENV-xxx
| Name | Type | Req | Description |
|---|---|---|---|
| proof_token | string | yes | The Shuka proof token to verify (shk_v1.xxx.yyy or ENV-xxx format) |
No output schema declared.
No examples provided.
What is the io.github.cdonoyan/shuka MCP server?
io.github.cdonoyan/shuka is an MCP server listed in the public MCP registry as io.github.cdonoyan/shuka. Universal trust attestation for AI agents. Create, verify, and negotiate trust proofs. This page covers its npm package (@shukashake/mcp).
Is the io.github.cdonoyan/shuka MCP server safe to use?
io.github.cdonoyan/shuka scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.cdonoyan/shuka MCP server expose?
io.github.cdonoyan/shuka exposes 3 tools: create_attestation, verify_proof, negotiate_trust. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.
Is the io.github.cdonoyan/shuka MCP server still maintained?
io.github.cdonoyan/shuka is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.cdonoyan/shuka MCP server under?
io.github.cdonoyan/shuka declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.