tools/list to inspect it. Registration does not establish hosted availability. Read capability status before depending on a data provider or delivery transport.
Authenticated cloud tools have REST endpoints under /v1/. The anonymous verify_link_free tool uses POST /free/check and /free/mcp.
Provider admission gates apply to request_competitor_inventory, request_domain_overview, discover_backlinks. Without the required provider configuration, these operations refuse with PROVIDER_NOT_CONFIGURED. No tool collects payment.
- Workspace Access
- Link Monitoring
- Destination Health
- Import Verification
- Discovery
- Competitor Intelligence
- Contacts
- Delivery Webhooks
Repository-local context tools
The registry separately defines 8 context tools:context_status, context_manual, context_focus, context_gsc_page, context_gsc_refresh, context_gsc_import, context_profile_build, context_profile_check. They run through the local stdio MCP host against the customer’s repository and are absent from hosted HTTP MCP.
These tools cover manual site inputs, Search Console context, public site facts and citation checks. Manual inputs and imported context do not require a Google connection; direct refresh requires its own authorization. See local records and capability status for the local package and access boundaries.