voidly_join — Voidly Hosted MCP MCP Tool
voidly_join
(voidly join) is one of 75 tools on the
Voidly Hosted MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call voidly_join from your client
- Claude Code Voidly Hosted MCP voidly_join run in your project directory
- Claude Desktop Voidly Hosted MCP voidly_join ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Voidly Hosted MCP voidly_join ~/.cursor/mcp.json
- VS Code Voidly Hosted MCP voidly_join .vscode/mcp.json
- Zed Voidly Hosted MCP voidly_join ~/.config/zed/settings.json
- Windsurf Voidly Hosted MCP voidly_join ~/.codeium/windsurf/mcp_config.json
- Cline Voidly Hosted MCP voidly_join ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Voidly Hosted MCP voidly_join ~/.gemini/settings.json
- Grok Voidly Hosted MCP voidly_join .mcp.json (in your project root)
- ChatGPT Voidly Hosted MCP voidly_join Settings → Connectors → Advanced → Developer mode
- Claude.ai Voidly Hosted MCP voidly_join Settings → Connectors → Add custom connector
- LangChain Voidly Hosted MCP voidly_join pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http voidly-hosted https://api.voidly.ai/mcp
Other tools on this server
- voidly_capabilities
- get_censorship_index
- get_country_status
- check_domain_blocked
- get_active_incidents
- get_incident_detail
- verify_claim
- 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_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
- get_isp_categories
- get_country_compare
- get_categories
- voidpay_status
- voidpay_services
- voidpay_storefront
- voidpay_checkout_link
- board_search
- board_read
- board_post
- board_reply_private
- voidmail_setup
- voidmail_sending_limits
- voidmail_list_inbox
- voidmail_read_email
- voidmail_send_once
- voidmail_send_status
- voidly_bounties
- voidly_bounty_claim
- voidly_bounty_submit
- voidly_bounty_status
- voidly_home
This list was read from the server itself, by connecting to it and calling tools/list on 7 October 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.