LeashIndex Get the report

Index / devtools

io.github.cameroncooke/XcodeBuildMCP

io-github-cameroncooke-xcodebuildmcp declares 58 capabilities across 58 tools, with 1 critical issue.

95/100 exposureHigh exposure

Manifest recorded 2026-10-15 from tools/list answered by the npm package xcodebuildmcp@1.12.8 (published to npm as xcodebuildmcp, listed in the official MCP registry as io.github.cameroncooke/XcodeBuildMCP 1.12.8), run in an isolated container with no network access and no credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 58 tools

58 of 58 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

high · no-expiry · All 58 tools

58 of 58 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 58 tools

58 of 58 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 46 of 58 tools

46 tools can modify data and declare no limit.

low · uncapped-read · 12 of 58 tools

12 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
build_devicewrite assumed
cleanwrite assumed
discover_projsread inferred
get_app_bundle_idread inferred
get_device_app_pathread inferred
install_app_devicewrite assumed
launch_app_devicewrite assumed
list_devicesread inferred
list_schemesread inferred
show_build_settingsread inferred
start_device_log_capwrite assumed
stop_app_devicewrite assumed
stop_device_log_capwrite assumed
test_devicewrite assumed
doctorwrite assumed
start_sim_log_capwrite assumed
stop_sim_log_capwrite assumed
build_macoswrite assumed
build_run_macoswrite assumed
get_mac_app_pathread inferred
get_mac_bundle_idread inferred
launch_mac_appwrite assumed
stop_mac_appwrite assumed
test_macoswrite assumed
scaffold_ios_projectwrite assumed
scaffold_macos_projectwrite assumed
boot_simwrite assumed
build_run_simwrite assumed
build_simwrite assumed
describe_uiread inferred
get_sim_app_pathread inferred
install_app_simwrite assumed
launch_app_logs_simwrite assumed
launch_app_simwrite assumed
list_simsread inferred
open_simwrite assumed
screenshotwrite assumed
stop_app_simwrite assumed
test_simwrite assumed
reset_sim_locationwrite assumed
set_sim_appearancewrite inferred
set_sim_locationwrite inferred
sim_statusbarwrite inferred
swift_package_buildwrite assumed
swift_package_cleanwrite assumed
swift_package_listread inferred
swift_package_runwrite assumed
swift_package_stopwrite assumed
swift_package_testwrite assumed
buttonwrite assumed
gesturewrite assumed
key_presswrite assumed
key_sequencewrite assumed
long_presswrite assumed
swipewrite assumed
tapwrite assumed
touchwrite assumed
type_textwrite assumed
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.