Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Synapze — Financial Intermediary MCP

REMOTE · MCP.SYNAPZE.EU · 2 COMPONENTS

Connect AI agents to licensed financial intermediaries in France: insurance, credit, wealth.

0 this week 24 Trust /100

Last scanned (19 hours ago)

Scores higher than 10% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security60
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 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
  • 16 Oct 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 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 0
    • 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
Diagnostics

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 21 Nov 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. DS published 35926 8 Verified
synapze.eu. DS published 1521 13 Verified
mcp.synapze.eu. Verified address RRset verified with the apex keys
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 502

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 HTTP error 502
http (plaintext) http://mcp.synapze.eu/v1/registry HTTPS enforced 301 https://mcp.synapze.eu/v1/registry
MCP tools · 4 exposed · ~701 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
citystring–City or zone in France (e.g. 'paris', 'lyon', 'marseille')
languagestring–Preferred language: fr, en
productstring–Insurance product. Legal protection only: 'protection_juridique' (alias 'pj').
sub_specialtystring–Sub-specialty niche within the product (e.g. 'architectes', 'sci_is', 'dirigeants')
ticketnumber–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.

NameTypeReqDescription
broker_codestring–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.

NameTypeReqDescription
broker_codestring–Broker code returned by find_broker. Optional in broker-authenticated mode.
categorystring–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.

NameTypeReqDescription
ageintegeryesClient age in whole years (e.g. 40). Used for rating. Do NOT send a date of birth.
broker_codestring–Broker code returned by find_broker. Optional in broker-authenticated mode.
budgetnumber–Client's monthly budget in euros (e.g. 20). Results sorted by proximity to budget.
coverage_areasarray–Dispute areas the client wants covered: consumer, housing, employment, neighbourhood, automotive, digital, tax, administrative.
formula_levelstring–Desired formula level, if the client already has a preference.
postal_codestringyesFrench postal code, 5 digits (e.g. '75011'). Used for territorial rating.
product_typestring–Product type. Legal protection only — the sole product this connector covers.
show_allboolean–Return ALL quotes instead of top 5. Use only when the client asks for more options.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http eu-synapze-financial-intermediary-mcp 'https://mcp.synapze.eu/v1/registry'
Common questions

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 24 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?

Its publisher declares no required credentials for Synapze — Financial Intermediary MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Synapze — Financial Intermediary MCP server?

VerifyMCP ran 5 checks on Synapze — Financial Intermediary MCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Synapze — Financial Intermediary MCP: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.