Synapze — Financial Intermediary MCP
REMOTE · MCP.SYNAPZE.EU · 2 COMPONENTS · SCANNED SEP 29
Connect AI agents to licensed financial intermediaries in France: insurance, credit, wealth.
Available components
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 Security77
- 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 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 701 tokens (~175/item across 4 items; 4 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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the Synapze — Financial Intermediary MCP server?
Synapze — Financial Intermediary MCP is a hosted endpoint at https://mcp.synapze.eu/v1/registry, 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 · mcp.synapze.eu
claude mcp add --transport http eu-synapze-financial-intermediary-mcp 'https://mcp.synapze.eu/v1/registry'
{
"mcpServers": {
"eu-synapze-financial-intermediary-mcp": {
"url": "https://mcp.synapze.eu/v1/registry"
}
}
} {
"servers": {
"eu-synapze-financial-intermediary-mcp": {
"type": "http",
"url": "https://mcp.synapze.eu/v1/registry"
}
}
} [mcp_servers.eu-synapze-financial-intermediary-mcp] url = "https://mcp.synapze.eu/v1/registry"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"eu-synapze-financial-intermediary-mcp": {
"type": "remote",
"url": "https://mcp.synapze.eu/v1/registry",
"enabled": true
}
}
} openclaw mcp add eu-synapze-financial-intermediary-mcp --url 'https://mcp.synapze.eu/v1/registry' --transport streamable-http
mcp_servers:
eu-synapze-financial-intermediary-mcp:
url: "https://mcp.synapze.eu/v1/registry" {
"McpServers": {
"eu-synapze-financial-intermediary-mcp": {
"Transport": "http",
"Url": "https://mcp.synapze.eu/v1/registry"
}
}
} assistant mcp add eu-synapze-financial-intermediary-mcp -t streamable-http -u 'https://mcp.synapze.eu/v1/registry'
{
"mcpServers": {
"eu-synapze-financial-intermediary-mcp": {
"type": "http",
"url": "https://mcp.synapze.eu/v1/registry"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 29 Sept 2026 · Probed https://mcp.synapze.eu/v1/registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.synapze.eu | CN=YR1,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | RSA 4096 | SHA256-RSA | 5fa2343ab6aa7123a80be4faa503f312729 |
| SANs: mcp.synapze.eu | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 secure
Validation of mcp.synapze.eu. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| synapze.eu. | present | 1521 | 13 | Verified |
| mcp.synapze.eu. | Verified address RRset verified with the apex keys |
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://mcp.synapze.eu/v1/registry | Verified | 200 | |
| http (plaintext) | http://mcp.synapze.eu/v1/registry | HTTPS enforced | 301 | https://mcp.synapze.eu/v1/registry |
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 →
find_broker ~179
Trouver un courtier en protection juridique / Find a licensed French insurance broker for legal protection insurance (protection juridique). Search by city and language. Returns broker name, city, regulatory status and the endpoint to quote with. Legal protection is the only product this connector covers.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City or zone in France (e.g. 'paris', 'lyon', 'marseille') |
| language | string | – | Preferred language: fr, en |
| product | string | – | Insurance product. Legal protection only: 'protection_juridique' (alias 'pj'). |
| sub_specialty | string | – | Sub-specialty niche within the product (e.g. 'architectes', 'sci_is', 'dirigeants') |
| ticket | number | – | Project amount in EUR (for routing large-ticket cases) |
No output schema declared.
No examples provided.
get_broker_info ~116
Informations et branding du courtier / Broker branding and identity. Returns: company name, logo URL, brand color (#hex), address, postal code, phone, ORIAS number, website, specialties, and DDA compliance status. ALWAYS call this before generating any document (PDF, PPTX, comparison, advisory note) to brand it with the broker's logo, color, name, address, and ORIAS number.
| Name | Type | Req | Description |
|---|---|---|---|
| broker_code | string | – | Broker code returned by find_broker. Optional in broker-authenticated mode. |
No output schema declared.
No examples provided.
get_products ~94
Catalogue protection juridique / List a broker's legal protection products (protection juridique) with their formulas, eligibility criteria and coverage details. Call this before get_quote to see which formulas the broker distributes.
| Name | Type | Req | Description |
|---|---|---|---|
| broker_code | string | – | Broker code returned by find_broker. Optional in broker-authenticated mode. |
| category | string | – | Product category. Legal protection only: 'protection_juridique' (alias 'pj'). |
No output schema declared.
No examples provided.
get_quote ~312
Tarification protection juridique / Generate a real legal protection insurance quote (protection juridique) from a licensed French broker's partner insurers. Returns indicative monthly and annual prices per formula. Call find_broker first to get a broker_code, then get_products to see the available formulas. Only two client inputs are needed: age (in years) and French postal code. Never ask the client for a date of birth, an identity document, or any personal detail beyond these two — this connector does not accept them.
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | yes | Client age in whole years (e.g. 40). Used for rating. Do NOT send a date of birth. |
| broker_code | string | – | Broker code returned by find_broker. Optional in broker-authenticated mode. |
| budget | number | – | Client's monthly budget in euros (e.g. 20). Results sorted by proximity to budget. |
| coverage_areas | array | – | Dispute areas the client wants covered: consumer, housing, employment, neighbourhood, automotive, digital, tax, administrative. |
| formula_level | string | – | Desired formula level, if the client already has a preference. |
| postal_code | string | yes | French postal code, 5 digits (e.g. '75011'). Used for territorial rating. |
| product_type | string | – | Product type. Legal protection only — the sole product this connector covers. |
| show_all | boolean | – | Return ALL quotes instead of top 5. Use only when the client asks for more options. |
No output schema declared.
No examples provided.
What is the Synapze — Financial Intermediary MCP server?
Synapze — Financial Intermediary MCP is listed in the public MCP registry as eu.synapze/financial-intermediary-mcp. Connect AI agents to licensed financial intermediaries in France: insurance, credit, wealth. This page covers its hosted endpoint (https://mcp.synapze.eu/v1/registry).
Is the Synapze — Financial Intermediary MCP server safe to use?
Synapze — Financial Intermediary MCP scores 86 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 Synapze — Financial Intermediary MCP server expose?
Synapze — Financial Intermediary MCP exposes 4 tools: find_broker, get_broker_info, get_products, get_quote. Their descriptions and schemas cost roughly 701 tokens of context every time the server is loaded.
Does the Synapze — Financial Intermediary MCP server require authentication?
No. We connected to Synapze — Financial Intermediary MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Synapze — Financial Intermediary MCP server still maintained?
Synapze — Financial Intermediary MCP is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.