Real Estate Capitale MCP
REMOTE · REALESTATECAPITALE.MA
Real estate MCP server for Morocco — search, valuation, market analysis, 17 tools.
Available components
Last scanned (18 hours ago)
Scores higher than 9% of remote servers
Reachable. Last reached 24 Oct 2026.
Category CRM and Sales
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. See how to fix → View diagnostics → Fail
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.
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.
- 7 Oct 26 −51
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.63 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 4 Oct 26 +51
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 17 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.63 ▲ 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
- 24 Sept 26 −46
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.27 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 23 Sept 26 +46
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 17 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.27 ▲ functional
- 18 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 16 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 24 Oct 2026 · Probed https://realestatecapitale.ma/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=realestatecapitale.ma | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7e6be56697c562c61337964ec5b3e365 |
| SANs: realestatecapitale.ma, www.realestatecapitale.ma, *.www.realestatecapitale.ma | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of realestatecapitale.ma. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ma. | present | 3254 | 8 | Verified |
| realestatecapitale.ma. | present | 2371 | 13 | Verified |
| realestatecapitale.ma. | 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 | 530 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://realestatecapitale.ma/mcp | HTTP error | 530 | |
| http (plaintext) | http://realestatecapitale.ma/mcp | HTTPS enforced | 301 | https://realestatecapitale.ma/mcp |
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 →
create_lead ~94
Creer un lead (contact client) pour prise de rendez-vous ou demande d'information
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | number | – | ID du bien concerne (optionnel) |
| name | string | yes | Nom du contact (2-120 caracteres) |
| phone | string | yes | Telephone (8-24 caracteres, ex: 0612345678) |
| source | string | – | Source du lead (defaut: mcp) |
No output schema declared.
No examples provided.
estimate_property ~139
Estimer la valeur d'un bien immobilier (prix au m², fourchette basse/haute)
| Name | Type | Req | Description |
|---|---|---|---|
| etage | string | – | Type d'etage (optionnel) |
| etat | string | – | Etat du bien (optionnel) |
| pieces | number | – | Nombre de pieces (optionnel) |
| quartier | string | yes | Quartier (ex: Agdal, Hay Riad) |
| standing | string | – | Standing (optionnel) |
| surface | number | yes | Surface en m² |
| type | string | yes | Type de transaction |
| ville | string | – | Ville (optionnel, defaut: Rabat) |
No output schema declared.
No examples provided.
get_agency_leaderboard ~45
Classement des agences immobilieres par volume d'annonces
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Nombre d'agences (5-100, defaut: 20) |
No output schema declared.
No examples provided.
get_comparables ~40
Trouver les annonces les plus similaires a un bien donne (pour evaluation ou estimation)
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | number | yes | ID du bien de reference |
No output schema declared.
No examples provided.
get_investor_alerts ~129
Identifier les biens sous-evalues (opportunites d'investissement avec discount)
| Name | Type | Req | Description |
|---|---|---|---|
| minDiscountPct | number | – | Discount minimum en pourcentage (10-70, defaut: 15) |
| minSample | number | – | Echantillon minimum par segment (12-300, defaut: 20) |
| page | number | – | Page (defaut: 1) |
| pageSize | number | – | Resultats par page (defaut: 20, max: 100) |
| status | string | – | Filtrer par type (defaut: vente) |
No output schema declared.
No examples provided.
get_liquidity ~67
Indice de liquidite du marche par quartier (taux de rotation, stock, delai de vente)
| Name | Type | Req | Description |
|---|---|---|---|
| quartier | string | – | Quartier specifique (optionnel, tous si omis) |
| status | string | – | Filtrer par type (defaut: all) |
No output schema declared.
No examples provided.
get_listing ~32
Obtenir le détail complet d'un bien immobilier par son ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | ID du bien immobilier |
No output schema declared.
No examples provided.
get_market_predictions ~83
Previsions de prix a 90 jours par quartier (regression lineaire)
| Name | Type | Req | Description |
|---|---|---|---|
| months | number | – | Periode d'analyse en mois (3-36, defaut: 12) |
| quartier | string | – | Quartier specifique (optionnel, tous si omis) |
| status | string | – | Filtrer par type (defaut: all) |
No output schema declared.
No examples provided.
get_market_trends ~64
Obtenir les tendances du marche immobilier par quartier (variation de prix sur N mois)
| Name | Type | Req | Description |
|---|---|---|---|
| months | number | – | Periode en mois (3-36, defaut: 12) |
| status | string | – | Filtrer par type (defaut: all) |
No output schema declared.
No examples provided.
get_price_analytics ~138
Analyser les prix au m² par quartier avec tendances et distribution
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | – | Quartier ou ville specifique (optionnel) |
| page | number | – | Page (defaut: 1) |
| pageSize | number | – | Resultats par page (defaut: 20, max: 100) |
| priceMax | number | – | Prix maximum (optionnel) |
| priceMin | number | – | Prix minimum (optionnel) |
| propertyType | string | – | Type de bien (optionnel, ex: Appartement, Villa) |
| transaction | string | – | Type de transaction (defaut: Vente) |
No output schema declared.
No examples provided.
get_quartier_comparison ~80
Comparer deux quartiers cote-a-cote (prix m², nombre d'annonces, volatilite)
| Name | Type | Req | Description |
|---|---|---|---|
| q1 | string | yes | Premier quartier (ex: Agdal) |
| q2 | string | yes | Second quartier (ex: Hay Riad) |
| status | string | – | Filtrer par type (defaut: all) |
No output schema declared.
No examples provided.
get_quartier_stats ~42
Obtenir les statistiques agregees par quartier (prix m² moyen, nombre d'annonces)
| Name | Type | Req | Description |
|---|---|---|---|
| transaction | string | – | Filtrer par transaction |
No output schema declared.
No examples provided.
get_rental_yield ~46
Obtenir le rendement locatif brut par quartier (comparatif achat vs location)
| Name | Type | Req | Description |
|---|---|---|---|
| quartier | string | – | Quartier specifique (optionnel, tous si omis) |
No output schema declared.
No examples provided.
get_suspicious_listings ~160
Detecter les annonces avec des prix anormaux (IQR outliers, scores de severite)
| Name | Type | Req | Description |
|---|---|---|---|
| iqrMultiplier | number | – | Multiplicateur IQR (1.5-3.0, defaut: 2.0) |
| minDeviationPct | number | – | Deviation minimum (10-90%, defaut: 30) |
| minSample | number | – | Echantillon minimum (12-300, defaut: 20) |
| page | number | – | Page (defaut: 1) |
| pageSize | number | – | Resultats par page (defaut: 20, max: 100) |
| status | string | – | Filtrer par type (defaut: all) |
No output schema declared.
No examples provided.
list_quartiers ~20
Lister tous les quartiers disponibles avec leur ville
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_villes ~16
Lister toutes les villes disponibles
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_listings ~214
Rechercher des biens immobiliers avec filtres (transaction, location, budget, surface, pieces, type de bien, mot-cle)
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | – | Quartier ou ville (ex: Agdal, Hay Riad, Salé) |
| page | number | – | Page (defaut: 1) |
| pageSize | number | – | Resultats par page (defaut: 12, max: 60) |
| priceMax | number | – | Prix maximum en MAD |
| priceMin | number | – | Prix minimum en MAD |
| propertyType | string | – | Type de bien |
| q | string | – | Mot-cle dans le titre ou la description |
| roomsMax | number | – | Nombre maximum de pieces |
| roomsMin | number | – | Nombre minimum de pieces |
| sort | string | – | Tri |
| surfaceMax | number | – | Surface maximum en m² |
| surfaceMin | number | – | Surface minimum en m² |
| transaction | string | – | Type de transaction |
No output schema declared.
No examples provided.
How do I install the Real Estate Capitale MCP server?
Real Estate Capitale MCP is a hosted endpoint at https://realestatecapitale.ma/mcp, 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 · realestatecapitale.ma
claude mcp add --transport http allamiwayl-27-rabatrealestate-mcp 'https://realestatecapitale.ma/mcp'
What is the Real Estate Capitale MCP server?
Real Estate Capitale MCP is listed in the public MCP registry as io.github.allamiwayl-27/rabatrealestate-mcp. Real estate MCP server for Morocco, search, valuation, market analysis, 17 tools. This page covers its hosted endpoint (https://realestatecapitale.ma/mcp).
Is the Real Estate Capitale MCP server safe to use?
Real Estate Capitale 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 Real Estate Capitale MCP server expose?
Real Estate Capitale MCP exposes 17 tools: search_listings, get_listing, estimate_property, get_market_trends, get_quartier_stats, and 12 more. Their descriptions and schemas cost roughly 1,409 tokens of context every time the server is loaded.
Does the Real Estate Capitale MCP server require authentication?
Its publisher declares no required credentials for Real Estate Capitale 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 Real Estate Capitale MCP server still maintained?
Real Estate Capitale MCP is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.