verify_proof_of_play — Trillboards DOOH Advertising MCP Tool
verify_proof_of_play
(verify proof of play) is one of 83 tools on the
Trillboards DOOH Advertising
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_proof_of_play from your client
- Claude Code Trillboards DOOH Advertising verify_proof_of_play run in your project directory
- Claude Desktop Trillboards DOOH Advertising verify_proof_of_play ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Trillboards DOOH Advertising verify_proof_of_play ~/.cursor/mcp.json
- VS Code Trillboards DOOH Advertising verify_proof_of_play .vscode/mcp.json
- Zed Trillboards DOOH Advertising verify_proof_of_play ~/.config/zed/settings.json
- Windsurf Trillboards DOOH Advertising verify_proof_of_play ~/.codeium/windsurf/mcp_config.json
- Cline Trillboards DOOH Advertising verify_proof_of_play ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Trillboards DOOH Advertising verify_proof_of_play ~/.gemini/settings.json
- Grok Trillboards DOOH Advertising verify_proof_of_play .mcp.json (in your project root)
- ChatGPT Trillboards DOOH Advertising verify_proof_of_play Settings → Connectors → Advanced → Developer mode
- Claude.ai Trillboards DOOH Advertising verify_proof_of_play Settings → Connectors → Add custom connector
- LangChain Trillboards DOOH Advertising verify_proof_of_play pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http trillboards-dooh https://api.trillboards.com/mcpOther tools on this server
- register_partner
- get_partner_info
- register_device
- list_devices
- get_device
- delete_device
- get_device_ads
- record_impression
- batch_impressions
- device_heartbeat
- get_analytics
- create_webhook
- list_webhooks
- update_webhook
- delete_webhook
- test_webhook
- get_webhook_deliveries
- discover_inventory
- get_live_audience
- get_audience_forecast
- create_campaign
- get_campaign_performance
- get_network_stats
- get_signals
- activate_signal
- get_adcp_capabilities
- get_products
- list_creatives
- list_creative_formats
- get_media_buys
- create_media_buy
- update_media_buy
- sync_creatives
- get_media_buy_delivery
- provide_performance_feedback
- log_event
- list_accounts
- sync_accounts
- get_task_status
- tasks_get
- list_tasks
- tasks_list
- get_pricing
- get_usage_summary
- setup_billing
- purchase_credits
- get_billing_status
- get_campaign_attribution
- get_attribution_timeseries
- get_attention_metrics
- get_creative_attention
- get_multi_touch_attribution
- get_cross_channel_journey
- get_incrementality
- create_experiment
- get_creative_attribution
- get_roas
- export_cohort
- get_audience_lookalike
- semantic_audience_search
- get_campaign_heatmap
- query_observations
- semantic_search_observations
- anomaly_detect
- cross_signal_correlate
- configure_sensing
- export_dataset
- predictive_query
- get_social_attention
- find_similar_moments
- predict_moment_quality
- recommend_creative
- get_social_contagion_summary
- get_dataset_stats
- get_content_performance
- search_content
- get_content_recommendations
- list_endpoints
- describe_endpoint
- validate_request
- list_error_codes
- query_changelog
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.