MCP tools: setup checks and custom domains

Use these tools when a link opens the browser instead of the app, before you move old links over, and while you set up a custom link domain.

On this page 3

Checks

Tool	What it does	Key needed
`check_app_links`	Checks a domain's `assetlinks.json` (Android) and `apple-app-site-association` (iPhone) files, with a fix for each problem	No
`check_link`	Checks any deep link, from any vendor (Firebase `page.link`, Branch `app.link`, Strait): where it goes on each platform and what to fix	No
`simulate_tap`	A dry run of one tap from one device or app (Android, iPhone, Instagram, WhatsApp, a preview bot…): what Strait would do and why. Nothing is recorded or billed	Secret
`trace_tap`	Walks a link through nine common channels in one call, one row each; or reads a Live Tap Trace from the website demo with its token	Secret (link) / none (demo token)
`get_workspace`	Who your key is: the workspace, its link domain, custom domains, plan, and what the key may do (full, links only or read only)	No
`search_docs`	Searches these docs, offline	No

The checks without a key share a small per-network budget (a few checks a minute), the same as the free checkers on this site.

Tool	What it does	Changes something?
`list_domains`	Your custom link domains, each one's status (`pending_dns`, then `live`; `verified` once ownership is proven) and the DNS records still to add	No
`add_domain`	Adds a subdomain you own and returns the CNAME and TXT records to add at your DNS provider (Scale and Enterprise, up to 5)	Yes, after you confirm
`remove_domain`	Removes a custom domain; links stop working on it at once	Yes, after you confirm

The full setup is in Custom domains.

"My links open the browser on iPhone. Check my link domain and shop.example.com."
"What happens when someone taps summer inside Instagram on Android?"
"Check https://example.page.link/abc before we move it to Strait."
"Add links.example.com as a custom domain and tell me which DNS records to create."