mcpbeat

Audit MCP Server

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

Audit is answering right now. Last checked 8 min ago. 402 installs a week from npm. It exposes 37 tools.

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

Installs per day peak 163 · avg 15 · +3250% w/w
a month agotoday
Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
37
Tools
read from the server
395 ms
Response time
average over 24h
402
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add audit --transport http https://publisher-revenue-audit.sulvo.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "audit": {
      "url": "https://publisher-revenue-audit.sulvo.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.audit]
url = "https://publisher-revenue-audit.sulvo.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "audit": {
      "url": "https://publisher-revenue-audit.sulvo.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "audit": {
      "url": "https://publisher-revenue-audit.sulvo.com/mcp"
    }
  }
}

Available tools 37

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

sulvo
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_sulvo_activation_smoke_status
Return active-probe, real-page, and remediation status for the latest activation attempt.
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.
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.
run_sulvo_activation_preflight
Run the complete bounded activation preflight for the locked workspace revision.
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.
update_sulvo_signup_company
Run normal Sulvo signup step 3: save optional company information for a pending Sulvo signup.
publisher
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.
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.
submit
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.
verify
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.
save
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.
start
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.
apply
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
attach_sulvo_revenue_audit
Attach a current public revenue audit artifact. Input requires expectedVersion and auditArtifactId.
connect
connect_sulvo_backup_provider
Return the GAM or AdSense authorization URL. Input requires provider set to gam or adsense.
import
import_sulvo_backup_units
Import connected provider units. Input requires provider and expectedVersion.
lock
lock_sulvo_placement_revision
Lock the exact mapped revision. Input requires expectedVersion and revisionId.
map
map_sulvo_placement_backup
Map a display placement backup. Input requires expectedVersion, stablePlacementId, provider, and providerId.
review
review_sulvo_placement_recommendations
Save accept, edit, or reject decisions. Input requires expectedVersion and decisions.
rollback
rollback_sulvo_activation
Return the workspace domain to publisher-owned backup-only serving.

Endpoints

URLTransportStateLatencyChecked
https://publisher-revenue-audit.sulvo.com/mcp streamable-http answering 458 ms 8 min ago

Audit — questions

Answers built from our own checks of this server.

What can Audit do?
It exposes 37 tools, read directly from the server on our last check. Among them: apply_for_sulvo_account, attach_sulvo_revenue_audit, connect_sulvo_backup_provider, create_sulvo_ad_unit, create_sulvo_auto_sticky_units, create_sulvo_interstitial_units and 31 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Audit mostly used for?
Its tools cluster around sulvo, verify and submit. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Audit working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 395 ms. The bar chart above shows every period we have measured.
How do I connect Audit?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Audit need an API key?
No. Audit completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 37 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Audit?
It answers our handshake in 395 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Audit?
The npm package publisher-revenue-audit-mcp was installed 402 times in the last week. Week over week that is +3250%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.