SpotMe
REMOTE · SERVER.SPOTME.MX
Rent storage and parking in Mexico — mini-bodegas, estacionamiento, bodegas. Live prices + links.
Available components
Last scanned (4 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 11 Nov 2026.
Category E-commerce
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 Security100
- 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, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1088 tokens (~120/item across 9 items; 4 tools + 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.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 supported MCP spec version (2025-11-25); the latest is 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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 14 Oct 26 +1
- Stability: 0.97 → pass security
- 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
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 11 Nov 2026 · Probed https://server.spotme.mx/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=server.spotme.mx | CN=YR2,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | RSA 2048 | SHA256-RSA | 54873bbc8518970ba02cf1e5aea93989251 |
| SANs: server.spotme.mx | ||||||
| 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 secure
Validation of server.spotme.mx. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| mx. | DS published | 43850 | 8 | Verified |
| spotme.mx. | DS published | 56875 | 8 | Verified |
| server.spotme.mx. | Verified address RRset verified with the apex keys |
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=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://server.spotme.mx/mcp | Verified | 200 | |
| http (plaintext) | http://server.spotme.mx/mcp | HTTPS enforced | 301 | https://server.spotme.mx/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_city_overview City inventory overview ~85
Summary of SpotMe inventory in a Mexican city: counts by space type, top neighborhoods, and price ranges. Falls back to benchmark ranges for cities where SpotMe is still expanding. Use this when the user wants a market overview.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug or name in Mexico — e.g. "ciudad-de-mexico", "monterrey". |
No output schema declared.
No examples provided.
get_listing_summary Look up a listing ~93
Look up a single SpotMe listing by its short ID (the part after `spotme.mx/c/` in the URL). Returns size, price, neighborhood, and a link back to spotme.mx. Use when the user provides a specific SpotMe link or short ID.
| Name | Type | Req | Description |
|---|---|---|---|
| nanoId | string | yes | The short ID of the listing — the segment after `spotme.mx/c/` in the URL. |
No output schema declared.
No examples provided.
get_pricing_guide Price guide ~156
Estimated monthly price range (MXN) for a given space type (self-storage, parking, warehouse, industrial-warehouse) in a Mexican city, optionally narrowed by target size in m². Pure benchmark/reference — does not return individual listings. Use this for "how much does X cost in Y?" questions.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug or name in Mexico. |
| sizeM2 | number | – | Optional. Approximate target size in square meters — narrows the price estimate. |
| spaceType | string | yes | Space type. self-storage = mini bodegas (B2C personal storage), parking = estacionamiento, warehouse = bodega comercial (B2B), industrial-warehouse = nave industrial. |
No output schema declared.
No examples provided.
search_listings Search listings ~399
Find rentable spaces in a Mexican city by space type. Space types: self-storage (mini bodegas, B2C personal storage), parking (estacionamiento), warehouse (bodega comercial, B2B), industrial-warehouse (nave industrial). Returns up to 5 listings with short URLs to spotme.mx; if none match, returns benchmark price ranges for that city. Use this when the user wants concrete options to rent.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug (kebab-case) or name in Mexico — e.g. "ciudad-de-mexico", "monterrey", "guadalajara". Required. |
| maxPriceMxn | integer | – | Optional. Maximum monthly price in Mexican Pesos (MXN). |
| minSizeM2 | number | – | Optional. Minimum size in square meters. |
| offset | integer | – | Optional. Skip this many matches before returning results — use it to show the NEXT few options for the same query (e.g. offset=5 after a first call returned 5). Max 20; beyond that, send the user to… |
| sortBy | string | – | Optional. Result ordering. Use "price_low_to_high" to surface the CHEAPEST listings first — the right way to find a city's price floor (e.g. "cheapest parking in Monterrey"). "price_high_to_low" = mo… |
| spaceType | string | – | Optional. self-storage = mini bodegas (B2C personal storage), parking = estacionamiento, warehouse = bodega comercial (B2B), industrial-warehouse = nave industrial (large industrial space). Omit to s… |
No output schema declared.
No examples provided.
How do I install the SpotMe MCP server?
SpotMe is a hosted endpoint at https://server.spotme.mx/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 · server.spotme.mx
claude mcp add --transport http mx-spotme-mcp 'https://server.spotme.mx/mcp'
What is the SpotMe MCP server?
SpotMe is an MCP server listed in the public MCP registry as mx.spotme/mcp. Rent storage and parking in Mexico, mini-bodegas, estacionamiento, bodegas. Live prices + links. This page covers its hosted endpoint (https://server.spotme.mx/mcp).
Is the SpotMe MCP server safe to use?
SpotMe scores 97 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 SpotMe MCP server expose?
SpotMe exposes 4 tools: search_listings, get_city_overview, get_pricing_guide, get_listing_summary. Their descriptions and schemas cost roughly 733 tokens of context every time the server is loaded.
Does the SpotMe MCP server require authentication?
No. We connected to SpotMe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SpotMe MCP server still maintained?
SpotMe is still listed as active in the MCP registry. We last reached this channel on 11 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 SpotMe MCP server?
VerifyMCP ran 13 checks on SpotMe, 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.