Servidor MCP de WebArm24

• Nome no registroonline.webarm24/webarm24verificado no registro MCP

O nome no registro fica sob webarm24.online. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-11-02
• Ferramentas61
• O servidor se chamawebarm24
• Versão do protocolo2025-06-18

Em 2026-11-02 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 470 ms.

• Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
• Verificado em 2 dos 7 dias necessários para julgar a confiabilidade.

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 MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 2 até agora
• Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta517 ms
• Espaço no contexto do agente≈ 5.236 tokensas definições de todas as ferramentas (61), que o agente carrega a cada turno
• Definições das ferramentasC · 68 de 100
• Resultados tipados0 de 61 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Sem descrição que permita ao agente escolher: 4 de 61
• Parâmetros sem tipo: em 1 de 61
• Parâmetros sem descrição: em 52 de 61
• Sem dizer se só lê ou se pode destruir: 61 de 61

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 →

• browser_navigate

  Open a URL in your private server-side browser session. `browser_session_label` loads a saved login (see browser_session_put) when the session is first created. Costs 1 mcp_call.

• browser_screenshot

  Screenshot of the current page (JPEG). Costs 1 mcp_call.

• browser_click

  Click an element by visible text, label or CSS selector. Costs 1 mcp_call.

• browser_click_at

  Click at pixel coordinates of the (resized) viewport. Costs 1 mcp_call.

• browser_fill

  Type a value into an input identified by label/placeholder/selector. Costs 1 mcp_call.

• browser_extract_text

  Extract text from a described area of the page. Costs 1 mcp_call.

• browser_scroll

  Scroll 'up' or 'down'. Costs 1 mcp_call.

• browser_get_html

  Return the current page HTML. Costs 1 mcp_call.

• browser_close_session

  Close your browser session (free). Idle sessions are closed after 30 minutes.

• send_email

  Send an email through the server SMTP (subject to server allowlists/limits). Costs 1 mcp_call.

• analyze_json

  Inspect large JSON: mode summary|schema|value|preview, optional dotted path. Costs 1 mcp_call.

• pipeline_list

  List your pipelines.

• pipeline_get

  Get one pipeline incl. steps, schedule and inbound trigger URL.

• pipeline_create

  Create a pipeline. See resource webarm://docs/pipeline-steps for the step schema. `extra` may carry webhook_url, webhook_secret, webhook_structured_data_only, inbound_trigger_only.

• pipeline_update

  Patch a pipeline. `fields` may contain any of: name, enabled, cron_expr, run_at (null clears), steps, task_variables, webhook_url, webhook_secret, clear_webhook_secret, webhook_structured_data_only, inbound_trigger_only…

• pipeline_delete

  Delete a pipeline and its schedule (restorable later via pipeline_deleted_restore).

• pipeline_history_list

  Change history of a pipeline, newest first: [{id, seq, action (create|update|delete|restore), source (manual|assistant|mcp|api), source_detail, changed_fields, created_at, updated_at}]. Consecutive manual UI edits within a few minutes are…

• pipeline_history_get

  One revision: {revision, snapshot (full pipeline state after that change), diff (vs previous revision)}.

• pipeline_history_restore

  Restore a pipeline to the state of a revision (recorded as a new `restore` revision). Returns the pipeline.

• pipeline_deleted_list

  Deleted pipelines that can be restored: [{pipeline_id, name, steps_count, deleted_at, source}].

• pipeline_deleted_restore

  Re-create a deleted pipeline from its last snapshot (same id, starts disabled, new inbound trigger URL).

• pipeline_group_list

  List your sidebar pipeline groups, each with its pipeline_ids. Ungrouped pipelines are in no group.

• pipeline_group_create

  Create a sidebar group, optionally moving the given pipelines into it.

• pipeline_group_update

  Rename a group and/or set whether it is collapsed in the sidebar.

• pipeline_group_delete

  Delete a group. Its pipelines are kept, just ungrouped.

• pipeline_group_assign

  Move a pipeline into a group; omit group_id (or pass null) to remove it from its group.

• pipeline_test_step

  Run a single step in isolation. `previous_outputs[i]` feeds {{step_{i+1}_output}}.

• pipeline_run

  Start a run (async; returns run_id). Costs the usual pipeline_run credits. Follow with pipeline_run_wait or pipeline_run_get.

• pipeline_run_get

  Run status (running|cancelling|ok|error|cancelled), current_step_index, per-step results, answer_preview.

• pipeline_run_wait

  Block until the run finishes or timeout_sec (max 600) elapses; returns the latest run state (check `status` — still 'running' means timed out).

• pipeline_runs_list

  Recent runs of a pipeline (max 50).

• pipeline_run_cancel

  Request cancellation of an active run (takes effect between steps).

• pipeline_builder_chat

  Ask the built-in AI pipeline builder (costs builder_call credits). `messages`=[{role,content}], `pipeline`=current draft. Returns {text, pipeline}; the draft is NOT saved — pass it to pipeline_create/update.

• pipeline_debug_chat

  Ask the AI to analyse a finished run (costs builder_call credits).

• agent_job_submit

  Run the browsing agent on a task (async; costs agent_job credits). Jobs are in-memory (lost on restart).

• agent_job_get

  Job status/result (queued|running|completed|failed).

• agent_job_list

  Recent agent jobs.

• schedule_list

  List automations (single-task schedules).

• schedule_get

  Automation details plus recent runs.

• schedule_create

  Create an automation. `schedule` follows ScheduleCreate: mode (agent|replay), task_text, target_url, webhook_url, cron_expr, run_at, lang, output_json_schema, task_variables, ...

• schedule_update

  Patch an automation (ScheduleUpdate fields).

• schedule_delete

  Delete an automation.

• schedule_run

  Run an automation now (synchronous; costs schedule_run credits).

• schedule_export

  Export an automation as portable JSON.

• schedule_import

  Import an exported automation.

• storage_list

  List your JSON/text stores.

• storage_read

  Read a store.

• storage_write

  Write a store (mode 'auto' keeps JSON, 'text' stores a string).

• storage_delete

  Delete a store.

• storage_files_list

  List stored files.

• storage_file_put

  Upload a file (base64 content). Size caps: USER_FILES_FILE_MAX_BYTES / per-user total.

• storage_file_get

  Download a file as base64 (limited to 8 MiB of base64).

• storage_file_delete

  Delete a stored file.

• browser_session_list

  List saved logins (Playwright storageState slots).

• browser_session_get

  Get a saved storageState.

• browser_session_put

  Save a Playwright storageState (stored encrypted).

• browser_session_delete

  Delete a saved login.

• account_me

  Your account incl. credit balance.

• credits_history

  Balance and last 100 ledger entries.

• credit_packs

  Purchasable credit packs.

As primeiras 60 de 61, na ordem do servidor.