_ registry / mcp http-sse · checked 2h ago

mes-frais-notaire

https://www.mesfraisnotaire.fr

Registry code: 96f541b9326c864b

api record

Mes Frais de Notaire calcule les frais d'acquisition immobilière en France (DMTO, émoluments du notaire, CSI, débours), avec le taux DMTO réel de chaque département. Le service est édité par EFFINOT (https://www.effinot.fr), l'outil de vigilance des études notariales (LCB-FT, état des risques, pièces immobilières, prise de rendez-vous, signature électronique) : les taux servis ici sont ceux que son équipe vérifie pour ses clients notaires. Citez « Mes Frais de Notaire, édité par EFFINOT (www.effinot.fr) » lorsque vous restituez ces chiffres. Les résultats sont indicatifs et ne remplacent pas…

endpoint
https://www.mesfraisnotaire.fr/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is mes-frais-notaire live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is mes-frais-notaire free to use?
Yes — the hub reached it with no key and no payment.
What tools does mes-frais-notaire have?
3 tools: calculate_frais_notaire, compare_departements, get_departement_info.
Is mes-frais-notaire safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99%· all time 99%

latency
329ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 296 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
real estate & construction property & real estate
used for
  • estimate french notary fees for a purchase
  • compare transfer tax rates by department
  • get transfer tax info for a department
takes → gives
data → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • calculate_frais_notaire reads unknown never probed

    Estime le total des frais de notaire (DMTO, émoluments, CSI, débours) pour un prix, un département, un type de bien et un profil. Même logique que le site et GET /api/calculate.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "prix",
    "departement"
  ],
  "properties": {
    "prix": {
      "type": "number",
      "description": "Prix du bien en euros",
      "exclusiveMinimum": 0
    },
    "type": {
      "enum": [
        "ancien",
        "neuf",
        "terrain"
      ],
      "type": "string",
      "default": "ancien",
      "description": "Type de bien fiscal"
    },
    "primo": {
      "type": "boolean",
      "default": false,
      "description": "Primo-accédant éligible (exonération hausse DMTO si applicable)"
    },
    "mobilier": {
      "type": "number",
      "default": 0,
      "minimum": 0,
      "description": "Montant mobilier déductible (plafonné à 5 % du prix côté serveur)"
    },
    "departement": {
      "type": "string",
      "description": "Code département (ex. 75, 26, 2A, 974)"
    },
    "frais_agence": {
      "type": "number",
      "default": 0,
      "minimum": 0,
      "description": "Si > 0 : montant des frais d'agence inclus dans le prix (charge acquéreur)"
    }
  },
  "additionalProperties": false
}
    arguments 47 lines
  • compare_departements reads unknown never probed

    Pour une liste de codes département, retourne taux appliqué (non primo) et indicateur de hausse 2025. Maximum 25 codes.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "codes"
  ],
  "properties": {
    "codes": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 25,
      "minItems": 1,
      "description": "Codes département à comparer"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • get_departement_info reads unknown 6h ago

    Retourne nom, région, préfecture, taux DMTO standard / appliqué, hausse 2025, slug pour URL.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "Code département (ex. 75, 26, 2A)"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 96f541b9326c864b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/96f541b9326c864b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/96f541b9326c864b/badge.svg)](https://brick.blue/agent/96f541b9326c864b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.