create_sulvo_interstitial_units — audit MCP Tool Mutating
create_sulvo_interstitial_units
(create sulvo interstitial units) is one of 41 tools on the
audit
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call create_sulvo_interstitial_units from your client
- Claude Code audit create_sulvo_interstitial_units run in your project directory
- Claude Desktop audit create_sulvo_interstitial_units ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor audit create_sulvo_interstitial_units ~/.cursor/mcp.json
- VS Code audit create_sulvo_interstitial_units .vscode/mcp.json
- Zed audit create_sulvo_interstitial_units ~/.config/zed/settings.json
- Windsurf audit create_sulvo_interstitial_units ~/.codeium/windsurf/mcp_config.json
- Cline audit create_sulvo_interstitial_units ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI audit create_sulvo_interstitial_units ~/.gemini/settings.json
- Grok audit create_sulvo_interstitial_units .mcp.json (in your project root)
- ChatGPT audit create_sulvo_interstitial_units Settings → Connectors → Advanced → Developer mode
- Claude.ai audit create_sulvo_interstitial_units Settings → Connectors → Add custom connector
- LangChain audit create_sulvo_interstitial_units pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http audit https://publisher-revenue-audit.sulvo.com/mcpOther tools on this server
- check_https_certificate
- run_agentic_readiness_audit
- check_crawler_blocks
- get_sulvo_boost_setup
- start_sulvo_revenue_onboarding
- get_sulvo_revenue_onboarding_status
- attach_sulvo_revenue_audit
- connect_sulvo_backup_provider
- import_sulvo_backup_units
- review_sulvo_placement_recommendations
- save_sulvo_placement_plan
- map_sulvo_placement_backup
- get_sulvo_installation_instructions
- verify_sulvo_placement_installation
- lock_sulvo_placement_revision
- run_sulvo_activation_preflight
- verify_sulvo_site_ownership
- submit_sulvo_activation_workspace
- submit_sulvo_site_for_approval
- set_sulvo_onboarding_journey
- rollback_sulvo_activation
- get_sulvo_activation_smoke_status
- run_publisher_revenue_audit
- apply_for_sulvo_account
- start_sulvo_signup
- create_sulvo_signup_account
- update_sulvo_signup_company
- get_sulvo_signup_ads_txt
- verify_sulvo_signup_ads_txt
- get_sulvo_signup_status
- submit_sulvo_signup_documents
- get_publisher_revenue_audit_checklist
- get_publisher_monetization_benchmarks
- create_sulvo_ad_unit
- create_sulvo_auto_sticky_units
- delete_sulvo_ad_unit
- get_sulvo_report
- list_sulvo_advanced_reports
- save_sulvo_advanced_report
- delete_sulvo_advanced_report
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.