Skip to content

feat(wallet-mcp): add Sigvara plugin - #20

Open
RunTimeAdmin wants to merge 2 commits into
coinbase:mainfrom
RunTimeAdmin:feat/wallet-mcp-sigvara-plugin
Open

RunTimeAdmin wants to merge 2 commits into
coinbase:mainfrom
RunTimeAdmin:feat/wallet-mcp-sigvara-plugin

Conversation

@RunTimeAdmin

@RunTimeAdmin RunTimeAdmin commented Nov 7, 2026 •

Copy link
Copy Markdown

Description

Adds the Sigvara Wallet MCP plugin: skills/wallet-mcp/plugins/sigvara.md, version 0.1.0, external-mcp over stdio, chains: [].

Sigvara is a registry and reputation protocol for AI agents. An agent posts a bond that can be slashed and earns a score from payments that settled to its address. This plugin lets an assistant read an agent's record before the user pays it, through sigvara-mcp, a read-only local MCP server in @sigvara/protocol-sdk.

  • It signs nothing and sends nothing. ## Submission is none.
  • It uses Wallet MCP's chain_rpc_request and probe_x402_response as read steps.
  • chains is empty because the contracts are on Arc testnet, which Wallet MCP does not target. Payments on Base Sepolia count toward scores, read by the oracles.
  • This is testnet only. Bonds are in a token with no value, most registered agents are our own labelled simulation, and no outside service relies on a score yet. The plugin says so and tells the assistant to report results that way, with no verdict on any agent.

Docs: https://sigvara.xyz/integrate. Source, MIT: https://github.com/RunTimeAdmin/Sigvara/tree/main/packages/sdk.

I also run Sigvara, and opened #16 for a separate project.

Change type

  • Skill workflow

Validation

  • Checked against the plugin spec and the Authoring Checklist, by hand and with a small script: frontmatter fields and enum values, canonical section names and order, the pinned version everywhere it appears, and local-exec with stdio.
  • Every call in the file was run against live services on 2026-11-07, and the Sigvara calls again on 2026-11-08 on 1.0.0-alpha.18:
    • sigvara_check_agent on the published @sigvara/protocol-sdk@1.0.0-alpha.17 over stdio, and again on 1.0.0-alpha.18, for a registered agent, a slashed one, a suspended one, an address that never registered, a threshold met and one missed, and input that is not an address. Each behaved as the file describes.
    • sigvara_verify_evidence on the published 1.0.0-alpha.18, 8 times on each of the two public Arc RPCs on 2026-11-08, half on an agent with 70 covered payments and half on one with none: every run succeeded, and on the first agent the contract confirmed all 70 each time.
    • chain_rpc_request with eth_getCode on base-sepolia, for an address with no code and one with code.
    • probe_x402_response against a live x402 endpoint, which reports payTo as the file says. Nothing was paid.
  • Not run: a full session with this plugin loaded beside Wallet MCP in Claude Code, Codex or Cursor (I reached the server directly over stdio); the install snippets themselves; the plugin-review skill, which is not in this checkout; the repository's unit tests.

Known limits

  • The first version of this PR pinned 1.0.0-alpha.17, whose sigvara_verify_evidence failed on an agent with a long payment history, because the public Arc RPC refused its burst of calls. 1.0.0-alpha.18 confirms them in one read through Multicall3, so the pin is now 1.0.0-alpha.18 and the evidence flow is back.
  • The public Arc RPC can also refuse several checks in quick succession. ## Notes tells the assistant this says nothing about the agent, and to wait and retry.

Release considerations

  • No web_request allowlist entry is needed. On chat-only surfaces the plugin stops and says it needs a local install, as the spec requires for stdio.
  • This adds the tag reputation, so the diff also touches the tag vocabulary in plugin-spec.md, as Contribution Scope allows. Nothing else changes outside the plugin file.
  • Maintainers to add the SKILL.md registry row on acceptance.

🤖 Generated with Claude Code

Adds skills/wallet-mcp/plugins/sigvara.md, version 0.1.0, external-mcp over
stdio, chains [].

Sigvara is a registry and reputation protocol for AI agents, on Arc testnet
only. The plugin reads an agent's record before the user pays it, through the
read-only sigvara-mcp server, and submits nothing through Wallet MCP. Adds the
tag reputation to the vocabulary list, as Contribution Scope allows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@cb-heimdall

Copy link
Copy Markdown

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
1 if authored by an app that is not allowlisted and lacks verified human attribution 0
Sum 1

1.0.0-alpha.18 confirms a finalized root's payments in one read through
Multicall3, so sigvara_verify_evidence no longer fails on a long payment history
against the public Arc RPC. The evidence flow and its example are back.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants