# com.sulvo.publisher-revenue-audit/audit

> Publisher revenue audit: ads.txt and ad-stack checks, Sulvo onboarding, and Boost ad-block recovery

- name: com.sulvo.publisher-revenue-audit/audit
- version: 0.2.1
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 72/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.sulvo.publisher-revenue-audit%2Faudit
- tools: https://api.protogrid.dev/v1/servers/com.sulvo.publisher-revenue-audit%2Faudit/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% ~updated-84d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 72/100 (needs work)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 79 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 41 of 41 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: delete_sulvo_advanced_report (idempotentHint); get_publisher_revenue_audit_checklist (idempotentHint); delete_sulvo_ad_unit (idempotentHint); …
- warn `tools.token_cost`: about 8,889 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 75 (weight 15)

- warn `stability.changes`: 41 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: 50 (weight 15)

- warn `deps.known_vulns`: 1 advisory of lower severity or without a published fix: GHSA-5r4p-p66f-jhc7 in hono@4.13.9 (indirect, fixed in 4.13.11)
- fail `deps.mcp_sdk_version`: @modelcontextprotocol/sdk 1.30.1 has 3 known advisories (GHSA-22jm-h49p-29qw, GHSA-6prh-2h8m-c8cw, GHSA-6qxp-vccf-f47h); update @modelcontextprotocol/sdk to 1.32.0 or later
- pass `deps.resolvable`: publisher-revenue-audit-mcp@0.2.1 resolved: 132 packages

- tools: 41, about 8,889 tokens to load them all
- tool set hash: 7bc1b9a66e2ec9266142f410c3692ed8
- tools last changed: 2026-10-02T18:03:46.330Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.sulvo.publisher-revenue-audit/audit.svg)](https://protogrid.dev/servers/com.sulvo.publisher-revenue-audit/audit)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-02 `delete_sulvo_advanced_report` changed (annotations)
- 2026-10-02 `save_sulvo_advanced_report` changed (annotations)
- 2026-10-02 `list_sulvo_advanced_reports` changed (annotations)
- 2026-10-02 `get_sulvo_report` changed (annotations)
- 2026-10-02 `delete_sulvo_ad_unit` changed (annotations)
- 2026-10-02 `create_sulvo_auto_sticky_units` changed (annotations)
- 2026-10-02 `create_sulvo_interstitial_units` changed (annotations)
- 2026-10-02 `create_sulvo_ad_unit` changed (annotations)
- 2026-10-02 `get_publisher_monetization_benchmarks` changed (annotations)
- 2026-10-02 `get_publisher_revenue_audit_checklist` changed (annotations)

Full history: https://api.protogrid.dev/v1/servers/com.sulvo.publisher-revenue-audit%2Faudit/changes

## Dependencies

- npm publisher-revenue-audit-mcp@0.2.1: resolved, 131 dependencies, MCP SDK @modelcontextprotocol/sdk 1.30.1
  - GHSA-22jm-h49p-29qw (high) in `` @modelcontextprotocol/sdk@1.30.1 ``, direct, fixed in `` 1.32.0 ``, advisory summary: "MCP TypeScript SDK: Experimental tasks were not tied to the session that created them" https://osv.dev/vulnerability/GHSA-22jm-h49p-29qw
  - GHSA-6qxp-vccf-f47h (high) in `` @modelcontextprotocol/sdk@1.30.1 ``, direct, fixed in `` 1.31.0 ``, advisory summary: "MCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server" https://osv.dev/vulnerability/GHSA-6qxp-vccf-f47h
  - GHSA-6prh-2h8m-c8cw (moderate) in `` @modelcontextprotocol/sdk@1.30.1 ``, direct, fixed in `` 1.32.0 ``, advisory summary: "MCP TypeScript client SDK: HTTP client transports and OAuth requests followed cross-origin redirects and re-sent custom headers and request bodies" https://osv.dev/vulnerability/GHSA-6prh-2h8m-c8cw
  - GHSA-5r4p-p66f-jhc7 (moderate) in `` hono@4.13.9 ``, indirect, fixed in `` 4.13.11 ``, advisory summary: "Hono: \`serveStatic\` decodes the request path a second time, leading to bypass of middleware on static paths" https://osv.dev/vulnerability/GHSA-5r4p-p66f-jhc7

Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0.

## Remotes

- https://publisher-revenue-audit.sulvo.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

- npm publisher-revenue-audit-mcp@0.2.1

## 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 generation should wait for Sulvo account approval.
- `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 403 against our scanner is a medium-confidence warn that needs verification.
- `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 within 14 days. Does not write a finding when both HTTP and HTTPS are unreachable.
- `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 — an account owner mints a write-scoped key in the Sulvo dashboard (Account Settings -> API key). The Sulvo account must be approved; the backend rejects unapproved accounts. Returns the created unit id and container root.
- `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 and review.
- `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 must own the unit; the backend enforces ownership.
- `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 Fastly, plus the WordPress plugin for publishers who would rather not use a terminal.
- `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). Covers by-date, by-date-and-ad-unit, by-domain-and-ad-unit, bot-filtering, bot-scores, invalid-activity, direct-bidder-analysis, and ad-units-by-domain.
- `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 guessing approval state.
- `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 schema, and a product/deals catalog. Returns what a buyer agent would see and what it cannot.
- `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 unblocked premium ad unit opportunities (such as Sulvo) to recover lost yield.
- `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 the reports:write scope) in the server environment. Note: advanced reports are delivered by email, not returned inline.
- `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 account - not through this connector, which has no access to the user's local files.
- `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.