Servidor MCP de Spidra

• Endereçohttps://mcp.spidra.io/mcpfora do registro oficial: respondeu quando perguntado

Nenhuma entrada do registro oficial de MCP nomeia este servidor. Ele respondeu em spidra.io quando o Atlas perguntou no endereço onde servidores costumam ficar, então é do próprio fornecedor. Clientes e catálogos que listam servidores a partir do registro não o mostram.

• Estadorespondeverificado em 2026-10-27
• Ferramentas28
• O servidor se chamaspidra-mcp
• Versão do servidor0.7.0
• Versão do protocolo2025-06-18

Em 2026-10-27 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 430 ms.

• As ferramentas fazem todos os casos de uso verificados: extract structured fields from web pages using a JSON schema; scrape Google Maps listings into a table of leads; convert PDFs and slides into markdown.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCP76 de 100responde 100 · faz o trabalho 100 · definições 98 · contexto 60 · conexão 100 · reduzida pelos sinais de alerta abaixo
• O que um agente consegue fazer com ele3 de 3 casos de uso
• Respondeuem 100% dos dias7 de 7 verificações diárias
• Mediana da primeira resposta629 ms
• Espaço no contexto do agente≈ 13.056 tokensas definições de todas as ferramentas (28), que o agente carrega a cada turno
• Definições das ferramentasA · 98 de 100
• Resultados tipados0 de 28 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 3 de 28

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• spidra_search

  Search the web and get back ranked results: titles, links and descriptions, as a search engine shows them. Waits and returns the results, usually in a few seconds. **Use it when** you don't know the URL yet, want news, images or videos…

• spidra_map

  List a website's page URLs without scraping them, from its sitemaps and the links on its pages. Waits and returns the URLs, usually in a few seconds. **Use it when** you need the right pages on a site before reading them ("which page on…

• spidra_scrape

  Read one known URL and get its content as Markdown, or the data you describe as JSON. Waits and returns the result, usually in a few seconds (up to a minute for hard pages). **Use it for** one URL. Links to PDF, Word, Excel and PowerPoint…

• spidra_batch_scrape

  Read 2 to 50 known URLs, each on its own with its own result, using the same prompt or schema for all. **Use it for** anything with more than one URL: product pages, listings, articles, or just two pages to compare. **Waiting:** with…

• spidra_crawl

  Start at one URL and follow links to the kind of pages you describe, optionally extracting data from each. Returns a "jobId" straight away. **Use it when** you need many pages of one kind and don't know their URLs (every blog post, every…

• spidra_crawl_pages

  Read a crawl's pages, in order, with each page's data and links to its Markdown and HTML (the links last 1 hour). Use it for crawls of more than 100 pages, since spidra_get_job returns only the first 100, or after a cancelled crawl to get…

• spidra_crawl_report

  Explain a finished crawl: how it read the instruction, how many pages it read only to find the wanted ones (free), and every link it didn't follow, counted by reason. Pass "reason" to list the URLs for one reason, each with the page it…

• spidra_crawl_extract

  Run a new extraction over every page a finished crawl saved, without visiting the site again. Much cheaper than crawling again: only AI credits are charged. Returns a new "jobId"; check it with spidra_get_job (type "crawl"). The original…

• spidra_retry_crawl_page

  Run a crawl's extraction again on one saved page and return the new data. It doesn't visit the site, and the page's stored data is replaced. Use it when one or two pages came back empty or wrong. Get "pageId" from spidra_crawl_pages (each…

• spidra_parse

  Turn documents into Markdown, page by page, and into JSON with a "prompt" or "schema". PDF, Word, Excel, PowerPoint, OpenDocument, RTF, EPUB, CSV and HTML files work, and scanned pages are read with AI. **Use it for** reports, papers…

• spidra_find_templates

  Find ready-made templates: jobs that turn a few inputs into a table of results, such as Google Maps leads with emails, Amazon keyword rank, LinkedIn or Indeed jobs, YouTube transcripts, Zillow homes or Google Flights prices. Free. **Use…

• spidra_get_template

  Get what a template needs and what it returns: its inputs (send them by "key" to spidra_run_template; "required" ones must be set, others have defaults), its columns, and its limits in plain words. Free.

• spidra_run_template

  Run a template and get its rows. Most runs finish in this call (it waits up to about 45 seconds). A longer one returns a "runId"; check it with spidra_get_job (type "template_run") every 10 to 15 seconds until "status" isn't "running"…

• spidra_list_presets

  List the user's saved presets, newest first: saved template runs (a template and its inputs) and saved tool requests. Pass "presetId" to get one in full. Run one with spidra_run_preset.

• spidra_save_preset

  Save a job so it can run again with one call, or change a saved one. - A template preset: "kind": "template", the template's "template" slug and its "inputs". - A tool preset: "kind": "tool", the "tool" (scrape, batch, crawl, map, search…

• spidra_run_preset

  Run a saved preset. "overrides" changes template inputs, or request fields of a tool preset, for this run only. A template preset returns its template run (check a running one with spidra_get_job, type "template_run"). A tool preset…

• spidra_delete_preset

  Delete a saved preset. Runs already made from it stay in the history. A monitor that watches it starts failing until its sources are changed. Confirm with the user before deleting.

• spidra_create_monitor

  Watch a template, a preset or a list of pages on a schedule and get an alert when something changes: new or removed items, changed fields (like a price), or page text changes. - The first check runs straight away and records the starting…

• spidra_list_monitors

  List the user's monitors with their schedule, last check and next check. Pass "monitorId" to get one in full. What changed is in spidra_monitor_changes.

• spidra_update_monitor

  Change a monitor, or pause and resume it. Send only what changes; the fields are the same as spidra_create_monitor. "status": "paused" stops checks and keeps the history; "active" starts them again. Changing "sources" restarts the…

• spidra_delete_monitor

  Delete a monitor and its check history. To stop checks but keep the history, pause it with spidra_update_monitor instead. Confirm with the user before deleting.

• spidra_check_monitor

  Run a monitor's check now, outside its schedule. It runs in the background, costs what a scheduled check costs, and alerts like one. Once a minute at most per monitor. Read the result with spidra_monitor_changes after a little while.

• spidra_monitor_changes

  A monitor's checks, newest first, with a one-line summary of each. Pass "checkId" for everything one check found, per source: new, changed and removed items (with old and new values), and page text changes. A source's first check has…

• spidra_get_job

  Get any job's status, and its result once finished. Use it for the ids other tools return when they don't wait to the end. - "scrape", "search": a jobId. Readable for about an hour after it finishes (failed ones 24 hours); after that, use…

• spidra_cancel_job

  Cancel a running batch, crawl or search. - "batch": URLs not yet started are stopped and their held credits returned; finished ones keep their results. A cancelled batch can't be retried. - "crawl": stops at its next check. If it had…

• spidra_retry_batch

  Run a batch's failed URLs again with the batch's original options; the rest are left alone. Use it after spidra_get_job shows "failedCount" above 0. Cookies are never stored, so pass "cookies" again if the batch used them. Then check the…

• spidra_account

  The user's plan, credits left this billing period, Stealth Mode bandwidth, and how many monitors the plan allows. Use it before a large batch, crawl or template run to check there's enough, or to answer "how many credits do I have"…

• spidra_logs

  Find past runs, newest first, or open one by its id. Every run is logged, including ones made in the dashboard, and logs last after the job itself can no longer be read with spidra_get_job. - "tool": scrape, search, map, parse, crawl…