Should my agent depend on the MCP server io.poolparty/main-stage-airtime?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

PoolParty Main Stage Airtime

io.poolparty/main-stage-airtime

Inspectable public airtime for agents routing demo media, launch videos, and proof assets.

— the operator's own registry description reported

Publisher io.poolparty · first seen 2026-08-12 · endpoint https://www.poolparty.io/api/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.58 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency187 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools71

vs populationhigh

capabilities3

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_797ac955e252b11f6ce70f76 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

accept_programming_proposal admit_programming_candidates attach_wallet_to_session browse_channels check_key_request_status claim_test_collateral claim_test_pol complete_media_upload complete_sim_pool_back configure_open_call create_channel_from_template create_join_session create_program_item draft_program_queue draft_slide_block_from_project finalize_block_mint finalize_pool_support get_airtime_opportunity get_block_economics get_block_mint_status get_block_type_schema get_channel_feed get_channel_metrics get_channel_stream get_collateral_opportunity get_distribution_report get_key_info get_open_submission_calls get_paid_action_receipt get_platform_pulse get_pooling_receipt get_program_mode_manifest get_reward_opportunities get_sim_signer_access get_sponsor_opportunities get_superblock_offerings get_wallet_pooling_state insert_live_next inspect_channel_programming_policy inspect_programming_discovery_inventory list_block_types list_channel_templates list_live_queue list_program_modes list_program_queue list_programming_buckets list_programming_candidates list_programming_scope_profiles pool_block prepare_block_mint prepare_superblock_purchase preview_channel_template preview_programming_candidate preview_slide_block propose_program_order publish_program_queue quote_sponsor_reservation quote_superblock_reservation remove_live_queue_item reorder_program_queue request_media_upload_url request_pilot_key resolve_channel revise_slide_block set_programming_bucket settle_paid_action simulate_program_queue_publish skip_current_live_item submit_media_block update_channel_settings withdraw_pool_support

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	71/71	✓
has a description	71/71	✓
description is substantive	71/71	✓
parameters are typed	70/71	70/71
parameters are described	69/71	69/71

71 of 71 tools graded · 71 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.20.21

server version poolparty

Capabilities: prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T20:00:24Z	ok_tools	200	187	2025-06-18
2026-08-12T05:35:35Z	ok_tools	200	183	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.poolparty/main-stage-airtime.svg)](https://robinsaige.com/s/io.poolparty/main-stage-airtime)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview