Included as an SEO intelligence surface whose unified API and beta Moz Data MCP expose Moz's link index, site authority and spam metrics, ranking keywords, keyword metrics and suggestions, search intent, redirects, index metadata, and quota state for agent-assisted research and reporting.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Sites and URLs; site authority, spam, link and ranking metrics; links, linking domains, anchor texts, top pages, redirects, and link status; ranking keywords; keyword volume, difficulty, opportunity, priority, intent, and suggestions; index metadata and quota state.
Use the unified JSON-RPC API or Moz Data MCP to retrieve supported site metrics and history, link relationships and intersections, linking domains, anchor text, top pages, ranking keywords, keyword metrics and suggestions, search intent, redirect targets, current index ID, and quota information.
The Moz Data catalog represented in this profile is analytical and no Data mutation is claimed. Moz Local has create, update, grouping, cancellation, and closure methods, but it is a separate product and MCP endpoint and must not be treated as Moz Data write scope.
Direct unified-API requests use a Moz API token in the `x-moz-token` header at `https://api.moz.com/jsonrpc`. Moz MCP recommends client OAuth and also accepts the same Moz token as an HTTP bearer token. MCP is currently limited to account owners, and each endpoint requires the corresponding Moz Data API or Moz Local subscription.
Keep the Moz Data and Moz Local endpoints as separate connections, show the selected endpoint and subscription, expose the queried site or keyword scope plus current index and quota context, and do not send a Data analysis result into Local location-management methods without a separately approved Local workflow.
Moz MCP is Beta and currently account-owner only; each endpoint requires its matching subscription. The current API is still transitioning versions, so documentation for several link and site methods remains in the legacy help hub. API plans and row quotas are separate from Moz Pro, and repeated 4xx responses can trigger a 50-requests-per-five-minutes throttle.
First-party access
Agent access
Support: Official MCP server
Read scope: For this profile, connect the Moz Data endpoint to site, link, linking-domain, anchor-text, ranking-keyword, keyword-metric, intent, suggestion, index, and quota tools supported by the current catalog.
Write scope: No Moz Data MCP mutation is claimed from the current catalog. Moz Local management actions belong to the separate Local endpoint and subscription and are outside this Moz Pro / Moz API profile.
Authentication: OAuth in the MCP client is recommended. Manual clients may send `Authorization: Bearer <Moz API token>`; the same dashboard token can authenticate either endpoint when the account has the required product subscription.
Approval boundary: Moz Data calls are analytical in this profile, but prompts should still disclose target, scope, locale, requested metrics, and row cost. Any Moz Local create, update, group, cancel, or close action requires a separate Local connection and explicit action review.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Moz ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
First-party API reference or API overview recorded for this platform.
Recorded first-party developer source; summary not endpoint-exhaustive
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
