Data Collection

muscat.properties

Provides tools to search and retrieve real estate project, area, and developer information from an Omani property catalogue.

1 endpoint4 known toolsFirst detected October 22, 2026Last detected October 22, 2026

ENDPOINT 1

https://muscat.properties/mcp

No auth detected

MCP server metadata

Name: muscat-properties
Version: 1.0.0

Capabilities

tools

Server instructions

Muscat Properties lists new-build and off-plan real estate in Oman: projects in Muscat (Al Mouj, Muscat Bay, Yiti, AIDA, Shatti Al Qurum), Jebel Sifah, Hawana Salalah, Sultan Haitham City and the other areas, with developer, starting price in Omani rial (OMR), status, handover, bedrooms and whether a purchase can lead to Oman residency. Use search_projects to find projects by area, developer, bedrooms, budget in OMR or status; get_project for one project in full; list_areas and list_developers for the directories. Prices are developer starting prices as listed on the project page and change over time: cite the project page (its url) with any figure. Pass lang (en, ar or ru) for names and text in that language. Every page also has a Markdown version: add index.md to its URL or send Accept: text/markdown.

Known tools 4

search_projects

Projects in the catalogue, filtered by area, developer, bedrooms, maximum starting price in OMR, status or free text.

Inferred read-only

get_project

Every published fact of one project: developer, area, status, handover, starting price and price per square metre in OMR, sizes, bedrooms, units, ownership, residency, payment plans, amenities, key distances, the opening answer and the FAQ.

Potential side effects

list_areas

The areas with a page on the site, with how many catalogue projects each has and whether foreigners may own there.

Inferred read-only

list_developers

The developers with a page on the site, with how many catalogue projects each has.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.muscat-properties]
url = "https://muscat.properties/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "muscat-properties": {
      "type": "http",
      "url": "https://muscat.properties/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: muscat-properties
Remote MCP URL: https://muscat.properties/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "muscat-properties": {
      "url": "https://muscat.properties/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "muscat-properties": {
      "type": "http",
      "url": "https://muscat.properties/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "muscat-properties",
  "transport": "streamable-http",
  "url": "https://muscat.properties/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.