Confirme, by Synapse MCP server
com.synapseconnexion.www/confirmewww.synapseconnexion.comstreamable-httpv1.0.0Scanned
Did it really happen? Independent signed receipts for AI agents: page, domain, email, heartbeat.
6 tools: 6 change things.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Confirme, by Synapse MCP server can do
The Confirme, by Synapse MCP server is published by www.synapseconnexion.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (6 tools: confirme_page, confirme_domaine, confirme_courriel, confirme_battement and 2 more), but cannot delete data. None of its tools only reads.
4 tools bring in text other people can write (confirme_page, confirme_domaine, confirme_courriel and 1 more); 1 tool can send data out of your system (confirme_page).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.0.0.
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.
6 tools
Changes things 6Claude Code: ask
confirme_battementHeartbeat: record that your scheduled or recurring task just ran successfully, under a secret key you choose.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 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.
Annotations the server declares
- title: Confirme · battement
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
confirme_courrielCan this email address receive mail?Reads text others writeNo 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.
Description, as the server wrote it 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.
Annotations the server declares
- title: Confirme · courriel
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
confirme_domaineDoes this domain exist, who registered it, when does it expire, which DNS (A, MX, NS, SPF, DMARC)?Reads text others writeNo 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.
Description, as the server wrote it 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.
Annotations the server declares
- title: Confirme · domaine
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
confirme_pageIs this web page really online right now?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 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).
Annotations the server declares
- title: Confirme · page
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
confirme_sacGet 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.1 finding
Why it is in this group
- The description's first verb is "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "confirme_sac" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Confirme · sac de jujubes
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
confirme_tacheDid my scheduled task really run in the last N seconds?Reads text others writeNo 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.
Description, as the server wrote it 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.
Annotations the server declares
- title: Confirme · tâche
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
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 out1
- 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.
Looked at Nov 20, 2026, 18:48 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
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.synapseconnexion.com/ia/mcp: tools/list returned 6 tools to an anonymous client, including confirme_page (write), confirme_domaine (write), confirme_courriel (write), confirme_battement (write), confirme_tache (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
- Warnconfirme_sac
The server marks "confirme_sac" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "get": a word for reading.
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.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http confirme https://www.synapseconnexion.com/ia/mcpclaude mcp add --transport http confirme https://www.synapseconnexion.com/ia/mcpRun 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.
{
"permissions": {
"allow": [],
"ask": [
"mcp__confirme__confirme_page",
"mcp__confirme__confirme_domaine",
"mcp__confirme__confirme_courriel",
"mcp__confirme__confirme_battement",
"mcp__confirme__confirme_tache",
"mcp__confirme__confirme_sac"
],
"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 confirme. Review it before you use it.
Capability tags behind 4 rules
- mcp__confirme__confirme_page untrusted-input, outbound
- mcp__confirme__confirme_domaine untrusted-input
- mcp__confirme__confirme_courriel untrusted-input
- mcp__confirme__confirme_tache untrusted-input
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.synapseconnexion.www/confirme/verify?hash=17e8a22a1a1a491590cdff419aa691b5cdda99d14871aaf01d89f6670df60e8c" | jq -e '.changed == false'Pinned hash 17e8a22a1a1a, from Nov 11, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.synapseconnexion.www/confirme/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.synapseconnexion.www/confirme)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:06 UTC.
Confirme, by Synapse MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Confirme, by Synapse MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Confirme, by Synapse MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Confirme, by Synapse MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Confirme, by Synapse MCP server have?
- 6 tools: 6 write. confirme_page, confirme_domaine, confirme_courriel, confirme_battement, confirme_tache and confirme_sac.
Does the Confirme, by Synapse MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Confirme, by Synapse MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): confirme_page.
Has the Confirme, by Synapse MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.