Roome Land Surveying
REMOTE · WWW.ROOMEINC.COM
Request a land survey quote from Roome Land Surveying in Plano, Texas, and find the right survey.
Available components
Last scanned (15 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
Recent critical change
Authorization (4 Nov 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (request_quote). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 513 tokens (~85/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 0
- Tool “contact_details” rewrote its description, which is the text the model reads security
- Tool “which_survey” rewrote its description, which is the text the model reads security
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Probed https://www.roomeinc.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.roomeinc.com | CN=YR2,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | RSA 2048 | SHA256-RSA | 6f1a3d810855e1bb15707f01cff3e7694cf |
| SANs: www.roomeinc.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.roomeinc.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| roomeinc.com. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://maps.gstatic.com https://www.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https://*.googleapis.com https://*.gstatic.com https://*.google.com https://*.googleusercontent.com https://www.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://pagead2.googlesyndication.com; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://www.google.com https://maps.googleapis.com https://places.googleapis.com https://maps.gstatic.com https://www.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://pagead2.googlesyndication.com https://ad.doubleclick.net https://vercel.com; worker-src 'self' blob:; frame-src https://www.google.com https://www.googl |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.roomeinc.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.roomeinc.com/mcp | HTTPS enforced | 308 | https://www.roomeinc.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 →
contact_details Contact details and hours ~38
Roome Land Surveying's phone, office hours, office and mailing addresses, and which email to use for quotes, billing, or anything else.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services List survey services ~35
The land surveying services Roome Land Surveying offers, each with its slug for request_quote and its page on roomeinc.com.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_quote Request a survey quote ~200
Sends a land survey quote request to Roome Land Surveying, a licensed land surveying firm in Plano, Texas, with the details the person gives. Properties in Texas only. Each accepted request emails the person a link to confirm it, and nothing reaches Roome until they do.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The property's street address with the city or ZIP, for example 1234 Main St, Plano, TX 75074. |
| date | string | – | Optional: the desired completion date, YYYY-MM-DD. |
| string | yes | The person's email address. The confirmation email goes here. | |
| name | string | yes | The person's full name. |
| needs | string | yes | What the survey is for, in the person's words (up to 1000 characters). |
| phone | string | yes | The person's 10-digit US phone number. |
| service | string | – | Optional: a service slug from list_services, for example boundary-survey. |
No output schema declared.
No examples provided.
service_area Check the service area ~62
Whether Roome Land Surveying serves a Texas county or city, from the service area on roomeinc.com.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | The property's Texas city, for example Plano. |
| county | string | – | The property's Texas county, for example Collin. |
No output schema declared.
No examples provided.
what_to_expect What to expect ~77
What happens when you ask Roome Land Surveying for a survey: the quote, how long a survey usually takes, the survey day, and paying. Give a service slug to add what you receive and the steps for that survey.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | – | Optional: a service slug from list_services, for example title-survey. |
No output schema declared.
No examples provided.
which_survey Find the right survey ~101
Which of Roome Land Surveying's services fits a person's situation, best match first: the same answers as the chooser on roomeinc.com/services, with why each fits, and each service's common uses and who it's for. Use it when someone doesn't know which survey they need.
| Name | Type | Req | Description |
|---|---|---|---|
| situation | string | yes | What the person needs a survey for, in their words, for example: buying a house in Plano, or putting up a new fence. |
No output schema declared.
No examples provided.
How do I install the Roome Land Surveying MCP server?
Roome Land Surveying is a hosted endpoint at https://www.roomeinc.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 · www.roomeinc.com
claude mcp add --transport http com-roomeinc-www-quotes 'https://www.roomeinc.com/mcp'
What is the Roome Land Surveying MCP server?
Roome Land Surveying is an MCP server listed in the public MCP registry as com.roomeinc.www/quotes. Request a land survey quote from Roome Land Surveying in Plano, Texas, and find the right survey. This page covers its hosted endpoint (https://www.roomeinc.com/mcp).
Is the Roome Land Surveying MCP server safe to use?
Roome Land Surveying scores 76 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 Roome Land Surveying MCP server expose?
Roome Land Surveying exposes 6 tools: request_quote, list_services, service_area, which_survey, what_to_expect, contact_details. Their descriptions and schemas cost roughly 513 tokens of context every time the server is loaded.
Does the Roome Land Surveying MCP server require authentication?
No. We connected to Roome Land Surveying without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Roome Land Surveying MCP server still maintained?
Roome Land Surveying is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Roome Land Surveying MCP server?
VerifyMCP ran 13 checks on Roome Land Surveying, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.