Servidor MCP de LeadMarina

Qué servidores del registro oficial de MCP son de LeadMarina, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-19

← Volver a LeadMarina

De quién es el servidor

Nombre en el registrocom.leadmarina/leadmarinaverificado en el registro MCP

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

Cuando le preguntamoscomprobado el 2026-10-19

Estadorespondecomprobado el 2026-10-19
Herramientas13
El servidor se llamaleadmarina
Versión del servidor1.3.0
Versión del protocolo2025-06-18

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

Medido cada díacomprobaciones diarias: 1, la primera el 2026-10-19

Respondiómidiendo1 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
Mediana de la primera respuesta223 ms
Espacio en el contexto del agente≈ 3,696 tokenslas definiciones de todas sus herramientas (13), que el agente lleva en cada turno
Definiciones de herramientasA · 100 de 100

Todas las herramientas pasan las seis comprobaciones.

Conviene revisar

Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: create_automation, update_automation, delete_automation

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.

Herramientas que ofrece13 herramientas · leído el 2026-10-19

search_leads
Run a live search for local businesses by niche + city (e.g. query 'electrician', location 'Austin, TX'). Returns a search_id and, usually, the first batch immediately (its listings are in `results`; their emails and phones are not…
get_search_results
Fetch a search's leads with verification filled in as enrichment progresses. Poll until enrichment is 'complete'. Each lead includes verified emails (SMTP status), verified phones (line type + carrier), owner name where identified…
enrich_domains
Already have businesses? Pass up to 10 website domains to run the full enrichment + verification pipeline on them (verified emails + phones, owner name, socials). Costs 1 lead per distinct domain — spellings of the same site (acme.com…
query_leads
Search ALL leads the account has ever collected (across every search) with filters and sorting — no new search is run and no leads are spent. A Google listing found more than once appears once, with its most recent data. Up to 1,000 leads…
export_leads
Push leads into a connected destination: 'close' (CRM — uses the account's saved field mapping), 'ghl' (GoHighLevel sub-account), 'google_sheets' (new spreadsheet, or pass spreadsheet_id for one LeadMarina created before), or a file…
list_searches
The account's recent searches (id, niche, location, result count, when) — use a search_id with get_search_results or export_leads.
get_balance
What the account has left, and when it resets. On a plan with a rate limit (no monthly quota) this is the leads left in the current 7-day period; on a metered plan it is the monthly allotment remaining.
list_views
The account's saved views from the leads table — each a named set of filters the user already built (e.g. 'Roofers with a mobile number'). Returns each view's filter conditions in the exact shape query_leads and export_leads accept, so…
list_integrations
Which export destinations this account has connected (Close, GoHighLevel, Google Sheets) and whether each is ready to receive leads. Check this BEFORE export_leads or create_automation with a CRM destination — those fail if the…
list_automations
The account's automations — saved searches that re-run on a schedule and export themselves. Shows each one's niche, cities, cadence, destination, whether it's active, when it next runs, and how the last run went.
create_automation
Create an automation: re-run a search on a schedule and send the results somewhere automatically. Pass cities as plain strings (e.g. ['Austin, TX', 'Dallas, TX']) — they're resolved for you. IT SPENDS LEADS ON EVERY RUN, one per result…
update_automation
Pause an automation (active=false) so it stops running and stops spending leads, or resume it (active=true). Pausing is the safe way to stop an automation you might want back — use delete_automation only when the user wants it gone for…
delete_automation
Permanently delete an automation. This cannot be undone — confirm with the user first, and prefer update_automation with active=false if they only want it to stop for now. Leads already collected by past runs are kept; only the schedule…

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

{
  "mcpServers": {
    "leadmarina": {
      "type": "http",
      "url": "https://leadmarina.com/api/mcp"
    }
  }
}

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.