MCP servers observed by Lowdown
online.webarm24/webarm24 MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 93 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-17 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:online.webarm24/webarm24
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:online.webarm24/webarm24?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-17: input or output schemas changed, descriptions changed, tool names changed; tool count 91 → 93
- 2026-11-14: input or output schemas changed, descriptions changed, tool names changed; tool count 89 → 91
What tools does it list?
93 tools on 2026-11-17:
account_meagent_job_getagent_job_listagent_job_submitai_models_listanalyze_jsonbrowser_clickbrowser_click_atbrowser_close_sessionbrowser_extract_textbrowser_fillbrowser_get_htmlbrowser_navigatebrowser_paste_htmlbrowser_press_keybrowser_screenshotbrowser_scrollbrowser_session_deletebrowser_session_getbrowser_session_listbrowser_session_putcredit_packscredits_checkout_urlcredits_historylicense_statuspipeline_builder_chatpipeline_createpipeline_debug_chatpipeline_deletepipeline_deleted_listpipeline_deleted_restorepipeline_getpipeline_group_assignpipeline_group_createpipeline_group_deletepipeline_group_listpipeline_group_updatepipeline_history_getpipeline_history_listpipeline_history_restorepipeline_listpipeline_runpipeline_run_cancelpipeline_run_getpipeline_run_waitpipeline_runs_listpipeline_test_steppipeline_updatepython_packages_listschedule_createschedule_deleteschedule_exportschedule_getschedule_importschedule_listschedule_runschedule_updatesend_emailskill_createskill_deleteskill_getskill_importskill_listskill_updatestorage_deletestorage_file_deletestorage_file_getstorage_file_putstorage_files_liststorage_liststorage_readstorage_writeworkflow_approveworkflow_builder_chatworkflow_builder_create_pipelineworkflow_createworkflow_deleteworkflow_deleted_listworkflow_deleted_restoreworkflow_exportworkflow_getworkflow_history_getworkflow_history_listworkflow_history_restoreworkflow_importworkflow_listworkflow_runworkflow_run_cancelworkflow_run_getworkflow_run_waitworkflow_runs_listworkflow_updateworkflow_validate
MCP Registry declaration
- Registry name:
online.webarm24/webarm24 - Declared version: 1.0.0
- Status: active
- Declared hosts:
webarm24.online
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:online.webarm24/webarm24", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:online.webarm24/webarm24?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).