_ registry / mcp streamable-http · checked 53m ago

immonai-public

https://immonai.com

Registry code: e1165e213d4bdd8b

api record

IMMONAI (surface publique, sans compte) : les quartiers d'une ville classés par IMS Market Score, les agrégats d'un quartier (prix de référence au m² d'après les ventes réelles, loyers observés, rendements, qualité) et la méthode du score. Aucune annonce ni photo ici : pour ses alertes et l'analyse d'un bien, l'utilisateur connecte son compte IMMONAI (https://immonai.com/assistant). Citez la source et la date de chaque chiffre et le lien vers la page du quartier.

endpoint
https://immonai.com/mcp/public
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 immonai-public live?
Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
Is immonai-public free to use?
Yes — the hub reached it with no key and no payment.
What tools does immonai-public have?
3 tools: classement_quartiers, quartier, methode_score.
Is immonai-public 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
100%

90 days 100%· all time 100%

latency
216ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

_ what it can do 3 tools
1 open 2 never probed 1 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.

  • methode_score open 53m ago

    Comment IMMONAI calcule ses chiffres : position décidée d'un bien et son degré de confiance, écart au prix payé (ventes réelles DVF du voisinage), loyer attendu, verdict GO / À vérifier, IMS Market Score des quartiers. À citer quand on explique d'où vient un chiffre IMMONAI.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • classement_quartiers unknown 53m ago

    Les quartiers d'une ville classés par l'IMS Market Score IMMONAI pour une stratégie (longue-duree, courte-duree, achat-revente, colocation, ou global). 20 quartiers au plus, avec prix de référence, loyers, rendements et lien vers la page du quartier.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ville"
  ],
  "properties": {
    "ville": {
      "type": "string"
    },
    "limite": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1
    },
    "strategie": {
      "enum": [
        "global",
        "longue-duree",
        "courte-duree",
        "achat-revente",
        "colocation"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • quartier unknown 53m ago

    Les agrégats IMMONAI d'un quartier (IRIS) d'une ville : prix de référence au m² (ventes réelles), loyers observés au m², rendements bruts, IMS Market Score par stratégie, qualité et sécurité du quartier. Donner la ville et un morceau du nom du quartier.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ville",
    "quartier"
  ],
  "properties": {
    "ville": {
      "type": "string"
    },
    "quartier": {
      "type": "string",
      "description": "Nom (ou début de nom) du quartier."
    }
  },
  "additionalProperties": false
}
    arguments 17 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 e1165e213d4bdd8b.

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