Shuka
Create, verify, and negotiate trust attestations so agents and services can prove trust without bespoke identity code.
Overview
Shuka is an MCP server for the Ship phase that lets agents create, verify, and negotiate universal trust attestations via the Shuka API.
What is this MCP server?
- Universal trust attestation for AI agents: create, verify, and negotiate trust proofs
- npm package @shukashake/mcp (stdio, server version 1.0.2)
- Configurable SHUKA_API_URL plus optional secret SHUKA_API_KEY
- Repository Auron_Shuka subfolder shuka-mcp-server
- npm @shukashake/mcp version 1.0.2
- Env: SHUKA_API_URL; optional secret SHUKA_API_KEY
- Transport: stdio
What problem does it solve?
Multi-agent and MCP tool chains lack a standard way to prove and verify trust between participants.
Who is it for?
Builders shipping agent-facing products who need attestable trust between tools, services, or autonomous workers.
Skip if: Hobby projects with no trust boundaries or teams that only need conventional OAuth for human users.
What do I get? / Deliverables
After registration, your agent can issue and check trust proofs through MCP instead of ad-hoc shared secrets or honor-system prompts.
- Stdio MCP bridge to Shuka attestation APIs
- Agent workflows that create, verify, and negotiate trust proofs
Recommended MCP Servers
Journey fit
How it compares
Trust attestation MCP for agents, not a secrets vault skill or a generic OAuth login boilerplate.
Common Questions / FAQ
Who is Shuka for?
Solo and small-team builders implementing AI agent systems that must create, verify, or negotiate trust proofs across MCP tools and services.
When should I use Shuka?
Use it in Ship security when you are hardening agent workflows before launch, or when integrating third-party agents that need verifiable trust.
How do I add Shuka to my agent?
Install @shukashake/mcp, set SHUKA_API_URL (and SHUKA_API_KEY if required), and add the stdio MCP server to Claude Code, Cursor, or your client config.