Point at an element in your running app (browser or iOS Simulator), say what should change, and your coding agent gets it over MCP.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
get_pending_annotationsReturn every pending annotation (comment + element details + screenshot) as a markdown task list. Use this first.Return every pending annotation (comment + element details + screenshot) as a markdown task list. Use this first.
No input schema was published for this tool.
list_annotationsOne-line summary per annotation. Defaults to pending only.One-line summary per annotation. Defaults to pending only.
No input schema was published for this tool.
get_annotationFull details and screenshot for a single annotation by id or number.Full details and screenshot for a single annotation by id or number.
No input schema was published for this tool.
recheck_annotationAsk the developer's browser to find this element again, right now, and report what changed since they marked it — with a fresh crop next to the original one.Ask the developer's browser to find this element again, right now, and report what changed since they marked it — with a fresh crop next to the original one.
No input schema was published for this tool.
resolve_annotationMark an annotation done after applying the change. Always call this when you have made the change.Mark an annotation done after applying the change. Always call this when you have made the change.
No input schema was published for this tool.
reply_annotationAsk the developer a question about an annotation instead of resolving it — when the request is ambiguous, or you need a decision before you change code.Ask the developer a question about an annotation instead of resolving it — when the request is ambiguous, or you need a decision before you change code.
No input schema was published for this tool.
wait_for_annotationBlock until the developer adds a new annotation in the browser (or timeout). Useful for a live 'watch' loop: wait → apply → resolve → wait. Each new annotation is handed to exactly one waiting agent, so several agents can watch at once without doing the same note twice.Block until the developer adds a new annotation in the browser (or timeout). Useful for a live 'watch' loop: wait → apply → resolve → wait. Each new annotation is handed to exactly one waiting agent, so several agents can watch at once without doing the same note twice.
No input schema was published for this tool.
clear_annotationsDelete all annotations (pending and resolved).Delete all annotations (pending and resolved).
No input schema was published for this tool.
8 of 8 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Point at an element in your running app (browser or iOS Simulator), say what should change, and your coding agent gets it over MCP.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+43 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.