MCP servers observed by Lowdown
io.github.shipvo/shipvo MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 110 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 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:io.github.shipvo/shipvo
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.shipvo/shipvo?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: 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-16: input or output schemas changed, descriptions changed, tool names changed; tool count 105 → 110
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed; tool count 75 → 105
What tools does it list?
110 tools on 2026-11-16:
a11y_audita2ui_actionsa2ui_opena2ui_sendapp_activityapply_updateapproval_approveapprovals_listarrange_appsattach_sessionaudit_logbackbackup_phonebrowser_backbrowser_clickbrowser_close_tabbrowser_openbrowser_screenshotbrowser_scrollbrowser_snapshotbrowser_tabsbrowser_typebrowser_wait_forcancel_remindercheck_for_updateclear_scheduleclear_wakeupclose_panelscreate_appdevice_logdevice_resetdismiss_notificationend_sessionexport_phone_appsexport_testfind_appsget_clipboardget_connectivityget_network_profileget_settingsget_update_statehide_appimport_phone_appsinbox_clearinbox_readinbox_viewinbox_waitinstall_appjob_statuskill_applist_appslist_installed_appslist_reminderslist_sessionslist_store_appslist_wakeupslocknotificationsopen_appopen_control_centeropen_notificationopen_notificationsopen_recentsopen_urlowner_commandowner_describepermission_logphone_modelspin_apppress_homepublish_previewpush_notificationrecord_markerrecord_startrecord_stoprefresh_appregister_wakeuprequest_app_installrequest_secretrestartrestore_phoneresume_approom_logroom_noteroom_reportrun_app_actionschedule_appscreenscreenshotscrollsearch_phonesecret_statusset_clipboardset_connectivityset_deviceset_network_profileset_phone_timeset_reminderset_settingshareshare_targetsswitch_apptaptoggle_tiletypeuninstall_appunlockupdate_appupload_buildwait_for_event
MCP Registry declaration
- Registry name:
io.github.shipvo/shipvo - Declared version: 0.0.6
- Status: active
- Declared hosts:
sim.shipvo.dev
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:io.github.shipvo/shipvo", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.shipvo/shipvo?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.github.shipvo/shipvo -- npx -y @shipvo/mcp
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).