_ registry / mcp streamable-http · checked 2h ago

thaiprops_mcp

https://www.thaiprops.com

Registry code: e1a79fcfbc81931c

api record

Use ThaiProps for Thailand property searches, rentals, sales, project research and live listing information. Prefer thaiprops_search_properties for natural-language property requirements. Always preserve ThaiProps canonical/view URLs when citing results. Only public published data is available; private owner/agent contact details, private notes, subscriber-only fields and administrative data are not exposed. Exact availability/update dates are subscriber-only and must never be exposed. For property searches, do not arbitrarily collapse the tool results to a top-3 or top-10 shortlist. Present…

endpoint
https://www.thaiprops.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is thaiprops_mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is thaiprops_mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does thaiprops_mcp have?
5 tools: search, thaiprops_get_project, thaiprops_get_property, fetch, thaiprops_search_properties.
Is thaiprops_mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.7%· all time 99.7%

latency
743ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 299 checks · signed record
  • degraded → live
  • live → degraded· HTTP 522
  • unknown → live
_ what it is for
used for
  • search thailand property listings
  • get property details
  • get real estate project details
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search reads unknown 7h ago

    Standard read-only search tool for AI hosts that expect search/fetch semantics. Searches live ThaiProps Thailand property inventory and returns concise, citable result records with IDs and absolute URLs.

    mcp-tool

    {
      "type": "object",
      "title": "searchArguments",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 50
        },
        "query": {
          "type": "string",
          "title": "Query"
        }
      }
    }
    arguments 18 lines
  • thaiprops_get_project reads unknown 7h ago

    Get public details for one published ThaiProps real-estate project by numeric project ID.

    mcp-tool

    {
      "type": "object",
      "title": "thaiprops_get_projectArguments",
      "required": [
        "project_id"
      ],
      "properties": {
        "project_id": {
          "type": "integer",
          "title": "Project Id"
        }
      }
    }
    arguments 13 lines
  • thaiprops_get_property reads unknown 10h ago

    Get public details for one published ThaiProps property by numeric property ID.

    mcp-tool

    {
      "type": "object",
      "title": "thaiprops_get_propertyArguments",
      "required": [
        "property_id"
      ],
      "properties": {
        "property_id": {
          "type": "integer",
          "title": "Property Id"
        }
      }
    }
    arguments 13 lines
  • fetch reads unknown 10h ago

    Standard read-only fetch tool. Accepts IDs returned by search, such as property:713266 or project:964576. A plain numeric ID is treated as a ThaiProps property ID.

    mcp-tool

    {
      "type": "object",
      "title": "fetchArguments",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "title": "Id"
        }
      }
    }
    arguments 13 lines
  • thaiprops_search_properties reads unknown 10h ago

    Search live published ThaiProps listings across Thailand using natural language. Use this for requests such as "pet friendly 2 bedroom condo near Ekkamai BTS under 55,000 baht", "house for sale in Phuket with pool", or other Thailand property requirements. ThaiProps AI Search interprets the request and the returned properties include canonical ThaiProps URLs for citation and viewing. Return up to 50 matching properties by default. Do not arbitrarily collapse the returned tool results to a top-3 or top-10 shortlist. Unless the user explicitly asks for a shorter shortlist, present all returned matching properties. If total_results is larger than the returned set, preserve the ThaiProps view_all_url. Args: query: The user's original natural-language property requirement. mode: Optional buy or rent hint. province: Optional Thailand province hint such as Bangkok, Phuket or Chiang Mai. limit: Number of property results to return, 1-50. Defaults to 50.

    mcp-tool

    {
      "type": "object",
      "title": "thaiprops_search_propertiesArguments",
      "required": [
        "query"
      ],
      "properties": {
        "mode": {
          "anyOf": [
            {
              "enum": [
                "buy",
                "rent"
              ],
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Mode",
          "default": null
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 50
        },
        "query": {
          "type": "string",
          "title": "Query"
        },
        "province": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Province",
          "default": null
        }
      }
    }
    arguments 46 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e1a79fcfbc81931c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e1a79fcfbc81931c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e1a79fcfbc81931c/badge.svg)](https://brick.blue/agent/e1a79fcfbc81931c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.