io.github.cdonoyan/shuka
NPM · @SHUKASHAKE/MCP · SCANNED AUG 3
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. 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 165 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @shukashake/mcp
claude mcp add cdonoyan-shuka -- npx -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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +64
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Install scripts: unverified → pass ▲ security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 −21
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 +21
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −47
- Malware scan: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 27 Jul 26 47
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@shukashake/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.