io.github.macek166/syntropy-mcp
REMOTE · API.SYNPROOF.AI
Synproof's Syntropy 5-sieve dialectical verification engine and Small Worlds axiom library.
Available components
Last scanned (20 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 4 Nov 2026.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 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
- Context-footprint check failed: tool/resource definitions use about 704 tokens (~117/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 66
First indexed and scored.
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 4 Nov 2026 · Probed https://api.synproof.ai/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=synproof.ai | CN=YE1,O=Let's Encrypt,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 502841a74a171292f9762e859421b953775 |
| SANs: *.synproof.ai, synproof.ai | ||||||
| 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.synproof.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| synproof.ai. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.synproof.ai/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.synproof.ai/v1/mcp | HTTPS enforced | 301 | https://api.synproof.ai/v1/mcp |
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 →
syntropy_fork_world ~65
Create an isolated private fork of a public Small World so custom rules can be ingested without altering public axioms.
| Name | Type | Req | Description |
|---|---|---|---|
| title | string | – | Title for the new private fork. |
| world_id_or_handle | string | yes | Source Small World handle or ID to fork. |
No output schema declared.
No examples provided.
syntropy_get_onboarding_guide ~90
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
syntropy_get_world_axioms ~64
Retrieve all atomic ground-truth axioms and metadata for a given Small World handle or ID.
| Name | Type | Req | Description |
|---|---|---|---|
| world_id_or_handle | string | yes | Small World handle (e.g. '@pravo:obcansky-zakonik-cz') or UUID. |
No output schema declared.
No examples provided.
syntropy_ingest_axioms ~132
Extract and synchronize atomic axioms from raw text or a JSON record into a Small World via Axiomat with deduplication and conflict resolution.
| Name | Type | Req | Description |
|---|---|---|---|
| on_conflict | string | – | Conflict resolution policy when new axioms contradict existing ones. |
| payload | object | – | Optional structured JSON/database record to compile into axioms. |
| source_reference | string | – | Citation or source identifier for the ingested axioms. |
| text | string | – | Raw regulatory, contractual, or policy text to compile into atomic axioms. |
| world_id_or_handle | string | yes | Target Small World handle or UUID. |
No output schema declared.
No examples provided.
syntropy_list_worlds ~73
List available public and official verified Small Worlds (@domain:tag) in the Synproof Syntropy Library.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Optional domain filter (e.g. 'pravo', 'law', 'medicine', 'physics', 'finance'). |
| search | string | – | Optional keyword search query. |
No output schema declared.
No examples provided.
syntropy_verify ~280
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.
| Name | Type | Req | Description |
|---|---|---|---|
| enable_research | boolean | – | Whether to enable external academic/statutory research tools during debate. |
| initial_axioms | array | – | Optional list of explicit ground-truth axioms that strictly override model priors. |
| max_failures | integer | – | Sceptical exhaustion limit (number of failed attack attempts required to confirm, 1-10). |
| model_name | string | – | Underlying model ('gemini-2.5-flash', 'gemini-2.5-pro', 'anthropic/claude-3.5-sonnet', 'deepseek/deepseek-r1'). |
| thesis | string | yes | The specific, declarative claim to put on trial. |
| world | string | – | Optional Small World handle(s) such as '@pravo:obcansky-zakonik-cz', '@law:insolvency-code', '@law:contract-act', or '@law:brrd-isda'. |
No output schema declared.
No examples provided.
How do I install the io.github.macek166/syntropy-mcp server?
io.github.macek166/syntropy-mcp is a hosted endpoint at https://api.synproof.ai/v1/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.synproof.ai
claude mcp add --transport http macek166-syntropy-mcp 'https://api.synproof.ai/v1/mcp'
What is the io.github.macek166/syntropy-mcp server?
io.github.macek166/syntropy-mcp is listed in the public MCP registry as io.github.macek166/syntropy-mcp. Synproof's Syntropy 5-sieve dialectical verification engine and Small Worlds axiom library. This page covers its hosted endpoint (https://api.synproof.ai/v1/mcp).
Is the io.github.macek166/syntropy-mcp server safe to use?
io.github.macek166/syntropy-mcp scores 66 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 io.github.macek166/syntropy-mcp server expose?
io.github.macek166/syntropy-mcp exposes 6 tools: syntropy_verify, syntropy_list_worlds, syntropy_get_world_axioms, syntropy_fork_world, syntropy_ingest_axioms, syntropy_get_onboarding_guide. Their descriptions and schemas cost roughly 704 tokens of context every time the server is loaded.
Does the io.github.macek166/syntropy-mcp server require authentication?
No. We connected to io.github.macek166/syntropy-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.macek166/syntropy-mcp server still maintained?
io.github.macek166/syntropy-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.