MCP.so
Sign In

Invinoveritas

@babyblueviper1

About Invinoveritas

The verification layer for autonomous agents — a neutral, capital-scale-aware verdict before an irreversible action (review), a signed portable proof after (prove), and a public, on-chain-verifiable track record anyone can check without trusting us (ledger / verify-proof). Pay-pe

Basic information

Category

Other

Transports

stdio

Publisher

babyblueviper1

Submitted by

babyblueviper1

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "invinoveritas": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.babyblueviper.com/mcp"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Invinoveritas?

Invinoveritas is a verification layer for autonomous agents, providing a neutral second opinion on proposed actions and signed, checkable proofs after irreversible actions. It builds a public, auditable track record of correctness, enabling agents to trust outcomes without trusting Invinoveritas.

How to use Invinoveritas?

  1. Register via POST /register to obtain an API key (Bearer token).
  2. Include Authorization: Bearer <api_key> on /mcp or REST endpoints.
  3. Fund via /topup (Lightning) or pay per call in USDC (x402) for paid tools.

Key features of Invinoveritas

  • Neutral, capital-scale-aware verdict before an irreversible action
  • Portable signed verdict proofs for external verification
  • Public, Nostr-anchored ledger linking each verdict to outcomes
  • Free, no-auth proof verification against published keys
  • Optional reasoning, structured decisions, code execution, and agent messaging

Use cases of Invinoveritas

  • Review a proposed action before a trading bot enters a position
  • Prove a previous verdict’s correctness with a signed proof
  • Audit an agent’s track record via the public ledger
  • Verify a proof from another agent without trusting them or Invinoveritas

FAQ from Invinoveritas

How does Invinoveritas differ from alternatives?

It gives a neutral, signed verdict and a publicly auditable track record, so judgment can be trusted without trusting the service itself.

What are the runtime or dependency requirements?

Only a registration endpoint and an API key; the service handles reasoning, execution, and memory.

Where is the ledger data stored?

Every verdict is published on Nostr and linked to on-chain outcomes, building a public record.

What transports and authentication are supported?

Uses Bearer token auth over REST; paid calls support L402 (Lightning) and x402 (USDC on Base).

Are there known limits?

The README does not mention any specific limits beyond requiring payment for certain tools.

Comments

More Other MCP servers