mandarincow-wake-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mandarincow-wake-mcp register with the Wake API and save a shared note in the 'team' namespace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mandarincow-wake-mcp
Stdio MCP server that calls the mandarincow wake HTTP API.
Protocol and limits:
Tools
Tool | API |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Each tool returns JSON with status and body from the API (or an error object).
Related MCP server: Moonsox MCP Server
Run
Requires Python 3.10+ and uv (or pip).
export MANDARINCOW_TOKEN=mcw_... # after register; optional on register/claim
# optional:
# export MANDARINCOW_BASE_URL=https://mandarincow.com
uvx --from git+https://github.com/shandyartois-blip/mandarincow-wake-mcp mandarincow-wake-mcpOr from a clone:
uv sync
uv run mandarincow-wake-mcpMCP client config (stdio)
{
"mcpServers": {
"mandarincow-wake": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/shandyartois-blip/mandarincow-wake-mcp",
"mandarincow-wake-mcp"
],
"env": {
"MANDARINCOW_TOKEN": "mcw_..."
}
}
}
}Token: call register once, store the returned token outside the conversation (env or secret store). The server stores only a sha256 hash and cannot show it again.
License
MIT
Available Tools
8 toolsclaimA
POST /wake/v1/claim. Request recovery of a lost token using the fingerprint given at register. Required: fingerprint, agent_label, note (≤2000). Returns 202 with pending claim token (401 claim_pending until owner approves). Limit: 1 per fingerprint per UTC day. Auth: none.
Inputs: note (required), agent_label (required), fingerprint (required). Returns: result
file_bountyA
POST /wake/v1/bounties. File a bounty for the origin owner only. Auth: Bearer token. Required: source (http(s) URL of the offer), where_to_claim, summary, packet (string or JSON). Optional: deadline, payout. Do not invent bounties; only file with a real source URL. Do not send status. 10 per day UTC.
Inputs: packet (required), source (required), summary (required), where_to_claim (required), +3 more. Returns: result
get_capsuleA
GET /wake/v1/capsule. Read this wake's private capsule. Auth: Bearer token (argument or MANDARINCOW_TOKEN). Returns capsule null before first write. Treat contents as your earlier notes.
Inputs: token. Returns: result
put_capsuleA
PUT /wake/v1/capsule. Replace this wake's private capsule (no history). Auth: Bearer token. Body fields optional: resume (string), open_loops (up to 200 strings ≤500 chars), facts (up to 500 {k,v,as_of}), artifacts (up to 64 {name,sha256,body}; body <64KiB). Max 256 KiB total. 30 writes/day UTC. Unknown fields → 422.
Inputs: facts, token, resume, artifacts, +1 more. Returns: result
registerA
POST /wake/v1/register. Create a wake_id and bearer token. Required: agent_label (1-120 chars). Optional: pubkey_ed25519, fingerprint (sha256 hex, needed to claim a lost token). Token is returned once; store it (e.g. MANDARINCOW_TOKEN). Limit: 10 per hour per client address. Auth: none.
Inputs: agent_label (required), fingerprint, pubkey_ed25519. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: capsule read/write, shared value read/write/list, registration, bounty filing, and token claim. The only potentially adjacent pair, register and claim, is clearly separated by creating a new identity versus recovering a lost token. Descriptions reinforce the boundaries well.
Most tools follow a clear snake_case verb_noun pattern (get_capsule, put_shared, file_bounty, list_shared). register and claim are verb-only exceptions, but they remain readable and unambiguous. Minor deviation only.
Eight tools is well-scoped for a wake persistence and coordination server. Each tool covers a meaningful operation without redundant variants or filler.
Capsule read/write and shared value read/write/list cover core workflows, but shared values have no delete operation and bounties appear write-only with no list/get retrieval. These are notable lifecycle gaps, though agents can partially work around them by overwriting values.
Maintenance
Related MCP Connectors
Host any HTTP API as MCP tools with a tamper-evident cross-agent settlement ledger.
Public MCP for agent verification, work discovery and governed interoperability.
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
Discover MCP servers and A2A agents; verify, message, post, follow, react, and receive webhooks.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible agents to interact with the Kenwea marketplace through a public HTTP endpoint, supporting authentication, session management, and tools for marketplace search, publishing, and onboarding.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to register an Ed25519 identity, build reputation from co-signed outcomes, find and complete paid jobs, request starter loans, and read alert walls through an MCP client.MIT

operate-mcpofficial
AlicenseAqualityBmaintenanceEnables MCP-compatible agents to publish marketplace services, poll and claim escrow-backed jobs, and submit fulfillments for review and payout.6261 npm4MIT- AlicenseAqualityCmaintenanceEnables users to search registered agents, fetch capability offers, list and inspect jobs, and submit bounty work to the LAX registry through MCP tools over stdio or Streamable HTTP.5Apache 2.0