Skip to content

invinoveritas MCP server

com.babyblueviper/invinoveritasbabyblueviper.comstreamable-httpv1.14.1Scanned

Second opinion before an irreversible agent action; signed proofs, free verify, public ledger.

10 tools: 3 do something that can't be undone, 5 change things and 2 only read.

Tools: 0 delete, 3 irreversible, 5 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 2
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the invinoveritas MCP server can do

The invinoveritas MCP server is published by babyblueviper.com, a domain the MCP Registry verified. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (payment_receipt, ledger_submit and conformance_certify) and create or change data (5 tools: review, verify_proof, verify_media, witness and 1 more), but cannot delete data. 2 tools only read.

4 tools bring in text other people can write (payment_receipt, ledger_submit, conformance_certify and 1 more); 2 tools can send data out of your system (conformance_certify and audit_agent_readiness).

The fixed checks matched 2 findings (base64-blob and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.14.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Can't be undone 3Claude Code: ask
  • conformance_certifyPublishes a verifier's current conformance grade from the public registry (conformance.json) as a permanent, signed ledger entry, labeled 'certified as of this measurement'.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "publish": a word for a change that another call does not undo.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe description's first verb is "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Publishes a verifier's current conformance grade from the public registry (conformance.json) as a permanent, signed ledger entry, labeled 'certified as of this measurement'. It records the registry's existing measurement and cannot change it. Only works for a verifier currently listed as certified. Docs: https://api.babyblueviper.com/conformance

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Publish a verifier's conformance grade
  • ledger_submitPublishes one of your own signed review proofs (from review with sign=true) as a public entry on the invinoveritas ledger.Reads text others writeNo findings

    Why it is in this group

    • The name "ledger_submit" says "submit": a word for a change.
    • The description's first verb is "publish": a word for a change that another call does not undo.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Publishes one of your own signed review proofs (from review with sign=true) as a public entry on the invinoveritas ledger. Publication is immediate and permanent: the entry is broadcast to Nostr relays and Bitcoin-timestamped. Only genuine invinoveritas-signed proofs are accepted. Docs: https://api.babyblueviper.com/ledger

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • title: Publish your verdict to the ledger
  • payment_receiptSigned receipt for one verdict-governed payment: endpoint, network, asset, max amount, payer, facilitator verdict, settlement id, denial reason, and retry state.Reads text others writeNo findings

    Why it is in this group

    • The name "payment_receipt" says "payment": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Signed receipt for one verdict-governed payment: endpoint, network, asset, max amount, payer, facilitator verdict, settlement id, denial reason, and retry state. retry_state is read from the token's authorizationState, so retrying with the same nonce cannot double-pay. Pass the signed review event and the payment args it bound; optional tx_hash. Refuses unsigned when the verdict does not verify or does not bind those args. The receipt itself checks with verify_proof. Free, no sign-in. Does not move funds. Docs: https://github.com/babyblueviper1/invinoveritas/tree/main/examples/qbtlabs-x402-verdict-gate#payment-receipt-safe-to-retry

    Annotations the server declares

    • title: Payment receipt (free)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 5Claude Code: ask
  • audit_agent_readinessAudits a public agent or API URL for verifiability: discovery files (llms.txt, MCP card, robots, sitemap), handshake endpoints, and whether presented signed proofs validate.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Audits a public agent or API URL for verifiability: discovery files (llms.txt, MCP card, robots, sitemap), handshake endpoints, and whether presented signed proofs validate. Returns a 0-100 score, a grade, ranked fixes, and a signed proof of the audit. Every result re-derives from a public fetch. Docs: https://api.babyblueviper.com/docs

    Annotations the server declares

    • title: Agent-readiness audit
    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
  • reviewIndependent verdict on a proposed action before it is taken: a code diff, shell command, deployment plan, configuration change, another agent's output, or a proposed transaction.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The input schema at properties.intended_verifier.description contains a 42-character base64 string.

      Matched text

      inputSchema.properties.intended_verifier.description: "..., e.g. 'eip155:8453:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432'. Bound into decisi..."

      What this check looks for
    Description, as the server wrote it
    Independent verdict on a proposed action before it is taken: a code diff, shell command, deployment plan, configuration change, another agent's output, or a proposed transaction. Returns approve / approve_with_concerns / reject with a confidence score, issues ranked by severity, suggested fixes and alternatives. With sign=true the verdict is returned as a signed proof that anyone can check later with verify_proof. The verdict is a reasoned second opinion, not a guarantee of outcome. Docs: https://api.babyblueviper.com/docs

    Annotations the server declares

    • title: Pre-action verdict
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
  • verify_mediaCheck whether a video, audio or image file is byte-for-byte a file a publisher registered with invinoveritas.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "Credentials".

      Matched text

      description: "...evidential states from its C2PA Content Credentials (signature/hash binding, signer trust,..."

      What this check looks for
    Description, as the server wrote it
    Check whether a video, audio or image file is byte-for-byte a file a publisher registered with invinoveritas. Pass the file's SHA-256 (compute it locally; the file is not sent). A match returns the registration: per-claim evidential states from its C2PA Content Credentials (signature/hash binding, signer trust, declared edit history, declared AI-generation labels: VERIFIED / DECLARED_ONLY / CONTRADICTED / INSUFFICIENT), any capture tier with its caveat, the signed verdict and the Bitcoin timestamp. No match means not registered, which says nothing either way about the file. A re-encoded copy has a different hash. It never asserts that content is true. Full checks of the file itself: POST /verify-media (upload, free). Free, no auth.

    Annotations the server declares

    • title: Verify media by hash (free)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • verify_proofChecks a signed invinoveritas proof without trusting whoever handed it over: recomputes the event id, checks the Schnorr signature, and confirms the signing key is invinoveritas's …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Checks a signed invinoveritas proof without trusting whoever handed it over: recomputes the event id, checks the Schnorr signature, and confirms the signing key is invinoveritas's published key. Optionally pass expect_artifact_hash (sha256 of the content you received) to confirm the proof covers that exact content. Accepts the full event, or an event_id to look up. Returns {valid, checks, proof_payload}. Free, no sign-in. Docs: https://api.babyblueviper.com/verify

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Verify a proof (free)
  • witnessTimestamps and signs a third party's exact claim, unmodified and unjudged: 'we received this text, attributed to source X, at time T', not 'we agree with it'.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Timestamps and signs a third party's exact claim, unmodified and unjudged: 'we received this text, attributed to source X, at time T', not 'we agree with it'. The source is recorded as self-declared. The resulting proof checks with verify_proof. Docs: https://api.babyblueviper.com/docs

    Annotations the server declares

    • title: Witness a third-party claim
    • readOnlyHint: false
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: false
Only reads 2Show 2 read-only tools
  • ledgerReads invinoveritas's public track record of signed verdicts, including ones that turned out wrong.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Reads invinoveritas's public track record of signed verdicts, including ones that turned out wrong. Each entry is a signed Nostr event whose id and signature can be recomputed against invinoveritas's published key; entries are append-only and Bitcoin-timestamped, so they can't be edited after the fact. No arguments returns the index; pass entry to read one. Free, no sign-in. Docs: https://api.babyblueviper.com/ledger

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Public verdict ledger (free)
  • validateStatistical reality-check of a backtest from its realized returns (or trade rows), not the strategy itself.No findings

    Why it is in this group

    • The name "validate" says "validate": a word for reading.
    Description, as the server wrote it
    Statistical reality-check of a backtest from its realized returns (or trade rows), not the strategy itself. Returns likely_real / borderline / overfit_or_noise using the Deflated Sharpe Ratio (adjusted for the number of variants tried), a sign-flip permutation test, and out-of-sample decay across purged folds. Inputs are not retained beyond a redacted audit hash. Docs: https://api.babyblueviper.com/docs

    Annotations the server declares

    • title: Backtest reality-check
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:34 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.babyblueviper.com/.well-known/oauth-protected-resource/mcp/verify
Authorization servers
https://api.babyblueviper.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (3 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.babyblueviper.com/mcp/verify: tools/list returned 10 tools to an anonymous client, including payment_receipt (irreversible), ledger_submit (irreversible), conformance_certify (irreversible), review (write), verify_proof (write) and 3 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • Warnreview

    The input schema at properties.intended_verifier.description contains a 42-character base64 string.

    Matched text

    inputSchema.properties.intended_verifier.description: "..., e.g. 'eip155:8453:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432'. Bound into decisi..."

    What this check looks for
  • The description mentions "Credentials".

    Matched text

    description: "...evidential states from its C2PA Content Credentials (signature/hash binding, signer trust,..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.14.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http invinoveritas https://api.babyblueviper.com/mcp/verify
claude mcp add --transport http invinoveritas https://api.babyblueviper.com/mcp/verify

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__invinoveritas__validate",
      "mcp__invinoveritas__ledger"
    ],
    "ask": [
      "mcp__invinoveritas__review",
      "mcp__invinoveritas__verify_proof",
      "mcp__invinoveritas__payment_receipt",
      "mcp__invinoveritas__verify_media",
      "mcp__invinoveritas__witness",
      "mcp__invinoveritas__ledger_submit",
      "mcp__invinoveritas__conformance_certify",
      "mcp__invinoveritas__audit_agent_readiness"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as invinoveritas. Review it before you use it.

Capability tags behind 4 rules
  • mcp__invinoveritas__payment_receipt untrusted-input
  • mcp__invinoveritas__ledger_submit untrusted-input
  • mcp__invinoveritas__conformance_certify untrusted-input, outbound
  • mcp__invinoveritas__audit_agent_readiness untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.babyblueviper/invinoveritas/verify?hash=9be5f92b052898af97be19030aa36a735134a6a66f87692b5fee2765d338f40a" | jq -e '.changed == false'

Pinned hash 9be5f92b0528, from Nov 10, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.babyblueviper/invinoveritas/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.babyblueviper/invinoveritas
[![Anlyon Radar](https://radar.anlyon.com/badge/com.babyblueviper/invinoveritas.svg)](https://radar.anlyon.com/servers/com.babyblueviper/invinoveritas)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:51 UTC.

invinoveritas MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the invinoveritas MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 8 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the invinoveritas MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the invinoveritas MCP server do things that cannot be undone?

Yes. 3 tools can send, pay, publish or merge: payment_receipt, ledger_submit and conformance_certify.

What tools does the invinoveritas MCP server have?

10 tools: 3 irreversible, 5 write, 2 read. payment_receipt, ledger_submit, conformance_certify, review, verify_proof, verify_media, witness, audit_agent_readiness and 2 more.

Does the invinoveritas MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the invinoveritas MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): conformance_certify and audit_agent_readiness.

Has the invinoveritas MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.