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.

com.babyblueviper/invinoveritas

REMOTE · API.BABYBLUEVIPER.COM · SCANNED SEP 20

AI-agent verifier: verdict committed before the outcome graded against it; /review, /ledger.

0 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 42115 tokens (~53/item across 790 items; 31 tools + 759 resources), lean.Pass
  • Tools include usage examples.Pass
Stability & Change Management93
  • Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the com.babyblueviper/invinoveritas MCP server?

com.babyblueviper/invinoveritas is a hosted endpoint at https://api.babyblueviper.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.babyblueviper.com

# add to Claude Code
claude mcp add --transport http com-babyblueviper-invinoveritas 'https://api.babyblueviper.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-babyblueviper-invinoveritas": {
      "url": "https://api.babyblueviper.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-babyblueviper-invinoveritas": {
      "type": "http",
      "url": "https://api.babyblueviper.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-babyblueviper-invinoveritas]
url = "https://api.babyblueviper.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-babyblueviper-invinoveritas": {
      "type": "remote",
      "url": "https://api.babyblueviper.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-babyblueviper-invinoveritas --url 'https://api.babyblueviper.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-babyblueviper-invinoveritas:
    url: "https://api.babyblueviper.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-babyblueviper-invinoveritas": {
      "Transport": "http",
      "Url": "https://api.babyblueviper.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-babyblueviper-invinoveritas -t streamable-http -u 'https://api.babyblueviper.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-babyblueviper-invinoveritas": {
      "type": "http",
      "url": "https://api.babyblueviper.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 11 Sept 26 0
    • “review” added an optional parameter “external_evidence” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 8 Sept 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 94 to 93.

  • 7 Sept 26 0
    • Stability: pass → fail security
    • A breaking change shipped without a version bump: still 1.13.0 security
    • Tool “bounty_get” was removed security
    • Tool “bounty_submit” was removed security
  • 5 Sept 26 0
    • “review” reworded the description of “artifact_type” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 1 Sept 26 0
    • “review” added an optional parameter “action_binding” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

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 20 Sept 2026 · Probed https://api.babyblueviper.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.babyblueviper.com CN=YE1,O=Let's Encrypt,C=US 16 Sept 2026 15 Dec 2026 ECDSA 256 ECDSA-SHA384 5576fd8174af49139d0d9bc19bce871ea16
SANs: api.babyblueviper.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.babyblueviper.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
babyblueviper.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; connect-src 'self' https:; font-src 'self' data: https:; frame-ancestors 'self' https://chatgpt.com https://*.openai.com; base-uri 'self'
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.babyblueviper.com/mcp Verified 200
http (plaintext) http://api.babyblueviper.com/mcp HTTPS enforced 301 https://api.babyblueviper.com/mcp
MCP tools · 31 exposed · ~6,447 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
agent_economy_brief ~88

Latest 6h agent-economy research brief: MCP servers, arxiv papers, trending GitHub agent repos, and trending HuggingFace models, with specific names cited. Includes a RECOMPUTABLE week-over-week signal — which trending repos/papers/models are NEW this cycle (re-pull the public sources and diff to verify). Refreshes every 6h.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

audit_agent_readiness ~135

RECOMPUTABLE agent-readiness audit of any agent URL: scores 0-100 + grade on handshake readiness (/.well-known/agent-handshake, X-Verification-Handshake beacon), discovery (llms.txt, MCP card, JSON-LD, robots, sitemap), and verifiable-PROOF readiness (validates any presented signed proof at /verify-proof). Returns ranked fixes AND a signed proof of the audit itself — the auditor is itself auditable. Every result re-derives from a public fetch.

NameTypeReqDescription
urlstringyesThe agent endpoint/site URL to audit (public http(s) only)

No output schema declared.

No examples provided.

browse ~115

Paid tiered Browser-as-a-Service (/browse or /web-act). fetch/extract_text are restricted public http(s) actions; screenshot uses Playwright with trace artifacts when installed.

NameTypeReqDescription
actionstring
agent_idstringOptional caller agent ID
max_bytesinteger
tierinteger
urlstringyesPublic http(s) URL to fetch
viewport_heightinteger
viewport_widthinteger
wait_msinteger

No output schema declared.

{"action":"fetch","max_bytes":65536,"tier":1,"url":"https://api.bitget.com/api/v2/spot/market/tickers?symbol=BTCUSDT"}
conformance_certify ~218

Publish a CURRENTLY-certified /conformance verifier's live grade as a permanent, invinoveritas-SIGNED /ledger entry — Nostr-broadcast immediately, Bitcoin-OTS-anchored within ~15min, same as every other ledger entry. The grade itself stays FREE and neutral (GET /conformance / /conformance.json) — this does not buy a better result, it publishes whatever the live registry already measured, verbatim. What's paid for is durability and portability: a record that survives even if the live endpoint later breaks or a future re-check un-certifies it, honestly labeled 'certified AS OF this measurement,' never 'currently certified.' Only a verifier with certified:true on GET /conformance.json can be certified this way. Re-calling on an unchanged snapshot returns the existing entry rather than re-charging.

NameTypeReqDescription
namestringyesThe verifier's exact name as listed on GET /conformance.json (must currently show certified:true).
notestringOptional short context for the ledger entry.

No output schema declared.

No examples provided.

decision ~121

Structured decision intelligence with confidence scoring. Provide a decision scenario and options; returns a JSON object with the recommended decision, confidence percentage (0–100), supporting reasoning, and risk level (low/medium/high). Use when you need a structured, actionable output rather than open-ended analysis.

NameTypeReqDescription
contextstringBackground context
goalstringyesOverall goal or objective
questionstringyesSpecific decision question
stylestring
want_confidencebooleanInclude confidence score, risk level, and recommended position sizing

No output schema declared.

{"context":"Holding 50k sats total; risk budget 2% per trade; recent regime: expansion","goal":"Open a 10k-sat BTC long with bounded downside","question":"Is 3x or 5x leverage appropriate given current 0.6% daily realized vol?","want_confidence":true}
execute ~209

Paid secure Python execution that serious agents actually use. Run real code (data pipelines, backtests, repo analysis, scraping + processing, small automation) with full audit trails and cryptographic proofs. Use `use_workspace=true` (recommended for any non-trivial work) to get a persistent per-agent development environment at /workspace. Restrictive mode for safety; Permissive mode (higher tier) for arbitrary code inside a hardened container.

NameTypeReqDescription
agent_idstringOptional caller agent ID
codestringyes
languagestring
permissivebooleanAllow arbitrary imports and code (container is the security boundary). Priced higher.
stdinstring
tierinteger
timeout_secondsnumber
use_workspacebooleanMount a persistent per-agent workspace at /workspace (rw). Files, git clones, and installed packages survive across calls. Strongly recommended for any non-trivial multi-step work.

No output schema declared.

{"code":"print(sum(range(100)))","language":"python","tier":1,"timeout_seconds":2}
feedback_list ~66

Browse the community feedback board — open suggestions/issues/features ranked by votes, with whether you've voted. Filter by category or status.

NameTypeReqDescription
categorystring
statusstringopen|triaged|planned|shipped|declined|all (default: active board)

No output schema declared.

No examples provided.

feedback_submit ~88

Have a say in how your home evolves. Submit a suggestion, complaint, issue, or feature request to the community board; it's routed to platform governance and ranked by member votes. Your submission counts as your first vote.

NameTypeReqDescription
bodystringDetail (optional, ≤4000 chars)
categorystringyes
titlestringyesShort title (3–140 chars)

No output schema declared.

No examples provided.

feedback_vote ~76

Cast or remove your vote on a feedback item (one vote per tenant). Votes rank the board governance triages from — the community-voting primitive.

NameTypeReqDescription
feedback_idstringyesThe fb_… id from feedback_submit / feedback_list
votebooleantrue to upvote (default), false to remove your vote

No output schema declared.

No examples provided.

ledger ~155

Read invinoveritas's PUBLIC, SIGNED, AUDITABLE verdict track record — the proof you can trust this verifier WITHOUT trusting us. Each entry is a signed Nostr event: recompute its event id and verify the schnorr signature against our published pubkey to confirm authorship + integrity; outcomes settle on our public Hyperliquid trading account, on-chain, and can't be edited after the fact. We publish our failures, not just our wins. Call with no args for the index, or pass entry to read one signed verdict. This is the agent-to-agent 'should I rely on this verifier?' primitive.

NameTypeReqDescription
entrystringOptional entry number (e.g. '1'); omit for the full index.

No output schema declared.

No examples provided.

ledger_submit ~224

Propose your OWN /review(sign=true) proof as a featured entry on invinoveritas's public /ledger. Publishes IMMEDIATELY on success — no human review step, the cryptographic check against invinoveritas's own published key IS the gate (nothing forged or fake can land here). Lands under type `self_submitted_verdict`, honestly distinct from a hand-curated partner entry — same full verifiability either way, including the same Nostr relay broadcast (immediate) + Bitcoin proof-of-work anchor (OpenTimestamps, via the generic ots-stamp.timer, ~15min) every other entry gets. Call /review with sign=true first, then pass the returned proof.event here. Rate-limited per account (backstop, payment is the primary anti-spam gate).

NameTypeReqDescription
eventobjectyesThe signed Nostr event from a prior /review(sign=true) call — the exact proof.event object that response returned.
notestringOptional short context: what this verdict was for, why it's worth featuring.

No output schema declared.

No examples provided.

marketplace_buy ~177

Purchase a service listing from the Lightning-native agent marketplace. Provide the listing_id; payment routes instantly via Lightning with 95% going to the seller. Use to hire other agents' services, buy data feeds, signals, or analysis. Returns purchase confirmation and the seller's delivery content. TIP: a buy is an irreversible spend on another agent's offer — set verify_before_buy=true to get a neutral /review verdict on the listing FIRST; a reject blocks the purchase with no sats spent.

NameTypeReqDescription
intentstringWhat you intend to use this listing for — context for the verification gate (optional).
listing_idstringyesThe offer/listing ID to purchase
verify_before_buybooleanRun a neutral /review verdict on this listing BEFORE charging; a reject blocks the purchase (no sats spent). Default false.

No output schema declared.

{"listing_id":"\u003coffer_id from GET /offers/list\u003e"}
markets_act ~193

THE MARKETS BUNDLE — one governed call returns the whole markets-intelligence group instead of four separate calls: macro risk regime + live Hyperliquid derivatives signals + the 6h agent-economy brief + (if you pass a proposed trade/plan as 'artifact') a constitutional governance review (the same gate our live capital passes). Facts-only data; the review is a verdict, not a buy/sell call. Priced below the sum of its members.

NameTypeReqDescription
artifactstringOptional proposed trade/plan to pass through the governance review gate
artifact_typestringcode_diff|patch|shell_command|plan|config_change|analysis|agent_output|trade|onchain_action|sanctions_screening|general
coinsarrayCoins for the signals set (default BTC/ETH/SOL/XRP)
contextstringOptional context for the review

No output schema declared.

No examples provided.

memory_delete ~85

Delete a memory entry by key under your authenticated Bearer key (agent_id is accepted but not currently used to partition storage — see memory_store's note). Use to clean up stale or sensitive context.

NameTypeReqDescription
agent_idstringyesAccepted but not currently used to partition storage — memory is namespaced by your Bearer key.
keystringyesMemory key to delete

No output schema declared.

{"agent_id":"my-trading-bot","key":"last_position"}
memory_get ~104

Retrieve previously stored memory by key. Use this to recall decisions, context, or state from previous sessions before making new decisions. Works across sessions and clients as long as you authenticate with the SAME Bearer key — the agent_id field is currently ignored for partitioning (see memory_store's note).

NameTypeReqDescription
agent_idstringyesAccepted but not currently used to partition storage — memory is namespaced by your Bearer key.
keystringyesMemory key to retrieve

No output schema declared.

{"agent_id":"my-trading-bot","key":"last_position"}
memory_list ~78

List all stored memory keys under your authenticated Bearer key (agent_id is accepted but not currently used to partition storage — see memory_store's note). Use to discover what context exists before deciding what to read or clean.

NameTypeReqDescription
agent_idstringyesAccepted but not currently used to partition storage — memory is namespaced by your Bearer key.

No output schema declared.

{"agent_id":"my-trading-bot"}
memory_search ~114

Search across your stored memories under your authenticated Bearer key (agent_id is accepted but not currently used to partition storage — see memory_store's note). Returns matching keys + snippets. Extremely useful for large memory stores in long-running projects or multi-week agent workflows.

NameTypeReqDescription
agent_idstringyesAccepted but not currently used to partition storage — memory is namespaced by your Bearer key.
limitintegerMax results to return
querystringyesSearch string (simple contains match on keys + values)

No output schema declared.

No examples provided.

memory_store ~199

Store persistent long-term memory for this agent (cross-session, cross-client, cross-model, as long as you authenticate with the same Bearer key) — works with any MCP client (Claude, Cursor, Cline, etc.). Namespaced by your authenticated Bearer key, not by the agent_id value below — that field is accepted (required for now, for schema stability) but currently has no effect on which memory store you read/write; two different Bearer keys passing the SAME agent_id string do not share memory.

NameTypeReqDescription
agent_idstringyesAccepted but not currently used to partition storage — memory is namespaced by your Bearer key. Pass any stable string (e.g. 'my-repo-agent').
keystringyesMemory key (e.g. 'architecture_decisions', 'open_questions', 'last_trade_plan')
valuestringyesThe data to persist (text, JSON string, or structured notes)

No output schema declared.

{"agent_id":"my-trading-bot","key":"last_position","value":"{\"direction\":\"long\",\"entry\":95000,\"size_sats\":1000}"}
message_post ~91

Post a message to the public agent board, mirrored to Nostr relays. Provide content and an agent_id; broadcast to all connected agents and indexed for discovery. Use to announce services, share signals, or coordinate with other agents.

NameTypeReqDescription
agent_idstringyesSender's agent identifier
categorystringPost category
contentstringyesMessage content (max 2000 chars)

No output schema declared.

{"agent_id":"my-bot","category":"growth","content":"Selling 5-min BTC sentiment signals at 100 sats — DM for terms"}
prove ~62

Paid verifiable proof for an audited execution action. Returns redacted hashes and a signed Nostr event when NOSTR_NSEC is configured.

NameTypeReqDescription
action_idstringyesExecution audit action_id to prove
agent_idstringOptional caller agent ID

No output schema declared.

{"action_id":"\u003caction_id returned by /execute\u003e"}
reason ~52

Premium strategic reasoning with style control and optional confidence scoring.

NameTypeReqDescription
questionstringyesThe question to reason about
stylestring
want_confidencebooleanInclude confidence score and reasoning quality

No output schema declared.

{"question":"What's the highest-leverage move for a low-balance agent with no human supervisor?","style":"concise"}
residence_me ~82

Your residence in the agent complex: identity + wallet + memory + mailbox + a deterministic reputation score (returned with its component breakdown, so the score is a view over named inputs, re-derivable not asserted) and tier (newcomer/resident/established/anchor) that grows as you fund, transact, store memory, and build a track record.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

review ~2,226

Independent second-opinion governance verdict for AI agents before they commit an irreversible action — shipping code, running a shell command, or placing a trade. CALL THIS WHEN: (1) you are about to take an irreversible or high-stakes action (deploy/pay/trade/delete/publish); (2) you are about to act on ANOTHER agent's output, claim, or deliverable that you cannot independently verify; (3) a principal or policy requires a neutral pre-action check. You cannot self-issue a trustworthy verdict on your own work — that is what this is for. Submit a code diff/patch, shell command, plan, config, the other agent's output, or a proposed order/trade (ticker, side, size, account balance, thesis). Returns a structured verdict (approve / approve_with_concerns / reject), issues ranked by severity, suggested fixes, and alternatives — you (the agent) read it and proceed automatically on a non-reject verdict. This is NOT a human-approval step: it's an automated second opinion, advisory, never blocks, no human in the loop — you stay fully autonomous and decide. Capital-scale-aware. Model-agnostic. Built and dogfooded daily by our own autonomous fleet (the same gate we run our own important decisions through). A self-building known-bad-address registry (GET /review/known-bad, free, no auth) forces a byte-reproducible reject — independent of the judgment model — on any address a prior real verdict already rejected; not an LLM-only judgment call end to end. The part only we have: the verdict is provably committed BEFORE the outcome it's graded against — recomputable from public data, no TEE, no trusted scorer. Verify-then-pay proves the work happened; we prove the judgment came first.

NameTypeReqDescription
action_bindingobjectOptional: the exact real-world action this verdict authorizes — tool identity, materialized (not templated) arguments, and the id of the agent that will execute it, e.g. {'tool': 'place_order', 'agen…
artifactstringyesThe artifact to review: unified diff / patch, shell command, plan, config, analysis, agent output, or raw text
artifact_typestringType of artifact. 'code_diff' or 'patch' triggers deep code review. 'plan' for architecture/strategy. 'trade' triggers the capital-scale-aware risk-manager review of a proposed entry/exit. 'onchain_a…
concernsstringSpecific things to check (e.g. 'production safety', 'edge cases in trading logic', 'regulatory risk')
confidentiality_tierstringWhich privacy/evidentiary tradeoff this verdict should use, only meaningful with sign=true. 'hash_only' (default): the proof carries only artifact_hash, raw content never disclosed — strongest privac…
contextstringWhat you are trying to accomplish, why now, success criteria
disclosed_summarystringOnly used when confidentiality_tier='partial_disclosure'. A real, human-readable description of the reviewed artifact/decision you're choosing to make public — bound raw into decision_ref. Ignored fo…
external_evidencearrayOptional (v17, 2026-09-10): third-party evidence this judgment relied on — e.g. a tool-reliability registry's own historical PASS/FAIL record, worked out live with arian-gogani/nobulex-registry#1. Ar…
include_trading_statebooleanSentinel mode: inject live Sovereign Earner state (equity, regime, open position, PnL) for trading-related reviews. Highly recommended for any trading or risk decision.
intended_audiencestringOptional: declare who/what this verdict is intended for (your own DID, endpoint URL, or gateway identifier). Bound into decision_ref so it can't be silently stripped or altered once issued. NOT indep…
intended_verifierstringOptional: a CAIP-10 string naming the specific on-chain verifier/gate this verdict is meant to be checked against, e.g. 'eip155:8453:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432'. Bound into decision_r…
related_proof_eventobjectOptional: if the artifact being reviewed IS another party's already-signed verdict proof (a verdict-of-verdict re-review), pass that proof's full signed event ({id, pubkey, created_at, kind, tags, co…
request_capture_refstringOptional: a requester-controlled commitment (a hash/id you generated and can independently prove existed at request-time) that this artifact was submitted for review — the captured-admission-v0 revie…
severity_thresholdstringMinimum severity to report
signbooleanReturn a PORTABLE SIGNED proof of this verdict (binds verdict + artifact hash + our pubkey), including a content-addressed decision_ref = sha256(JCS({artifact_hash, artifact_type, policy_version, ver…

No output schema declared.

{"artifact":"systemctl restart my-trading-bot.service \u0026\u0026 curl -X POST https://api.exchange.com/v3/order -d '{\"side\":\"buy\",\"qty\":100000}'","artifact_type":"shell_command","concerns":"Is the order-of-operations safe? What can go wrong between restart and the order?","context":"About to deploy a tuned config and immediately open a 100k-sat position on the exchange","severity_threshold":"high"}
seller_intel ~153

x402 Bazaar SELLER INTELLIGENCE no other seller offers. Pass a buyer {wallet} → its on-chain behavior (catalog-walker vs real-customer verdict, total USDC spend, distinct sellers, the sellers winning its money, daily crawl cadence). Or pass your {resource}/{domain} → a DISCOVERABILITY audit (your exact CDP-catalog offset + freshness, how the recency-ranked depth-first daily crawl finds listings, why you're buried, the honest levers). Recomputable from public Base RPC + the CDP catalog.

NameTypeReqDescription
resourcestringYour resource URL / domain (discoverability audit)
walletstringBuyer 0x… Base address (behavior analysis)

No output schema declared.

No examples provided.

signals ~130

Live Hyperliquid derivatives signals (facts-only, non-advice): per-coin funding rate + 24h funding-delta, basis vs oracle, open interest (coins+USD), realized vol, 24h volume, and the vol-expansion regime read our own trading research is grounded in (std(close[-20:])/std(close[-100:]), expansion ≥1.3). Multi-coin (BTC/ETH/SOL/XRP) + BTC DVOL. The same venue we trade on.

NameTypeReqDescription
coinsarrayCoins for the set (default BTC/ETH/SOL/XRP)

No output schema declared.

No examples provided.

validate ~350

EdgeProof — paid backtest reality-check. Submit a strategy's realized returns (or trade rows) — NOT the strategy itself — and get a verdict: likely_real / borderline / overfit_or_noise. Scored with the Deflated Sharpe Ratio (haircut for the number of variants tried), a sign-flip permutation test against a coin-flip null, and purged k-fold out-of-sample decay. Include 'coin' and 'ts'/'timestamp' on each trade row to also get a concentration jackknife (does the total sign flip once you exclude the single best trade or single dominant coin) and a BTC-regime overlay (does the sign differ inside vs outside a BTC melt-up window) under a 'concentration_and_regime' key — the same mechanical audit this platform's own trading tapes are held to. Inputs are not retained beyond a redacted audit hash.

NameTypeReqDescription
agent_idstringOptional caller agent ID
k_foldsinteger
n_permsinteger
n_trialsintegerHow many strategy variants/params you tried before selecting this one. Be honest — more trials = bigger Deflated-Sharpe haircut.
periods_per_yearnumberOptional, for annualized-Sharpe display only.
returnsarrayPer-trade (or per-period) realized returns.
tradesarrayAlternative to 'returns': rows with a return field (ret/pnl/net_bps) and optional 'coin'/'ts'/'entry'/'exit' fields.
trial_sharpesarrayOptional: Sharpes of all variants tried → exact DSR variance.

No output schema declared.

No examples provided.

verify_proof ~526

CALL THIS WHEN another agent hands you output and claims it was verified by invinoveritas. Pass the signed proof `event` they gave you; this confirms — WITHOUT trusting that agent OR us — that invinoveritas really issued that verdict, by recomputing the Nostr event id, checking the schnorr signature, and confirming the pubkey is our published key. Optionally pass expect_artifact_hash (sha256 of the output you received) to confirm the proof covers THAT exact artifact, not a different one. If you only have the bare event_id (not the full event — e.g. it was pasted into a reply without created_at/kind/tags/content), pass event_id instead and we fetch the durably-stored full event server-side before verifying. Returns {valid, checks{id_integrity,signature_valid,issued_by_invinoveritas}, proof_payload}. This is the agent-to-agent trust handshake: refuse to act on unverified output, demand a proof, verify it here. Free, no auth — and you can run the same NIP-01 check yourself.

NameTypeReqDescription
eventobjectThe signed proof event {id,pubkey,created_at,kind,tags,content,sig} the counterparty handed you (from a /prove or /review sign=true response).
event_idstringAlternatively, the Nostr event id alone (from a /review sign=true, /prove, or /witness proof) — fetches the durably-stored full event, independent of relay retention, and verifies it.
expect_artifact_hashstringOptional sha256 hex of the output you received — asserts the proof is ABOUT that exact artifact.
expect_intended_verifierstringOptional (added 2026-08-16) — asserts the proof's declared intended_verifier matches you, the consumption-identity check alongside expect_artifact_hash's content-identity check. A match confirms the…
proof_idstringAlternatively, a stored attestation proof_id to fetch + verify.
verifier_signaturestringOptional (added 2026-08-16) — an EIP-191 personal_sign signature over 'invinoveritas-verify-proof:<event_id>', signed by the key controlling the address in expect_intended_verifier (eip155 CAIP-10 na…

No output schema declared.

No examples provided.

witness ~165

Anchor a THIRD PARTY's exact claim bytes, unmodified and unjudged. Distinct from review (which always runs OUR verdict) and prove (which proves our own audited actions): witness is pure notarization — 'we received and timestamped this, attributed to source X', not 'we agree with it'. The proof carries your body verbatim + its hash, notes that source is self-declared, and verifies via verify_proof (free) or offline NIP-01. Lets two independent verifiers compose a joint artifact where each claim stays separately attributable.

NameTypeReqDescription
bodystringyesThe exact claim to anchor, byte-for-byte (max 16000 chars)
sourcestringyesWho this claim is attributed to (self-declared, NOT verified by us)

No output schema declared.

No examples provided.

workspace_delete ~48

Delete a file or directory from your persistent workspace. Free. Use responsibly.

NameTypeReqDescription
agent_idstringyesYour agent identifier
pathstringyesRelative path inside the workspace to delete

No output schema declared.

No examples provided.

workspace_list ~71

List files and directories in your persistent execution workspace (created with use_workspace=true on execute calls). Extremely useful for multi-step coding, data work, and repo-based agents. Free.

NameTypeReqDescription
agent_idstringyesYour agent identifier
pathstringRelative path inside the workspace (default: root)

No output schema declared.

No examples provided.

workspace_status ~46

Get basic status of your persistent workspace (total size, file count, last modified). Very useful before deciding to clean up. Free.

NameTypeReqDescription
agent_idstringyesYour agent identifier

No output schema declared.

No examples provided.

Common questions

What is the com.babyblueviper/invinoveritas MCP server?

com.babyblueviper/invinoveritas is an MCP server listed in the public MCP registry as com.babyblueviper/invinoveritas. AI-agent verifier: verdict committed before the outcome graded against it; /review, /ledger. This page covers its hosted endpoint (https://api.babyblueviper.com/mcp).

Is the com.babyblueviper/invinoveritas MCP server safe to use?

com.babyblueviper/invinoveritas scores 81 out of 100 on VerifyMCP. 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 com.babyblueviper/invinoveritas MCP server expose?

com.babyblueviper/invinoveritas exposes 31 tools: reason, decision, review, signals, markets_act, and 26 more. Their descriptions and schemas cost roughly 6,447 tokens of context every time the server is loaded.

Does the com.babyblueviper/invinoveritas MCP server require authentication?

No. We connected to com.babyblueviper/invinoveritas without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.babyblueviper/invinoveritas MCP server still maintained?

com.babyblueviper/invinoveritas is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.