# Sulvo Publisher Revenue Audit Audit MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.sulvo.publisher-revenue-audit%2Faudit
Registry id: `mcp-registry/com.sulvo.publisher-revenue-audit/audit`
Status: live (checked 2026-10-27T03:27:09.571Z)

## Measurements (30 days)

- Uptime: 99.95%
- Checks: 4972
- Outages (90 days): 7

## Install

```json
{
  "mcpServers": {
    "sulvo-publisher-revenue-audit-audit-mcp-": {
      "type": "http",
      "url": "https://publisher-revenue-audit.sulvo.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http sulvo-publisher-revenue-audit-audit-mcp- https://publisher-revenue-audit.sulvo.com/mcp
```

## Tools (41)

- `apply_for_sulvo_account`: Submit an unauthenticated Sulvo account application lead through the current signup API. Audit tools remain available without login, API key, or OAuth; ad-unit 
- `attach_sulvo_revenue_audit`: Attach a current public revenue audit artifact. Input requires expectedVersion and auditArtifactId.
- `check_crawler_blocks`: Check whether robots.txt or a live probe blocks AmazonAdBot / Google ad crawlers. robots.txt Disallow and Amazon Crawl-delay are high-confidence fails. A WAF 40
- `check_https_certificate`: Check a publisher domain for HTTPS and certificate issues: expired/untrusted/hostname-mismatch certs, HTTPS down, HTTP that does not upgrade, and certs expiring
- `connect_sulvo_backup_provider`: Return the GAM or AdSense authorization URL. Input requires provider set to gam or adsense.
- `create_sulvo_ad_unit`: Create a Sulvo ad unit for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment, never passed as an argument
- `create_sulvo_auto_sticky_units`: Create Sulvo auto-sticky ad units for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment.
- `create_sulvo_interstitial_units`: Create Sulvo interstitial ad units (tagless) for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment.
- `create_sulvo_signup_account`: Run normal Sulvo signup step 2: create the pending Sulvo user/account. The current signup backend requires a password before the account can continue to ads.txt
- `delete_sulvo_ad_unit`: Delete a Sulvo ad unit by id for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment. The key's account mus
- `delete_sulvo_advanced_report`: Delete a saved Sulvo advanced report by id. Requires SULVO_API_KEY (with the reports:write scope) in the server environment.
- `get_publisher_monetization_benchmarks`: Get comparative yield and CPM industry benchmarks by publisher vertical to compare standard stacks (AdSense and managed wrappers) against Sulvo Premium Ad Units
- `get_publisher_revenue_audit_checklist`: Return the public checklist and interpretation notes used by the publisher revenue-readiness screen.
- `get_sulvo_activation_smoke_status`: Return active-probe, real-page, and remediation status for the latest activation attempt.
- `get_sulvo_boost_setup`: Instructions for setting up Sulvo Boost: first-party serving from the publisher's own CDN that recovers ad-blocked impressions. Covers Cloudflare, AWS and Fastl
- `get_sulvo_installation_instructions`: Return installation values for the locked revision. Input is empty.
- `get_sulvo_report`: Fetch a Sulvo report (read-only). Requires SULVO_API_KEY in the server environment (a publisher generates it in the dashboard: Account Settings -> API key). Cov
- `get_sulvo_revenue_onboarding_status`: Return the backend-owned journey stage, readiness dimensions, and one next best action.
- `get_sulvo_signup_ads_txt`: Run normal Sulvo signup step 4a: fetch the ads.txt lines the publisher must add for site ownership verification.
- `get_sulvo_signup_status`: Return the current signup status capability. The current signup API has no public approval-status endpoint, so this tool reports that limitation instead of gues
- `import_sulvo_backup_units`: Import connected provider units. Input requires provider and expectedVersion.
- `list_sulvo_advanced_reports`: List the saved Sulvo advanced reports for the account. Requires SULVO_API_KEY (with the reports:read scope) in the server environment.
- `lock_sulvo_placement_revision`: Lock the exact mapped revision. Input requires expectedVersion and revisionId.
- `map_sulvo_placement_backup`: Map a display placement backup. Input requires expectedVersion, stablePlacementId, provider, and providerId.
- `review_sulvo_placement_recommendations`: Save accept, edit, or reject decisions. Input requires expectedVersion and decisions.
- `rollback_sulvo_activation`: Return the workspace domain to publisher-owned backup-only serving.
- `run_agentic_readiness_audit`: Free top-of-funnel scan: could a buyer agent find and buy this publisher? Checks adagents.json, standardized taxonomy tagging, audience segments in a readable s
- `run_publisher_revenue_audit`: Run a public publisher revenue-readiness screen using directional public evidence. Audits ad stacks, ads.txt hygiene, consent readiness, PageSpeed metrics, and 
- `run_sulvo_activation_preflight`: Run the complete bounded activation preflight for the locked workspace revision.
- `save_sulvo_advanced_report`: Create/update a Sulvo advanced report (adUnit, dimensions, or customData), run immediately (emailed) or on a recurring schedule. Requires SULVO_API_KEY (with th
- `save_sulvo_placement_plan`: Save a placement revision. Input requires expectedVersion and payload.
- `set_sulvo_onboarding_journey`: Set or change the journey intake answers on the workspace. Input requires expectedVersion plus at least one of mode, goal, retagTiming.
- `start_sulvo_revenue_onboarding`: Create or resume a verified-account activation workspace after the public audit and signup steps.
- `start_sulvo_signup`: Run normal Sulvo signup step 1: verify the publisher domain and create the unauthenticated signup lead.
- `submit_sulvo_activation_workspace`: Submit the proven revision. Input requires expectedVersion and revisionId.
- `submit_sulvo_signup_documents`: Explains how to complete Sulvo signup document review. Document submission is done in Sulvo onboarding - upload monthly earnings proof or connect an AdSense acc
- `submit_sulvo_site_for_approval`: Retag-after-approval journeys: submit the bare site for Google approval (ads.txt ownership only, no tags). Input requires expectedVersion.
- `update_sulvo_signup_company`: Run normal Sulvo signup step 3: save optional company information for a pending Sulvo signup.
- `verify_sulvo_placement_installation`: Verify every stable placement container and the inert loader for the locked revision.
- `verify_sulvo_signup_ads_txt`: Run normal Sulvo signup step 4b: verify whether the submitted publisher domain has the required Sulvo ads.txt lines.
- `verify_sulvo_site_ownership`: Verify the required ads.txt and inert Sulvo head-tag ownership evidence.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.