Rate-My-Agent
REMOTE · MCP.RATE-MY-AGENT.COM · SCANNED SEP 28
Get matched with a top-rated, review-verified real estate agent in the US or Canada.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 911 tokens (~303/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 30 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 53% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Rate-My-Agent MCP server?
Rate-My-Agent is a hosted endpoint at https://mcp.rate-my-agent.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.rate-my-agent.com
claude mcp add --transport http com-rate-my-agent-mcp-rate-my-agent 'https://mcp.rate-my-agent.com/mcp'
{
"mcpServers": {
"com-rate-my-agent-mcp-rate-my-agent": {
"url": "https://mcp.rate-my-agent.com/mcp"
}
}
} {
"servers": {
"com-rate-my-agent-mcp-rate-my-agent": {
"type": "http",
"url": "https://mcp.rate-my-agent.com/mcp"
}
}
} [mcp_servers.com-rate-my-agent-mcp-rate-my-agent] url = "https://mcp.rate-my-agent.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-rate-my-agent-mcp-rate-my-agent": {
"type": "remote",
"url": "https://mcp.rate-my-agent.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-rate-my-agent-mcp-rate-my-agent --url 'https://mcp.rate-my-agent.com/mcp' --transport streamable-http
mcp_servers:
com-rate-my-agent-mcp-rate-my-agent:
url: "https://mcp.rate-my-agent.com/mcp" {
"McpServers": {
"com-rate-my-agent-mcp-rate-my-agent": {
"Transport": "http",
"Url": "https://mcp.rate-my-agent.com/mcp"
}
}
} assistant mcp add com-rate-my-agent-mcp-rate-my-agent -t streamable-http -u 'https://mcp.rate-my-agent.com/mcp'
{
"mcpServers": {
"com-rate-my-agent-mcp-rate-my-agent": {
"type": "http",
"url": "https://mcp.rate-my-agent.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 −9
- Stability: pass → fail ▼ security
- Tool “get_lead_quiz” was removed ▼ security
- Tool “search_agents” was removed ▼ security
- Tool “submit_lead” was removed ▼ security
- Injection markers: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 501 → 303 ▲ functional
- Server version: 1.1.1 → 1.2.0 functional
- New tool “get_local_agent_review_data” functional
- New tool “get_matching_questions” functional
- New tool “submit_match_request” functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://mcp.rate-my-agent.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rate-my-agent.com | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e2a8be2a1291d2021392796a9bc8e2e8 |
| SANs: rate-my-agent.com, mcp.rate-my-agent.com, *.mcp.rate-my-agent.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.rate-my-agent.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rate-my-agent.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.rate-my-agent.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.rate-my-agent.com/mcp | HTTPS enforced | 301 | https://mcp.rate-my-agent.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_local_agent_review_data Verified-review statistics for a city ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name, e.g. "Austin" or "Vancouver". |
| prov_state | string | yes | 2-letter province/state code, e.g. "BC", "TX". |
| Name | Type | Req | Description |
|---|---|---|---|
| adapter_version | string | – | – |
| city | string | – | – |
| city_proof | – | – | – |
| coverage | – | – | – |
| network_proof | – | – | – |
| prov_state | string | – | – |
No examples provided.
get_matching_questions Agent-matching questionnaire ~127
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| adapter_version | string | – | – |
| assistant_instructions | string | – | – |
| principle | string | – | – |
| questions | – | – | – |
| quiz_version | string | – | – |
| then | string | – | – |
No examples provided.
submit_match_request Submit a request to be matched with an agent ~317
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | For SELLERS: the property's full street address. For BUYERS: the city or neighbourhood they are targeting. |
| also_buying_or_selling | string | – | – |
| budget | string | – | Use an exact option value from get_matching_questions. |
| buy_sell | string | yes | – |
| consent | boolean | yes | Set to true ONLY after the user picks "1. Confirm and Submit Request". Must be true to submit. |
| string | yes | – | |
| financing_help | string | – | Buyers only — exact option value. |
| full_name | string | yes | – |
| notes | string | – | – |
| phone | string | yes | North-American number; 10 digits. |
| property_condition | string | – | Sellers only — exact option value. |
| property_type | string | – | – |
| quiz_version | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | e.g. invalid_input, invalid_email, no_response. |
| field | string | – | Which field to correct, when applicable. |
| http_status | number | – | – |
| message | string | – | Relay verbatim on success; on error, the fix to explain. |
| ok | boolean | yes | true only when the lead was accepted. |
| retryable | boolean | – | true means submit once more. |
| status | string | – | – |
No examples provided.
What is the Rate-My-Agent MCP server?
Rate-My-Agent is an MCP server listed in the public MCP registry as com.rate-my-agent.mcp/rate-my-agent. Get matched with a top-rated, review-verified real estate agent in the US or Canada. This page covers its hosted endpoint (https://mcp.rate-my-agent.com/mcp).
Is the Rate-My-Agent MCP server safe to use?
Rate-My-Agent scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Rate-My-Agent MCP server expose?
Rate-My-Agent exposes 3 tools: get_local_agent_review_data, get_matching_questions, submit_match_request. Their descriptions and schemas cost roughly 612 tokens of context every time the server is loaded.
Does the Rate-My-Agent MCP server require authentication?
No. We connected to Rate-My-Agent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Rate-My-Agent MCP server still maintained?
Rate-My-Agent is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.