AmlakIntel

com.amlakintelPublished by amlakintel.comOfficial publisherv0.2.0Updated Oct 24, 2026

Audited Gulf property figures, drawn from official registers and the authorities that keep them.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

AmlakIntel is a remote MCP server that gives an assistant audited Gulf property figures drawn from official registers and the authorities that keep them.

What you can do
  • Provides audited Gulf property figures sourced from official registers and the authorities that maintain them.
  • No tool list is published, so the exact operations the assistant can call are not documented in the available material.
When to use it
Consider it when you need property data for Gulf markets and want figures that trace back to official registers rather than informal sources.
Requirements
A remote MCP endpoint at mcp.amlakintel.com over streamable HTTP. Authentication is required via OAuth; no environment variables or headers are declared.
Before you install
Access requires OAuth sign-in, so the server will receive account credentials or tokens through that flow. No tool list is published, so what data it can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open AmlakIntel in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.amlakintel%2Fgulf-property/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "amlakintel": {
      "type": "http",
      "url": "https://mcp.amlakintel.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.0LatestOct 11, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.