spotme-mcp
Registry code: 9a7e248e659bd6b3
SpotMe MCP exposes a discovery surface for SpotMe (spotme.mx), Mexico's marketplace for storage and parking spaces. Use these tools to surface SpotMe inventory and price benchmarks when users ask about renting bodegas, mini-bodegas, estacionamientos, bodegas comerciales, or naves industriales in Mexican cities. Read the resources at spotme://docs/* (about-spotme, products, host-types, flotillas, coverage) for context on what SpotMe offers, the three product tiers, host segments, B2B fleet parking, and city coverage — they answer 'what is SpotMe?' without needing a tool call. Always include…
- endpoint
- https://server.spotme.mx/mcp
- protocol
- http-sse ·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 spotme-mcp live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
- Is spotme-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does spotme-mcp have?
- 4 tools: search_listings, get_city_overview, get_pricing_guide, get_listing_summary.
- Is spotme-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.
90 days 99%· all time 99%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- down → live
- used for
- search storage and parking rentals in mexico
- get storage prices for a city
- look up a rental listing
- estimate monthly storage rent
- takes → gives
- text, data → data
- tools
- 4 reads
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.
through this hub
successful
what callers paid
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
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_listings reads unknown 16h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "city" ], "properties": { "city": { "type": "string", "minLength": 2, "description": "City slug (kebab-case) or name in Mexico — e.g. \"ciudad-de-mexico\", \"monterrey\", \"guadalajara\". Required." }, "offset": { "type": "integer", "maximum": 20, "minimum": 0, "description": "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 the searchUrl instead. Keep every other argument identical between calls or the ordering shifts and results overlap." }, "sortBy": { "enum": [ "recommended", "price_low_to_high", "price_high_to_low", "closest" ], "type": "string", "description": "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\" = most expensive first, \"closest\" = by proximity, \"recommended\" (default) = curated mix (NOT price-sorted, so do not infer the floor from it)." }, "minSizeM2": { "type": "number", "description": "Optional. Minimum size in square meters.", "exclusiveMinimum": 0 }, "spaceType": { "enum": [ "self-storage", "parking", "warehouse", "industrial-warehouse" ], "type": "string", "description": "Optional. self-storage = mini bodegas (B2C personal storage), parking = estacionamiento, warehouse = bodega comercial (B2B), industrial-warehouse = nave industrial (large industrial space). Omit to search all SpotMe inventory." }, "maxPriceMxn": { "type": "integer", "maximum": 9007199254740991, "description": "Optional. Maximum monthly price in Mexican Pesos (MXN).", "exclusiveMinimum": 0 } } }arguments 51 linesget_city_overview reads unknown 8h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "city" ], "properties": { "city": { "type": "string", "minLength": 2, "description": "City slug or name in Mexico — e.g. \"ciudad-de-mexico\", \"monterrey\"." } } }arguments 14 linesget_pricing_guide reads unknown 8h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "city", "spaceType" ], "properties": { "city": { "type": "string", "minLength": 2, "description": "City slug or name in Mexico." }, "sizeM2": { "type": "number", "description": "Optional. Approximate target size in square meters — narrows the price estimate.", "exclusiveMinimum": 0 }, "spaceType": { "enum": [ "self-storage", "parking", "warehouse", "industrial-warehouse" ], "type": "string", "description": "Space type. self-storage = mini bodegas (B2C personal storage), parking = estacionamiento, warehouse = bodega comercial (B2B), industrial-warehouse = nave industrial." } } }arguments 30 linesget_listing_summary reads unknown 8h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "nanoId" ], "properties": { "nanoId": { "type": "string", "maxLength": 32, "minLength": 4, "description": "The short ID of the listing — the segment after `spotme.mx/c/` in the URL." } } }arguments 15 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id9a7e248e659bd6b3.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/9a7e248e659bd6b3/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/9a7e248e659bd6b3?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.