Home / MCP registry index / dev.busymate/busymate-devtools

Busymate DevTools

dev.busymate/busymate-devtools in the official MCP registry. Endpoint https://mcp.busymate.dev/. Source: github.com/serebano/busymate-devtools.

The registry describes it as: Capture, inspect & debug HTTPS traffic across iOS, Android, browsers & backends — 304 MCP tools.

We read its 53 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

get_product_pricing search_docs read_docs_page list_docs_sections get_setup_steps list_breakpoint_events get_device list_devices get_device_status get_device_health list_device_events list_device_audit_modes test_pac_connection list_screen_share_recordings get_screen_share_recording get_my_account get_device_egress_status get_device_egress_fail_posture get_entry_count list_wipe_jobs get_entry_counts_freshness search_entries list_entries get_entry export_har inspect_requests summarize_device_traffic list_service_groups get_service_group list_tags get_device_settings get_subscription list_invoices get_usage get_block_rules_device list_todos get_todo list_advisor_findings get_advisor_finding share_advisor_finding list_issue_reports list_workspaces get_workspace list_tabs list_snapshots download_snapshot list_push_tokens get_push_response get_stats get_status list_audit_events get_audit_event list_device_service_groups

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/dev-busymate-busymate-devtools/badge.svg)](https://lazaretto.dev/mcp-registry/dev-busymate-busymate-devtools)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.