# io.github.cdonoyan/shuka (npm · @shukashake/mcp)

Universal trust attestation for AI agents. Create, verify, and negotiate trust proofs.

- Trust score: 65/100 (medium)
- Change this week: +18
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@shukashake/mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/cdonoyan-shuka/shukashake-mcp.md), [page](https://verifymcp.io/servers/cdonoyan-shuka/shukashake-mcp)

## Channel facts

- Registry: `npm`
- Package: `@shukashake/mcp`
- Version: `1.0.2`
- Transport: `stdio`

## Trust breakdown

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

Scored 2026-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 165 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 474 tokens (~118/item across 4 items; 3 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add cdonoyan-shuka -- npx -y @shukashake/mcp
```

### Codex

```bash
codex mcp add cdonoyan-shuka -- npx -y @shukashake/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cdonoyan-shuka": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@shukashake/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cdonoyan-shuka --command npx --arg -y --arg @shukashake/mcp
```

### Hermes

```yaml
mcp_servers:
  cdonoyan-shuka:
    command: "npx"
    args: ["-y", "@shukashake/mcp"]
```

### Other

```json
{
  "mcpServers": {
    "cdonoyan-shuka": {
      "command": "npx",
      "args": [
        "-y",
        "@shukashake/mcp"
      ]
    }
  }
}
```

## 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-08-03 (score 65, +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.

### 2026-08-02 (score 64, +64)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security improvement] Install scripts: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → good
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 0, −21)

- [functional regression] Schema quality: 100 → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-31 (score 21, +21)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 0, −47)

- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-27 (score 47)

First indexed and scored.

## MCP tools (3)

### `create_attestation` (~162 tokens)

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.

Input parameters:

- `description` (string, required): 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

### `verify_proof` (~124 tokens)

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

Input parameters:

- `proof_token` (string, required): The Shuka proof token to verify (shk_v1.xxx.yyy or ENV-xxx format)

### `negotiate_trust` (~146 tokens)

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.

Input parameters:

- `agent_id` (string): Your agent identifier (optional, for audit trail)
- `proof_token` (string, required): The proof token to verify
- `purpose` (string): Why you need to verify this (provides context for the trust decision)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cdonoyan-shuka/shukashake-mcp#diagnostics

## Score history

- 2026-08-03: 65
- 2026-08-02: 64
- 2026-08-01: 0
- 2026-07-31: 21
- 2026-07-30: 0
- 2026-07-28: 47
- 2026-07-27: 47

## Links

- npm package: https://www.npmjs.com/package/@shukashake/mcp
- Socket report: https://socket.dev/npm/package/@shukashake/mcp
- Changelog RSS feed: https://verifymcp.io/servers/cdonoyan-shuka/shukashake-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/cdonoyan-shuka/shukashake-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/cdonoyan-shuka/shukashake-mcp