Penumbra MCP Server

Created By
avahowella year ago
an MCP server for penumbra, allowing AI agents to operate a penumbra wallet.
Overview

what is Penumbra MCP Server?

Penumbra MCP Server is a Model Context Protocol (MCP) server designed for Penumbra, enabling AI agents to operate a Penumbra wallet.

how to use Penumbra MCP Server?

To use the Penumbra MCP Server, set up the server environment as per the documentation, and configure your AI agents to interact with the Penumbra wallet through the MCP protocol.

key features of Penumbra MCP Server?

  • Supports AI agent operations for wallet management
  • Built using the Rust programming language for performance
  • Open-source and available on GitHub

use cases of Penumbra MCP Server?

  1. Automating transactions in a Penumbra wallet using AI agents.
  2. Integrating AI functionalities for enhanced wallet security.
  3. Developing custom AI solutions for managing digital assets.

FAQ from Penumbra MCP Server?

  • What programming language is Penumbra MCP Server built with?

Penumbra MCP Server is built using Rust.

  • Is Penumbra MCP Server open-source?

Yes! It is available on GitHub for public use and contributions.

  • Can I use Penumbra MCP Server for other wallets?

Currently, it is specifically designed for the Penumbra wallet.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
avahowell
Star
0
Language
Rust
License
-

Recommend Servers

View All
Payai X402 Tools

8 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago