_ registry / mcp streamable-http · checked 53m ago

synproof-syntropy

https://api.synproof.ai

Registry code: e055db5d710ebf6a

api record

Synproof's Syntropy 5-sieve dialectical verification engine and Small Worlds axiom library.

from a public catalogue that lists it, not from the operator

endpoint
https://api.synproof.ai/v1/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is synproof-syntropy live?
Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
Is synproof-syntropy free to use?
Yes — the hub reached it with no key and no payment.
What tools does synproof-syntropy have?
6 tools: syntropy_fork_world, syntropy_verify, syntropy_ingest_axioms, syntropy_get_world_axioms, syntropy_get_onboarding_guide, syntropy_list_worlds.
Is synproof-syntropy safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
194ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
2 open 4 never probed 2 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • syntropy_get_onboarding_guide open 53m ago

    Return the complete interactive Synproof Syntropy Customer Implementation & Onboarding Skill (SKILL.md). Call this tool whenever the user asks to integrate, set up, or connect Syntropy into their project so you know which questions to ask (ground-truth sources, max_failures iterations, on_refuted behavior, API keys) and which SDK/Proxy code templates to apply.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • syntropy_list_worlds open 53m ago

    List available public and official verified Small Worlds (@domain:tag) in the Synproof Syntropy Library.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "domain": {
          "type": "string",
          "description": "Optional domain filter (e.g. 'pravo', 'law', 'medicine', 'physics', 'finance')."
        },
        "search": {
          "type": "string",
          "description": "Optional keyword search query."
        }
      }
    }
    arguments 13 lines
  • syntropy_fork_world unknown never probed

    Create an isolated private fork of a public Small World so custom rules can be ingested without altering public axioms.

    mcp-tool

    {
      "type": "object",
      "required": [
        "world_id_or_handle"
      ],
      "properties": {
        "title": {
          "type": "string",
          "description": "Title for the new private fork."
        },
        "world_id_or_handle": {
          "type": "string",
          "description": "Source Small World handle or ID to fork."
        }
      }
    }
    arguments 16 lines
  • syntropy_verify unknown never probed

    Put a falsifiable claim (thesis), contract clause, scientific hypothesis, or AI output on formal adversarial trial against explicit ground-truth axioms and/or a Small World (@domain:tag) using Synproof's 5-sieve Syntropy dialectical engine. Returns a deterministic CONFIRMED or REFUTED verdict, winning thesis, refuting argument, and triggered axioms.

    mcp-tool

    {
      "type": "object",
      "required": [
        "thesis"
      ],
      "properties": {
        "world": {
          "type": "string",
          "description": "Optional Small World handle(s) such as '@pravo:obcansky-zakonik-cz', '@law:insolvency-code', '@law:contract-act', or '@law:brrd-isda'."
        },
        "thesis": {
          "type": "string",
          "description": "The specific, declarative claim to put on trial."
        },
        "model_name": {
          "type": "string",
          "default": "gemini-2.5-flash",
          "description": "Underlying model ('gemini-2.5-flash', 'gemini-2.5-pro', 'anthropic/claude-3.5-sonnet', 'deepseek/deepseek-r1')."
        },
        "max_failures": {
          "type": "integer",
          "default": 3,
          "description": "Sceptical exhaustion limit (number of failed attack attempts required to confirm, 1-10)."
        },
        "initial_axioms": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional list of explicit ground-truth axioms that strictly override model priors."
        },
        "enable_research": {
          "type": "boolean",
          "default": true,
          "description": "Whether to enable external academic/statutory research tools during debate."
        }
      }
    }
    arguments 38 lines
  • syntropy_ingest_axioms unknown never probed

    Extract and synchronize atomic axioms from raw text or a JSON record into a Small World via Axiomat with deduplication and conflict resolution.

    mcp-tool

    {
      "type": "object",
      "required": [
        "world_id_or_handle"
      ],
      "properties": {
        "text": {
          "type": "string",
          "description": "Raw regulatory, contractual, or policy text to compile into atomic axioms."
        },
        "payload": {
          "type": "object",
          "description": "Optional structured JSON/database record to compile into axioms."
        },
        "on_conflict": {
          "enum": [
            "flag",
            "replace",
            "keep"
          ],
          "type": "string",
          "default": "flag",
          "description": "Conflict resolution policy when new axioms contradict existing ones."
        },
        "source_reference": {
          "type": "string",
          "description": "Citation or source identifier for the ingested axioms."
        },
        "world_id_or_handle": {
          "type": "string",
          "description": "Target Small World handle or UUID."
        }
      }
    }
    arguments 34 lines
  • syntropy_get_world_axioms unknown 53m ago

    Retrieve all atomic ground-truth axioms and metadata for a given Small World handle or ID.

    mcp-tool

    {
      "type": "object",
      "required": [
        "world_id_or_handle"
      ],
      "properties": {
        "world_id_or_handle": {
          "type": "string",
          "description": "Small World handle (e.g. '@pravo:obcansky-zakonik-cz') or UUID."
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e055db5d710ebf6a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e055db5d710ebf6a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e055db5d710ebf6a/badge.svg)](https://brick.blue/agent/e055db5d710ebf6a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.