{"id":"patchorbit-domscribe","name":"domscribe","af_score":60.5,"security_score":47.0,"reliability_score":30.0,"what_it_does":"Domscribe instruments supported frontend apps to map rendered DOM elements to stable source locations (AST-injected data-ds IDs and a manifest) and to enable agents to query live runtime context from the browser (props/state/DOM snapshots). It also provides a UI overlay for pointing at elements and sending UI-change annotations that agents can claim/implement via MCP.","best_when":"You’re using an AI coding agent with MCP support and want reliable mapping between what you see in the browser and where to edit in the source during active development.","avoid_when":"You need strict authenticated multi-tenant access to a remote API or you cannot run a dev server with the target page open for runtime capture.","last_evaluated":"2026-03-30T13:46:50.825906+00:00","has_mcp":true,"has_api":true,"auth_methods":["MCP stdio (local agent-side integration)","Local REST/WebSocket between browser overlay and a localhost daemon"],"has_free_tier":false,"known_gotchas":["Agents should be instructed to query runtime state explicitly (README tip: prompt agents to use domscribe before changing anything).","Runtime capture requires the dev server to be running with the target page open in the browser.","Stable ID mapping and annotation claiming/implementation are tied to the mapped source locations/line numbers; agents should follow the tool outputs to avoid stale assumptions during rapid edits/HMR."],"error_quality":0.0}