Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sigvara

NPM · @SIGVARA/PROTOCOL-SDK

Read-only checks of an AI agent's Sigvara standing, score, stake and slashes before you rely on it.

−11 this week 59 Trust /100

Last scanned (6 hours ago)

Scores higher than 29% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security48
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 2 of 10 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 642 tokens (~128/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 1.0.0-alpha.22 → 1.0.0-alpha.23 functional
  • 19 Nov 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.17 → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.0.0-alpha.21 → 1.0.0-alpha.22 functional
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 1.0.0-alpha.20 → 1.0.0-alpha.21 functional
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 55

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@sigvara/protocol-sdk@1.0.0-alpha.23

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 10 packages
Packages resolved 10
Stale 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~573 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
sigvara_check_agent ~196

Check an agent before paying or relying on it. Reports whether it is registered, Active and holding the minimum stake now; its matured score, the band it is in, and when the score was last written; the stake a slash could take; and anything pending (a slash, a queued withdrawal, a new score). With a threshold it also gives the yes or no SigvaraGate gives, without the proof of identity: use sigvara_challenge for that.

NameTypeReqDescription
agentstringyesThe agent, as did:sigvara:<chainId>:<address> or as its 0x address on the chain this server reads.
maxScoreAgeSecondsinteger–Optional. Refuse a score last written longer ago than this many seconds, or never written.
thresholdinteger–Optional. The lowest matured score you accept, 0 to 100. With it, the result carries a decision.

No output schema declared.

No examples provided.

sigvara_identity ~70

Who operates an agent, its status, when it registered, the Ed25519 key it signs with, and its DID document.

NameTypeReqDescription
agentstringyesThe agent, as did:sigvara:<chainId>:<address> or as its 0x address on the chain this server reads.

No output schema declared.

No examples provided.

sigvara_score ~80

The six factors of an agent's score, the earned total, the matured total a threshold is checked against, when it was written, and any proposal waiting out its challenge window.

NameTypeReqDescription
agentstringyesThe agent, as did:sigvara:<chainId>:<address> or as its 0x address on the chain this server reads.

No output schema declared.

No examples provided.

sigvara_stake ~89

An agent's stake: what it holds, what is queued for withdrawal and when it can leave, the minimum, its most recent slash proposal, and the share of a slash that goes to the victim the committee names.

NameTypeReqDescription
agentstringyesThe agent, as did:sigvara:<chainId>:<address> or as its 0x address on the chain this server reads.

No output schema declared.

No examples provided.

sigvara_verify_evidence ~138

Check the payments behind an agent's score against what the chain committed to. Fetches the payments the oracle lists, rebuilds their Merkle root here (never trusting the oracle's own leaves), finds which of them the finalized root on chain covers, and asks the reputation contract to confirm them with verifyEvidence. Also says whether a pending proposal's root is reproduced. It shows the oracle scored on the set it published; it does not check each transaction itself.

NameTypeReqDescription
agentstringyesThe agent, as did:sigvara:<chainId>:<address> or as its 0x address on the chain this server reads.

No output schema declared.

No examples provided.

Install

How do I install the Sigvara MCP server?

Sigvara runs locally as an npm package, launched with npx -y @sigvara/protocol-sdk. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @sigvara/protocol-sdk

# add to Claude Code
claude mcp add runtimeadmin-sigvara -- npx -y @sigvara/protocol-sdk
Common questions

What is the Sigvara MCP server?

Sigvara is an MCP server listed in the public MCP registry as io.github.RunTimeAdmin/sigvara. Read-only checks of an AI agent's Sigvara standing, score, stake and slashes before you rely on it. This page covers its npm package (@sigvara/protocol-sdk).

Is the Sigvara MCP server safe to use?

Sigvara scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Sigvara MCP server expose?

Sigvara exposes 5 tools: sigvara_check_agent, sigvara_score, sigvara_stake, sigvara_identity, sigvara_verify_evidence. Their descriptions and schemas cost roughly 573 tokens of context every time the server is loaded.

Is the Sigvara MCP server still maintained?

Sigvara is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Sigvara MCP server under?

Sigvara declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Sigvara MCP server?

VerifyMCP ran 15 checks on Sigvara, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Sigvara: Malware scan. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.