IMMONAI
REMOTE · IMMONAI.COM · 2 COMPONENTS
Alertes Hunter, analyse d'un bien (écart au prix payé, loyer, verdict), quartiers classés par IMS.
Available components
Last scanned (12 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security83
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 384 tokens (~128/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 69
First indexed and scored.
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 5 Nov 2026 · Probed https://immonai.com/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=immonai.com | CN=YR2,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | RSA 2048 | SHA256-RSA | 6095447777f5a331b7f98c8926fc0bcc30b |
| SANs: immonai.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 immonai.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| immonai.com. | present | 23414 | 8 | Verified |
| immonai.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://immonai.com/mcp/public | Verified | 200 | |
| http (plaintext) | http://immonai.com/mcp/public | HTTPS enforced | 308 | https://immonai.com/mcp/public |
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 →
classement_quartiers Classement des quartiers d'une ville ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limite | integer | – | – |
| strategie | string | – | – |
| ville | string | yes | – |
No output schema declared.
No examples provided.
methode_score Méthode du score IMMONAI ~75
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quartier Un quartier : prix, loyers, tension ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| quartier | string | yes | Nom (ou début de nom) du quartier. |
| ville | string | yes | – |
No output schema declared.
No examples provided.
How do I install the IMMONAI MCP server?
IMMONAI is a hosted endpoint at https://immonai.com/mcp/public, 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 · immonai.com
claude mcp add --transport http com-immonai-immonai 'https://immonai.com/mcp/public'
What is the IMMONAI MCP server?
IMMONAI is an MCP server listed in the public MCP registry as com.immonai/immonai. Alertes Hunter, analyse d'un bien (écart au prix payé, loyer, verdict), quartiers classés par IMS. This page covers its hosted endpoint (https://immonai.com/mcp/public).
Is the IMMONAI MCP server safe to use?
IMMONAI scores 70 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 IMMONAI MCP server expose?
IMMONAI exposes 3 tools: classement_quartiers, quartier, methode_score. Their descriptions and schemas cost roughly 265 tokens of context every time the server is loaded.
Does the IMMONAI MCP server require authentication?
No. We connected to IMMONAI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the IMMONAI MCP server still maintained?
IMMONAI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.