Publisher revenue audit: ads.txt and ad-stack checks, Sulvo onboarding, and Boost ad-block recovery
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
start_sulvo_revenue_onboardingNo description publishedThis tool published no description. Forge does not invent one.
get_sulvo_revenue_onboarding_statusNo description publishedThis tool published no description. Forge does not invent one.
get_sulvo_boost_setupNo description publishedThis tool published no description. Forge does not invent one.
run_publisher_revenue_auditNo description publishedThis tool published no description. Forge does not invent one.
apply_for_sulvo_accountNo description publishedThis tool published no description. Forge does not invent one.
start_sulvo_signupNo description publishedThis tool published no description. Forge does not invent one.
create_sulvo_signup_accountNo description publishedThis tool published no description. Forge does not invent one.
update_sulvo_signup_companyNo description publishedThis tool published no description. Forge does not invent one.
get_sulvo_signup_ads_txtNo description publishedThis tool published no description. Forge does not invent one.
verify_sulvo_signup_ads_txtNo description publishedThis tool published no description. Forge does not invent one.
get_sulvo_signup_statusNo description publishedThis tool published no description. Forge does not invent one.
submit_sulvo_signup_documentsNo description publishedThis tool published no description. Forge does not invent one.
0 of 12 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Publisher revenue audit: ads.txt and ad-stack checks, Sulvo onboarding, and Boost ad-block recovery
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.