_ registry / mcp streamable-http · checked 3h ago

aucadastre

https://aucadastre.fr

Registry code: 6f38bbcacf57e021

api record

Aucadastre repond a quatre questions sur une adresse en France : tout ce que les sources publiques

disent d'une adresse (la parcelle cadastrale et sa contenance, le zonage d'urbanisme et ce qu'on peut y

endpoint
https://aucadastre.fr/mcp
protocol
streamable-http ·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 aucadastre live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is aucadastre free to use?
Yes — the hub reached it with no key and no payment.
What tools does aucadastre have?
4 tools: get_french_building_permits, get_french_commune_facts, get_french_parcel, get_french_address_facts.
Is aucadastre 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.7%· all time 99.7%

latency
1,078ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 294 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • get public facts about a french address
  • look up a cadastral parcel
  • list building permits in a commune
  • get property prices for a commune
takes → gives
text → data
tools
4 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 4 tools
4 never probed 0 of 4 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.

  • get_french_building_permits reads unknown 7h ago

    Les permis de construire, d'amenager, de demolir et les declarations prealables delivres dans une commune, tels que la commune les declare au ministere (fichier Sitadel) : date, nature, adresse des travaux, parcelle, logements et surface crees, etat du chantier, demandeur quand c'est une personne morale. Les 500 plus recents ; l'API pagine le reste.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code_insee"
      ],
      "properties": {
        "code_insee": {
          "type": "string",
          "pattern": "^[0-9][0-9AB][0-9]{3}$",
          "description": "Code INSEE de la commune, cinq caracteres, par exemple 94081 (Vitry-sur-Seine)."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_french_commune_facts reads unknown 7h ago

    Une commune francaise : ses voies adressees, le prix median au metre carre du dernier millesime, le loyer d'annonce au metre carre, le taux de taxe fonciere et son evolution depuis 2020, le document d'urbanisme opposable, la zone A/B/C du marche du logement, la part des locaux raccordables a la fibre, les risques communaux, la delinquance enregistree face au departement et a la France (SSMSI), l'eau du robinet (dernier controle sanitaire, analyses de douze mois, PFAS). Meme texte que le jumeau .md de la page de commune. Paris, Marseille et Lyon renvoient a leurs arrondissements.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code_insee"
      ],
      "properties": {
        "code_insee": {
          "type": "string",
          "pattern": "^[0-9][0-9AB][0-9]{3}$",
          "description": "Code INSEE de la commune, cinq caracteres, par exemple 94081 (Vitry-sur-Seine)."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_french_parcel reads unknown 7h ago

    Une parcelle par son identifiant a quatorze caracteres (code INSEE, prefixe, section, numero, par exemple 940810000E0107) : sa contenance, sa commune, et la voie la plus proche de son centre, dont le jumeau porte tout le reste. Le proprietaire n'y est pas : ceux qui sont des personnes morales se lisent dans le jumeau de la voie, un particulier nulle part.

    mcp-tool

    {
      "type": "object",
      "required": [
        "parcel_id"
      ],
      "properties": {
        "parcel_id": {
          "type": "string",
          "pattern": "^[0-9][0-9AB][0-9]{3}[0-9A-Z]{3}[0-9A-Z]{2}[0-9]{4}$",
          "description": "L'identifiant de la parcelle, quatorze caracteres, par exemple 940810000E0107."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_french_address_facts reads unknown never probed

    Les proprietaires personnes morales de l'adresse (SCI, societes, bailleurs sociaux, collectivites, Etat, avec SIREN et date de situation, jamais un particulier), la parcelle cadastrale d'une adresse francaise et sa contenance, le zonage d'urbanisme et les destinations autorisees, les prescriptions et servitudes, les risques (argile, sismicite, radon, catastrophes naturelles, installations classees), le terrain (altitude, pente, solaire), les permis de construire rattaches a la voie, les ventes des cinq derniers millesimes, au numero demande l'historique de sa parcelle (ventes, autorisations, naissance au plan depuis 2017), les diagnostics energetiques, les ecoles et entreprises autour. Meme texte que le jumeau .md de la page de voie. L'adresse se donne en toutes lettres ; sans numero, la reponse vaut au point de reference de la voie.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "address": {
          "type": "string",
          "minLength": 3,
          "description": "L'adresse en toutes lettres, par exemple « 60 rue Pasteur, Vitry-sur-Seine ». Le numero est facultatif."
        }
      },
      "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 6f38bbcacf57e021.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6f38bbcacf57e021/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/6f38bbcacf57e021/badge.svg)](https://brick.blue/agent/6f38bbcacf57e021?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
80%

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.