ae.projectory/mcp

Est-ce que ae.projectory/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « ae.projectory/mcp » est classé « Vérifié ». Aucun comportement malveillant détecté au test comportemental. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 5 outils

• fetch≈ 1554 tokens

  Fetch one development's detail using a known ID, slug or Projectory URL; no prior search or facet lookup is needed. Returns development-wide pricing, location, availability, enquiry action, payment plan, grouped unit types, evidence, media and a plain-text description marked as untrusted source material. Individual unit rows and raw HTML are omitted. Accepted forms: `project:jacob-co-beachfront-living`, `jacob-co-beachfront-living`, or `https://projectory.ae/projects/jacob-co-beachfront-living/`. Use `search` if only the project name is known.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Project ID from search, plain slug, or public Projectory project URL.

  Exemple d'appel

  {"name": "fetch", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "slug": "texte", "areas": [], "flags": {}, "title": "texte", "emirate": "texte", "pricing": {}, "bedrooms": {}, "evidence": [], "developer": "texte", "coordinates": {}}}

• list_project_facets≈ 504 tokens

  Explore all exact values for `emirate`, `area`, `developer`, `propertyType`, `availability` and `sort`, plus boolean flags `newLaunch` and `comingSoon`. Skip this call when the needed slugs are known. Use `suggest_project_terms` for a single partial facet name instead of downloading all choices.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_project_facets", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"sort": [], "emirates": [], "developers": [], "availability": [], "booleanFlags": [], "propertyTypes": [], "areasByEmirate": {}}}

• search≈ 1612 tokens

  Find published off-plan UAE developments by project name or slug text, combined with exact structured filters. Returns shortlist facts and a pagination cursor. Follow more pages only when the user's task needs them; a page's result count is not a total. Use `suggest_project_terms` for a partial facet name, `list_project_facets` to explore all filter choices, and `fetch` for selected project detail. A known project URL or slug can go straight to `fetch`. Prices and price filters apply to the whole development. They do not establish that a particular bedroom count, property type, or unit is available at that price.

  Paramètres, retour & exemple (15)

  Paramètres

  • area · string · optionnel
    Exact public API area slug from list_project_facets, for example dubai-marina.
  • sort · string · optionnel · recommended | price-asc | price-desc | handover-asc | handover-desc
    Sort value from list_project_facets.
  • limit · integer · optionnel
    Maximum results to return. Defaults to 10.
  • query · string · optionnel
    Literal text within a project name or slug; ASCII letter case is ignored. Use structured filters for location, budget and other criteria; this does not interpret natural-language requests.
  • cursor · string · optionnel
    Pagination cursor returned by a previous search call.
  • emirate · string · optionnel
    Exact public API emirate slug from list_project_facets, for example dubai.
  • developer · string · optionnel
    Exact public API developer slug from list_project_facets, for example sobha-realty.
  • newLaunch · boolean · optionnel
    Filter for projects marked as new launches.
  • comingSoon · boolean · optionnel
    Filter for projects marked as coming soon.
  • bedroomsMin · integer · optionnel
    Return developments advertising a bedroom count at or above this value. Zero leaves the filter unset; it does not select studios or identify a unit at a particular price.
  • priceMaxAed · integer · optionnel
    Upper bound of the desired development-wide price interval. A development matches when its known range starts at or below this amount; unknown pricing is excluded.
  • priceMinAed · integer · optionnel
    Lower bound of the desired development-wide price interval. A development matches when its known range reaches this amount or above; unknown pricing is excluded.
  • availability · string · optionnel · available | limited | sold-out
    Availability filter from list_project_facets.
  • handoverYear · integer · optionnel
    Expected handover year.
  • propertyType · string · optionnel
    Exact public API property type slug from list_project_facets, for example apartment.

  Exemple d'appel

  {"name": "search", "arguments": {"area": "texte", "sort": "recommended", "limit": 1, "query": "texte", "cursor": "texte", "emirate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"limit": 1, "projects": [], "nextCursor": "texte", "pricingNote": "texte"}}

• search_transactions≈ 1266 tokens

  Search canonical residential sale registrations in one required market: Dubai or Abu Dhabi. Whole area, project and building names ignore ASCII letter case; provider IDs match exactly. Filters combine with AND; date bounds are inclusive. Returns newest-first pages of 25 rows by default, at most 100. Follow `nextCursor` with the same filters only when more rows are needed for the user's task. A page's row count is not the total number of matching sales. A bedroom count matches the canonical range; 0 means studio. `sourceProjectId` is a provider identifier, not a Projectory development ID. Partial-name discovery, totals and statistics are not provided. Results do not guarantee real-time freshness.

  Paramètres, retour & exemple (10)

  Paramètres

  • to · string · optionnel
    Inclusive sale-registration date upper bound in YYYY-MM-DD format; year 1900 to 2200.
  • from · string · optionnel
    Inclusive sale-registration date lower bound in YYYY-MM-DD format; year 1900 to 2200.
  • limit · integer · optionnel
    Maximum rows to return. Defaults to 25.
  • cursor · string · optionnel
    Opaque pagination cursor returned by the previous transaction search page. Reuse the same filters when continuing.
  • market · string · requis · dubai | abu-dhabi
    Required transaction market.
  • areaName · string · optionnel
    Whole canonical area name; ASCII letter case is ignored.
  • bedrooms · integer · optionnel
    Bedroom count to match against each transaction's canonical bedroom range. Use 0 for a studio.
  • projectName · string · optionnel
    Whole canonical project name; ASCII letter case is ignored.
  • buildingName · string · optionnel
    Whole canonical building name; ASCII letter case is ignored.
  • sourceProjectId · string · optionnel
    Exact provider project identifier. This is not a Projectory development ID.

  Exemple d'appel

  {"name": "search_transactions", "arguments": {"market": "dubai"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"nextCursor": "texte", "transactions": []}}

• suggest_project_terms≈ 381 tokens

  Resolve partial emirate, area, developer or property-type text, such as "marina" or "sobha", into exact filter slugs for `search`. Does not search project names. Skip when the exact slug is known; use `list_project_facets` to enumerate all values.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Maximum suggestions. Defaults to 5.
  • query · string · requis
    Partial developer, area, emirate, or property-type text.

  Exemple d'appel

  {"name": "suggest_project_terms", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": "texte", "suggestions": []}}

Badge pour votre README

Ce serveur a passé le pentest comportemental. Le badge porte son nom et renvoie à cette fiche — la preuve, c'est la fiche (verdict live qu'on contrôle), pas l'image.

[![Vérifié par MCP Hub](https://dokore.fr/badge/ae.projectory--mcp.svg)](https://dokore.fr/serveur/ae.projectory--mcp)

<a href="https://dokore.fr/serveur/ae.projectory--mcp"><img src="https://dokore.fr/badge/ae.projectory--mcp.svg" alt="Vérifié par MCP Hub" height="20"></a>

Réévalué en continu : si le comportement change, le verdict tombe et le badge disparaît. Un badge qui ne pointe pas vers une fiche dokore.fr ne prouve rien. Comment ça marche

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.projectory.ae/mcp