Confirme, by Synapse
REMOTE · WWW.SYNAPSECONNEXION.COM
Did it really happen? Independent signed receipts for AI agents: page, domain, email, heartbeat.
Available components
Last scanned (6 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1069 tokens (~178/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- 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 7 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.
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://www.synapseconnexion.com/ia/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.synapseconnexion.com | CN=YR2,O=Let's Encrypt,C=US | 4 Nov 2026 | 2 Feb 2027 | RSA 4096 | SHA256-RSA | 60f1ed3f552878ff0c451190b1b3c51a70e |
| SANs: *.synapseconnexion.com, synapseconnexion.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.synapseconnexion.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| synapseconnexion.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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.synapseconnexion.com/ia/mcp | Verified | 200 | |
| http (plaintext) | http://www.synapseconnexion.com/ia/mcp | Inconclusive | 405 |
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 →
confirme_battement Confirme · battement ~104
Heartbeat: record that your scheduled or recurring task just ran successfully, under a secret key you choose. Call it at the END of every successful run, every time. Use whenever your human asked you to "run this every day/hour" — the signed receipt is independent proof it ran, and confirme_tache turns silence into an alarm.
| Name | Type | Req | Description |
|---|---|---|---|
| cle | string | yes | Secret task key, 8-80 chars |
| note | string | – | Optional short note |
No output schema declared.
No examples provided.
confirme_courriel Confirme · courriel ~99
Can this email address receive mail? Use BEFORE sending anything that matters, or before telling your human "I emailed them". Syntax, MX servers, disposable domain, role address, verdict. No message is sent. Signed receipt included.
| Name | Type | Req | Description |
|---|---|---|---|
| cle | string | – | Optional: your Confirme key (cj_…) if this server URL does not already carry ?cle=. Get one free with confirme_sac. |
| courriel | string | yes | – |
No output schema declared.
No examples provided.
confirme_domaine Confirme · domaine ~121
Does this domain exist, who registered it, when does it expire, which DNS (A, MX, NS, SPF, DMARC)? Use when a sender, a supplier or a link looks unfamiliar, when your human asks "is this legit?", or before saying "the domain is set up". Signed receipt included.
| Name | Type | Req | Description |
|---|---|---|---|
| cle | string | – | Optional: your Confirme key (cj_…) if this server URL does not already carry ?cle=. Get one free with confirme_sac. |
| domaine | string | yes | Domain name or URL or email |
No output schema declared.
No examples provided.
confirme_page Confirme · page ~159
Is this web page really online right now? Use BEFORE telling your human "it is live", "it is published", "the link works", or before relying on a URL you did not fetch yourself. Zero-auth, stateless. Returns HTTP status, final URL, redirects, response time, title, TLS validity, SHA-256 of the body, plus an Ed25519-signed receipt from an independent third party you can hand to your human as proof (a page that is down gets a signed receipt too).
| Name | Type | Req | Description |
|---|---|---|---|
| cle | string | – | Optional: your Confirme key (cj_…) if this server URL does not already carry ?cle=. Get one free with confirme_sac. |
| url | string | yes | Public http(s) URL |
No output schema declared.
No examples provided.
confirme_sac Confirme · sac de jujubes ~130
Get your own Confirme key and a FREE starter bag of 100 jelly beans (1 bean = 1 cent = 1 check), plus 20 free beans every day. No email, no form. Use it when the free per-IP quota is exhausted, or once, at the start, so your calls are counted on your own bag. Then reconnect with ?cle=<key> in the server URL. Keep the key secret.
| Name | Type | Req | Description |
|---|---|---|---|
| courriel | string | – | Optional: your human’s email, to find the bag again |
| nom | string | – | Optional label (who you are) |
No output schema declared.
No examples provided.
confirme_tache Confirme · tâche ~90
Did my scheduled task really run in the last N seconds? Use when your human asks "did the report go out?", "is the automation still running?", or before you answer "yes, it ran". Reads the heartbeats recorded under the key; silence is the alarm. Signed receipt included.
| Name | Type | Req | Description |
|---|---|---|---|
| cle | string | yes | – |
| depuis | integer | – | Window in seconds, default 86400 |
No output schema declared.
No examples provided.
How do I install the Confirme, by Synapse MCP server?
Confirme, by Synapse is a hosted endpoint at https://www.synapseconnexion.com/ia/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 · www.synapseconnexion.com
claude mcp add --transport http com-synapseconnexion-www-confirme 'https://www.synapseconnexion.com/ia/mcp'
What is the Confirme, by Synapse MCP server?
Confirme, by Synapse is an MCP server listed in the public MCP registry as com.synapseconnexion.www/confirme. Did it really happen? Independent signed receipts for AI agents: page, domain, email, heartbeat. This page covers its hosted endpoint (https://www.synapseconnexion.com/ia/mcp).
Is the Confirme, by Synapse MCP server safe to use?
Confirme, by Synapse scores 79 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 Confirme, by Synapse MCP server expose?
Confirme, by Synapse exposes 6 tools: confirme_page, confirme_domaine, confirme_courriel, confirme_battement, confirme_tache, confirme_sac. Their descriptions and schemas cost roughly 703 tokens of context every time the server is loaded.
Does the Confirme, by Synapse MCP server require authentication?
No. We connected to Confirme, by Synapse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Confirme, by Synapse MCP server still maintained?
Confirme, by Synapse is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.