Is com.sulvo.publisher-revenue-audit/audit up? Live MCP status

Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.

A stock client connected with no credential and negotiated 2025-11-25. Use it.

Outcomeusable
HTTP status200
Protocol version2025-11-25
Server says it ispublisher-revenue-screen 0.3.4
Answered in240 ms
Endpoint checkedhttps://publisher-revenue-audit.sulvo.com/mcp
Checked

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://publisher-revenue-audit.sulvo.com/mcp/server-card
MCP server card (SEP-1649 location)Not published (HTTP 404).
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://publisher-revenue-audit.sulvo.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 41 tools: apply_for_sulvo_account, attach_sulvo_revenue_audit, check_crawler_blocks, check_https_certificate, connect_sulvo_backup_provider, create_sulvo_ad_unit, create_sulvo_auto_sticky_units, create_sulvo_interstitial_units, create_sulvo_signup_account, delete_sulvo_ad_unit, delete_sulvo_advanced_report, get_publisher_monetization_benchmarks, get_publisher_revenue_audit_checklist, get_sulvo_activation_smoke_status, get_sulvo_boost_setup, get_sulvo_installation_instructions, get_sulvo_report, get_sulvo_revenue_onboarding_status, get_sulvo_signup_ads_txt, get_sulvo_signup_status, import_sulvo_backup_units, list_sulvo_advanced_reports, lock_sulvo_placement_revision, map_sulvo_placement_backup, review_sulvo_placement_recommendations, rollback_sulvo_activation, run_agentic_readiness_audit, run_publisher_revenue_audit, run_sulvo_activation_preflight, save_sulvo_advanced_report, save_sulvo_placement_plan, set_sulvo_onboarding_journey, start_sulvo_revenue_onboarding, start_sulvo_signup, submit_sulvo_activation_workspace, submit_sulvo_signup_documents, submit_sulvo_site_for_approval, update_sulvo_signup_company, verify_sulvo_placement_installation, verify_sulvo_signup_ads_txt, verify_sulvo_site_ownership.

Its tools changed between 2026-09 and 2026-10:

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry namecom.sulvo.publisher-revenue-audit/audit
DescriptionPublisher revenue audit: ads.txt and ad-stack checks, Sulvo onboarding, and Boost ad-block recovery
Endpointhttps://publisher-revenue-audit.sulvo.com/mcp
Publisher repositorynone listed
Version0.2.1
Listing updated

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy