Koskamo

Rate-My-Agent MCP

This MCP server provides AI assistants with access to verified real estate agent reviews and a matching service for buyers and sellers in the US and Canada. It allows agents to retrieve city-level review statistics, access matching quiz questions, and submit match requests on behalf of users.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Rate-My-Agent MCP logo, by Rate-My-AgentVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by Rate-My-Agent
MCP endpoint (Streamable HTTP)
https://mcp.rate-my-agent.com/mcp
Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (2)

Can change data (1)

3 of 3 have a description · 3 of 3 declare behavior hints · 1 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to mcp.rate-my-agent.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve verified review statistics for a specific city
  • Access questions and options for the agent matching quiz
  • Submit a completed agent match request for a user

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: com.rate-my-agent.mcp/rate-my-agent@1.0.0Project website

Protocol and capabilities

Server
rate-my-agent 1.2.0
MCP protocol negotiated in check
2025-06-18
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Rate-My-Agent.com publishes verified client reviews of real estate agents and runs a free agent-matching service for buyers and sellers across the United States and Canada. This connector can do three things: report verified-review statistics for a city (get_local_agent_review_data), return the matching questionnaire (get_matching_questions), and submit a completed request so the service can match the user with an agent (submit_match_request). A typical flow: share the review statistics for the user's city if useful, ask the questionnaire questions, echo the answers and contact details back for confirmation, then submit. Matching is available in every US and Canadian city, including those with few local reviews. Questionnaire style: ask ONE question at a time. Present its answer options as a NUMBERED list (1, 2, 3, …) and end with "Reply with the number or the answer." Renumber from 1 for every question, and accept either the number or the text — "2" and "Condo" mean the same thing. The location question depends on buying versus selling: for a SELLER, ask for the property's full street address, because the match is made on the actual property being sold. For a BUYER, ask which city or neighbourhood they are targeting — a street address is not needed. Before calling submit_match_request, show the user their answers and contact details and get an explicit confirmation, so it is unmistakable that submitting sends their information to the matching service.

Tools

3 advertised

get_local_agent_review_data — Verified-review statistics for a city
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Returns Rate-My-Agent.com's verified-review statistics for one city: how many reviewed agents and verified reviews exist there and site-wide, the average rating, the most-reviewed neighbourhoods, and whether the free matching service covers that city (it covers every US and Canadian city). Call it when the user asks about real estate agents in a specific place, or before running the matching questionnaire, to show what the ratings are based on. It returns aggregate statistics only — it does not return, rank or recommend individual agents. To collect the user's requirements, call get_matching_questions next.

get_local_agent_review_data input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "city",
    "prov_state"
  ],
  "properties": {
    "city": {
      "type": "string",
      "description": "City name, e.g. \"Austin\" or \"Vancouver\"."
    },
    "prov_state": {
      "type": "string",
      "description": "2-letter province/state code, e.g. \"BC\", \"TX\"."
    }
  },
  "additionalProperties": false
}
get_local_agent_review_data output schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "city": {
      "type": "string"
    },
    "coverage": {},
    "city_proof": {},
    "prov_state": {
      "type": "string"
    },
    "network_proof": {},
    "adapter_version": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
get_local_agent_review_data annotations
{
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}
get_matching_questions — Agent-matching questionnaire
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Returns the questions the matching service asks, each with its exact answer options and the values submit_match_request expects, plus the questionnaire version. Call it when the user wants to be matched with an agent, so the questions and accepted values always come from the service itself rather than from memory. Ask only the questions the conversation has not already answered, one at a time, presenting options as a numbered list. Financing applies to buyers and property condition to sellers. Once every required question is answered and you have the user's name, email and phone, confirm the details with them and call submit_match_request.

get_matching_questions input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
get_matching_questions output schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "then": {
      "type": "string"
    },
    "principle": {
      "type": "string"
    },
    "questions": {},
    "quiz_version": {
      "type": "string"
    },
    "adapter_version": {
      "type": "string"
    },
    "assistant_instructions": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
get_matching_questions annotations
{
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}
submit_match_request — Submit a request to be matched with an agent
Advertised by the server during the last successful anonymous check.
Open-world

Submits the user's completed questionnaire and contact details to Rate-My-Agent.com's free agent-matching service. Call it only after showing the user their answers and contact details and receiving an explicit confirmation; set consent to true to record that confirmation. Use each option's exact value from get_matching_questions. Handling the result: report success only on "ok":true, and relay the returned message verbatim. On "ok":false with code "no_response" the service did not answer in time — call it once more. On "ok":false with a field and message (for example an invalid email), tell the user what to correct, collect the new value and submit again.

submit_match_request input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "buy_sell",
    "address",
    "full_name",
    "email",
    "phone",
    "consent"
  ],
  "properties": {
    "email": {
      "type": "string"
    },
    "notes": {
      "type": "string"
    },
    "phone": {
      "type": "string",
      "description": "North-American number; 10 digits."
    },
    "budget": {
      "type": "string",
      "description": "Use an exact option value from get_matching_questions."
    },
    "address": {
      "type": "string",
      "description": "For SELLERS: the property's full street address. For BUYERS: the city or neighbourhood they are targeting."
    },
    "consent": {
      "type": "boolean",
      "description": "Set to true ONLY after the user picks \"1. Confirm and Submit Request\". Must be true to submit."
    },
    "buy_sell": {
      "enum": [
        "buying",
        "selling"
      ],
      "type": "string"
    },
    "full_name": {
      "type": "string"
    },
    "quiz_version": {
      "type": "string",
      "default": "mcp-v1"
    },
    "property_type": {
      "enum": [
        "single_family",
        "condominium",
        "townhouse",
        "commercial",
        "vacant_lot",
        "other"
      ],
      "type": "string"
    },
    "financing_help": {
      "type": "string",
      "description": "Buyers only — exact option value."
    },
    "property_condition": {
      "type": "string",
      "description": "Sellers only — exact option value."
    },
    "also_buying_or_selling": {
      "enum": [
        "yes",
        "no",
        "maybe"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
submit_match_request output schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ok"
  ],
  "properties": {
    "ok": {
      "type": "boolean",
      "description": "true only when the lead was accepted."
    },
    "code": {
      "type": "string",
      "description": "e.g. invalid_input, invalid_email, no_response."
    },
    "field": {
      "type": "string",
      "description": "Which field to correct, when applicable."
    },
    "status": {
      "type": "string"
    },
    "message": {
      "type": "string",
      "description": "Relay verbatim on success; on error, the fix to explain."
    },
    "retryable": {
      "type": "boolean",
      "description": "true means submit once more."
    },
    "http_status": {
      "type": "number"
    }
  },
  "additionalProperties": false
}
submit_match_request annotations
{
  "readOnlyHint": false,
  "openWorldHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1118 ms
95th percentile latency
1118 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1118 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http rate-my-agent-mcp https://mcp.rate-my-agent.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add rate-my-agent-mcp --url https://mcp.rate-my-agent.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable rate-my-agent-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "rate-my-agent-mcp": {
      "url": "https://mcp.rate-my-agent.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "rate-my-agent-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.rate-my-agent.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start rate-my-agent-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "rate-my-agent-mcp": {
      "type": "http",
      "url": "https://mcp.rate-my-agent.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http rate-my-agent-mcp https://mcp.rate-my-agent.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.rate-my-agent.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "rate-my-agent-mcp": {
      "serverUrl": "https://mcp.rate-my-agent.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Rate-My-Agent MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 1,120

Do you run Rate-My-Agent MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing