Home / MCP registry index / io.github.voidly-ai/voidly-hosted
Voidly Hosted MCP
io.github.voidly-ai/voidly-hosted in the official MCP registry.
Endpoint https://api.voidly.ai/mcp.
The registry describes it as: Voidly MCP: research, Atlas score, capabilities; gated Voidpay, Voidmail, Home, board and bounty.
We read its 85 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
start_here voidly_capabilities get_censorship_index get_country_status check_domain_blocked get_active_incidents get_incident_detail verify_claim country_brief explain_outage watch watch_list watch_delete get_risk_forecast get_platform_risk check_service_accessibility get_most_censored agent_relay_stats get_shutdown_risk get_shutdown_risk_leaderboard get_shutdown_risk_accountability get_early_warning_protocol get_early_warning_commitments get_atlas_score get_multi_horizon_forecast get_global_heatmap get_high_risk_countries get_election_risk get_upcoming_elections get_isp_risk_index get_platform_scores get_incident_stats get_incident_report get_incident_evidence export_incidents get_incidents_since get_classifier_score get_classifier_info get_anomaly_dbscan get_probe_stats get_data_freshness get_prediction_track_record get_ai_service_availability get_country_profile get_censorship_techniques get_censorship_technique_trend get_censorship_by_category get_most_blocked_domains get_data_confidence get_censorship_by_region get_measurement_freshness get_censorship_intent get_category_leaders get_co_blocking get_network_depth get_category_coverage get_censorship_summary get_national_blocklist get_domain_timeline get_classifier_scope and 25 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-voidly-ai-voidly-hosted)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.