World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Read-only checks of an AI agent's Sigvara standing, score, stake and slashes before you rely on it.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 20/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 32/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Sigvara. Follow https://mcp.popnx.com/i/runtimeadmin-sigvara.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 19, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Sigvara for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "sigvara": { "command": "npx", "args": [ "-y", "@sigvara/protocol-sdk" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Sigvara tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"sigvara": {
"command": "npx",
"args": [
"-y",
"@sigvara/protocol-sdk"
]
}
}
}Use Sigvara and tell me what you can do for me, then show me one thing✓ If Claude says it is using Sigvara or shows a Sigvara tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Sigvara yet
Sigvara runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Sigvara
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Sigvara for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user sigvara -- npx -y @sigvara/protocol-sdk 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Sigvara tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user sigvara -- npx -y @sigvara/protocol-sdkYou should see Sigvara listed as connected
Use Sigvara and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Sigvara or shows a Sigvara tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Sigvara for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "sigvara": { "command": "npx", "args": [ "-y", "@sigvara/protocol-sdk" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Sigvara tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Sigvara and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Sigvara or shows a Sigvara tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Sigvara for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "sigvara": { "type": "stdio", "command": "npx", "args": [ "-y", "@sigvara/protocol-sdk" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Sigvara tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Sigvara and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Sigvara or shows a Sigvara tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user sigvara -- npx -y @sigvara/protocol-sdkClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"sigvara": {
"command": "npx",
"args": [
"-y",
"@sigvara/protocol-sdk"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"sigvara": {
"command": "npx",
"args": [
"-y",
"@sigvara/protocol-sdk"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"sigvara": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sigvara/protocol-sdk"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @sigvara/protocol-sdkBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account RunTimeAdmin, which owns the repo
Code last changed yesterday
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/runtimeadmin-sigvara)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (1.0.0-alpha.22) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Sigvara | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
TypeScript SDK for the Sigvara protocol: on-chain agent identity, computed reputation, staked accountability, and Ed25519 challenge-response authentication between agents. Successor to @countersig/protocol-sdk.
npm install @sigvara/protocol-sdk
Runtime dependencies are ethers v6 and tweetnacl. Node 18 or newer.
Use 1.0.0-alpha.12 or later. On 1.0.0-alpha.9 and earlier an agent object carries its secret key in an ordinary property, so JSON.stringify(agent) or logging one includes it; never log or serialize an agent from those versions. If one was logged, serialized or sent to an error reporter, treat its key as exposed and rotate it (Key Rotation).
Upgrading from 1.0.0-alpha.11:
agent.signChallengeis removed. It signed whatever it was
handed, so a verifier could get an agent to sign a challenge naming a different verifier and
present the signature there as the agent. A call does not compile in TypeScript, and in JavaScript
it throws an error that names
signChallengeFor(payload, audience), which signs only a challenge
addressed to the audience you pass and works from 1.0.0-alpha.10. The exported function
signChallenge(payload, secretKey)is unchanged. Details in CHANGELOG.md.
Upgrading from 1.0.0-alpha.10:
verifySignaturenow requires the audience, as its fifth
argument. Leaving it out used to compile and skip the check of who the agent had signed for, so a
response given to one verifier was accepted at another, and a v1 payload was accepted too. It now
does not compile in TypeScript, throws
expectedAudience is requiredin JavaScript, and a v1 payload
is always refused. A caller that already passes the audience needs no change. Details in
Upgrading from 1.0.0-alpha.9: the secret key is now a private field, so code that read it by
reaching around the type system stops working; sign with
signChallengeFor. It signs only a
challenge addressed to the audience you pass, where
signChallengesigned whatever it was handed
and is removed in 1.0.0-alpha.12. A gate now also checks the bond held now, so an agent
admitted at an old minimum stake and not topped up is refused as
not_active. It refuses to be
built with a
thresholdorttlSecondsthat is not a usable number, refuses a challenge dated
more than 60 seconds ahead, and gives up on a chain read after 30 seconds (
timeoutMs). The
optional
maxScoreAgeSecondsrefuses a score nobody has refreshed. Details in
Upgrading from 1.0.0-alpha.7:
generateChallengenow takes an audience as its
second argument, and every existing call site needs it.
`diff
- const challenge = generateChallenge(agentDid);
+ const challenge = generateChallenge(agentDid, 'https://your-service.example');
`
Without it, a verifier holding a valid response could present that same response to a
different verifier and be accepted as the agent. Pass the same audience to
verifySignatureas its fifth argument; on 1.0.0-alpha.10 and earlier, omitting it still
compiles and still accepts the relayable older proofs. Full detail in CHANGELOG.md.
This does not make you replay-proof. The audience stops a response being reused at
a *different* verifier. Reuse at *yours* is stopped by remembering the nonce, and the
SDK cannot do that for you — see
What the SDK still needs from you.
did:sigvara: : and its on-chain didHash, and register the agent from the operator wallet, with a proof of control signed by the agent address.meetsThreshold, stake and minimum-stake checks, and a W3C DID Document built from chain state.depositStake handles the ERC-20 approval and the deposit in one call, and is what moves a newly registered agent from PendingBond to Active.SigvaraGate turns the reads above into one decision: issue a challenge, admit or refuse, and say which reason applies. It owns the nonce, so replay protection is not left to the caller.SigvaraTrustCheck asks the gate's question about a bare address. sigvaraX402Fetch puts it in front of an x402 payment, and sigvaraTrustTool and requireTrustedAgent put it in an agent framework's tools.signPaymentOutcome), so the oracle can count it without a token, and check such a signature the way the oracle does (verifyPaymentOutcome).Scores come in two forms. The earned score is what the oracle last finalized; the total score is the matured one, which climbs toward it over time and is what meetsThreshold checks. A newly bonded agent has earned a score before it can spend it.
import { SigvaraAgent, SigvaraVerifier, registerAgent, depositStake, generateChallenge } from '@sigvara/protocol-sdk';
import { ethers } from 'ethers';
const RPC = 'https://rpc.testnet.arc.io'; const CHAIN_ID = 5042002; // Arc testnet const addresses = { identity: '0x…', reputation: '0x…', staking: '0x…' }; // deployments/5042002.json
// Operator side: create, register and bond an agent const { agent, privateKey } = SigvaraAgent.generate({ agentAddress: '0xAgent…', chainId: CHAIN_ID }); const operator = new ethers.Wallet(process.env.OPERATOR_KEY!, new ethers.JsonRpcProvider(RPC));
// The agent address must prove control of itself. Pass a signer for it, or // { signature } if it was signed elsewhere (HSM, Safe, any ERC-1271 contract). const agentSigner = new ethers.Wallet(process.env.AGENT_KEY!); // a signer for agent.agentAddress await registerAgent(operator, agent.agentAddress, agent.publicKeyBytes32, addresses.identity, { agentSigner });
// Registration leaves the agent PendingBond. This deposit is what activates it. await depositStake(operator, agent.didHash, 1000n * 10n ** 18n, addresses.staking);
// Counterparty side: challenge the agent, verify the signature, read status and score const verifier = new SigvaraVerifier({ rpcUrl: RPC, addresses, chainId: CHAIN_ID }); // The second argument is the audience: who is asking. Pass a stable identifier you // control, normally your own origin. It is signed, so the agent's response proves it was // talking to *you* and cannot be relayed onward by anyone who receives it. const challenge = generateChallenge(agent.did, 'https://your-service.example'); // Done by the agent, returned to the counterparty. signChallengeFor refuses a challenge that is not // addressed to the verifier the agent means to prove itself to, which is what stops a verifier from // collecting a signature meant for someone else. const signature = agent.signChallengeFor(challenge.payload, 'https://your-service.example');
// Pass the same audience back when verifying. It is required: verifySignature throws without // it, and it refuses a v1 payload, which names no audience to check. const ok = await verifier.verifySignature( agent.did, challenge.payload, signature, 300, 'https://your-service.example', ); const trusted = ok && (await verifier.isActive(agent.did)) && (await verifier.meetsThreshold(agent.did, 40));
The 40 in these examples is a placeholder. A score below roughly 60 says little on its own, so read what a fake score costs before you pick a number, and sigvara.xyz/status for how the scores spread today.
Signature validity, status and score are separate reads. Combining them correctly is easy to get subtly wrong, so there is a piece that does it.
SigvaraGateimport { SigvaraGate } from '@sigvara/protocol-sdk';
const gate = new SigvaraGate({ rpcUrl: RPC, addresses, chainId: CHAIN_ID, threshold: 40, audience: 'https://your-service.example', // required, and signed into every challenge });
// 1. hand the challenge to the agent const challenge = gate.challenge(agentDid);
// 2. the agent signs challenge.payload and returns the signature
// 3. decide const result = await gate.admit(agentDid, challenge, signature); if (!result.ok) { // 'bad_proof' | 'replayed' | 'not_active' | 'below_bond' | 'stale_score' | 'below_threshold' return refuse(result.reason); }
The reasons are separate because they need different responses. bad_proof means nothing was proven. replayed means a valid signature arrived twice. not_active means a real, proven agent that is unbonded, suspended or slashed, and telling that caller to earn more points would be wrong. "Unbonded" is the bond held now against the minimum stake in force now, not the status stored when the agent was admitted: a minimum raised since leaves an agent marked Active while it holds less than the contract asks, and the gate reads the bond for that reason. below_bond appears only if you set minBond, and stale_score only if you set maxScoreAgeSeconds. Only below_threshold is about reputation, and it carries the score so you can say how short they were.
A score nobody has refreshed. Nothing on chain ages a score, so one left over from an oracle outage keeps passing a threshold. Set maxScoreAgeSeconds to refuse a score written longer ago than that, or never, with stale_score. A healthy score gets to about two of your oracle's proposals apart before the next one lands (about 20 hours on Arc testnet, where an unchanged score is proposed again every 12 hours, two days on a daily epoch), so choose more than that. It is measured against your host's clock. Unset, a score is trusted however old it is. It costs one more read per admission. The same check exists on chain as SigvaraReader.isTrustedFresh, on Arc testnet at 0x2921b4eE879CdF5793FA273BbDc4E7dF01ABcef8.
More at stake than the minimum covers. Set minBond to refuse an agent holding less, with below_bond, whatever its score (from 1.0.0-alpha.16). It is in the bond token's base units, as a bigint or a string of digits. A number is refused, because a floor past what a double can hold would quietly become another floor. A floor under the protocol's minimum still needs the minimum, and an amount queued for withdrawal does not count. It compares the same number as SigvaraReader.isTrusted(agent, minScore, minBond), and costs one more read per admission.
The constructor refuses a threshold that is not a finite number of 0 or more, and a ttlSeconds or maxScoreAgeSeconds that is not a positive number. A NaN threshold, for example Number(process.env.THRESHOLD) with the variable unset, would otherwise admit every active agent that can prove its key, whatever its score.
A gate that has to say how it runs. Two of the defaults suit a test bench and not a deployment, and both fail open by being left out: instances defaults to one process, and no maxScoreAgeSeconds means no age limit. profile: 'production' (from 1.0.0-alpha.14) makes the constructor refuse to build the gate until both are set, and names everything missing in one error:
const gate = new SigvaraGate({
rpcUrl: RPC, addresses, chainId: CHAIN_ID, threshold: 40, audience: 'https://your-service.example', profile: 'production', instances: 'multiple', // or 'single' if exactly one process serves this gate nonceStore, // shared and atomic, required with 'multiple' (see below) maxScoreAgeSeconds: 86_400, // more than two of your oracle's