Servidor MCP de Property leads & county data

• Nombre en el registroio.gisdb/gisdbverificado en el registro MCP

El nombre en el registro está bajo gisdb.io. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-29
• Herramientas15
• El servidor se llamagisdb
• Versión del servidor0.4.1
• Versión del protocolo2025-06-18

El 2026-10-29 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 420 ms.

• Sus herramientas hacen todos los casos de uso comprobados: find parcels by address, parcel ID, or owner name; build property lead lists from county records.
• Comprobado 6 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 6 hasta ahora
• Qué puede hacer un agente con él2 de 2 casos de uso
• Respondiómidiendo6 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta421 ms
• Espacio en el contexto del agente≈ 5737 tokenslas definiciones de todas sus herramientas (15), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100
• Resultados tipados12 de 15 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Todas las herramientas pasan las seis comprobaciones.

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• gisdb_search_catalog

  Find county records packages and directory listings. Check each package's availability, price, source coverage and limits before buying. A county listing does not confirm lead, assessment or CAD coverage.

• gisdb_get_metadata

  Read a county records package's verified details, source coverage, missing facts and limits. Returns unavailable when no verified package exists. CAD compatibility and the current tax year are not assumed.

• gisdb_search_records

  Search recorded county property facts or repeated owner-name groups. Use property_records for address, parcel or owner-name searches, or owner_portfolios for unfiltered groups. Property records allow 1–250 rows and offsets through…

• gisdb_guide_search

  Find available property records, owner-name groups, lead packages or county downloads. Ask one next_question at a time. Accept unknown or skipped answers and resend previous answers and skipped IDs. Returns source coverage, previews and…

• gisdb_start_search

  Save this GISDB search to the connected account. Reuse the same idempotency_key if the result is uncertain. Does not buy, subscribe or send anything.

• gisdb_continue_search

  Continue this saved search with its latest revision and all previous answers and skips. Review any changed source or offer. Reuse a retry key only with identical arguments.

• gisdb_get_search

  Reopen this account's saved search and recheck its sources and offers. Keep the user's preferences and ask them to confirm any changed source or offer.

• gisdb_save_search

  Name and save this account's search. Saving does not buy a subscription or start updates. Use the current revision and a stable retry key.

• gisdb_list_saved_searches

  List this connected GISDB account's saved searches, with their workflow IDs and revisions. Reopen a search to check its source before calling it current.

• gisdb_create_checkout

  Create a secure payment link for the selected reviewed records, lead or subscription offer. First show its price, coverage, update frequency, renewal and cancellation terms and get the user's purchase request. Card details stay on the…

• gisdb_get_order

  Check the same account's order after checkout or an uncertain result. Verifies payment, subscription, access and delivery separately. Use only its returned order_id. A payment link or confirmed payment does not prove files were delivered.

• gisdb_open_billing_portal

  Open secure billing for this account's order or subscription when the user asks. Payment details stay on the hosted page. Read the order after returning to confirm any change; opening the page alone confirms nothing.

• gisdb_cancel_subscription

  Cancel the selected subscription's renewal at the end of its paid period, only when the user asks. Returns confirmed renewal and access status. Pausing updates does not cancel renewal.

• gisdb_get_lead_updates

  Read this account's saved-search updates, delivery revision, source dates, check times and available downloads. Only a successful source check can establish no new records. Failed checks keep the last successful result. Subscription and…

• gisdb_set_lead_updates

  Pause or resume updates for this saved search when the user asks. Read updates first, then use its delivery revision and a stable retry key. Pausing does not cancel renewal. Resuming requires verified paid access and source checks and…