Voidly MCP Server

@voidly/mcp-server npm v2.17.0

Published by @voidly — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

84-tool MCP server: censorship intelligence (119 countries, 19.6M measurements) + E2E encrypted agent-to-agent messaging (Double Ratchet, X3DH, post-quantum) + Voidly Pay onboarding (agent-to-agent payments, x402, USDC on Base)

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: agent_unread_count → agent_export_data → agent_join_channel. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow agent_unread_count → agent_export_data → agent_join_channel

medium Unconstrained URL/host parameter "webhook_url" on "agent_register_webhook"MTC-CAP-007

Tool "agent_register_webhook" takes a URL/host parameter "webhook_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool agent_register_webhook · inputSchema.properties.webhook_url

Tools 87

Each tool and what it can reach — statically extracted from the published source.

  • agent_export_datareads sensitive data
  • agent_join_channelnetwork egress
  • agent_register_webhooknetwork egress
  • agent_send_messagenetwork egress
  • agent_unread_countingests untrusted input
  • agent_analyticsno sensitive capability
  • agent_broadcast_taskno sensitive capability
  • agent_corroborateno sensitive capability
  • agent_create_attestationno sensitive capability
  • agent_create_channelno sensitive capability
Show 77 more tools ↓
  • agent_create_taskno sensitive capability
  • agent_deactivateno sensitive capability
  • agent_delete_capabilityno sensitive capability
  • agent_delete_messageno sensitive capability
  • agent_discoverno sensitive capability
  • agent_get_attestationno sensitive capability
  • agent_get_broadcastno sensitive capability
  • agent_get_consensusno sensitive capability
  • agent_get_identityno sensitive capability
  • agent_get_profileno sensitive capability
  • agent_get_taskno sensitive capability
  • agent_get_trustno sensitive capability
  • agent_invite_to_channelno sensitive capability
  • agent_key_pinno sensitive capability
  • agent_key_pinsno sensitive capability
  • agent_key_verifyno sensitive capability
  • agent_list_broadcastsno sensitive capability
  • agent_list_capabilitiesno sensitive capability
  • agent_list_channelsno sensitive capability
  • agent_list_invitesno sensitive capability
  • agent_list_tasksno sensitive capability
  • agent_list_webhooksno sensitive capability
  • agent_mark_readno sensitive capability
  • agent_mark_read_batchno sensitive capability
  • agent_memory_deleteno sensitive capability
  • agent_memory_getno sensitive capability
  • agent_memory_listno sensitive capability
  • agent_memory_namespacesno sensitive capability
  • agent_memory_setno sensitive capability
  • agent_pingno sensitive capability
  • agent_ping_checkno sensitive capability
  • agent_post_to_channelno sensitive capability
  • agent_query_attestationsno sensitive capability
  • agent_read_channelno sensitive capability
  • agent_receive_messagesno sensitive capability
  • agent_registerno sensitive capability
  • agent_register_capabilityno sensitive capability
  • agent_relay_statsno sensitive capability
  • agent_respond_inviteno sensitive capability
  • agent_search_capabilitiesno sensitive capability
  • agent_trust_leaderboardno sensitive capability
  • agent_update_profileno sensitive capability
  • agent_update_taskno sensitive capability
  • agent_verify_messageno sensitive capability
  • check_domain_blockedno sensitive capability
  • check_domain_probesno sensitive capability
  • check_service_accessibilityno sensitive capability
  • check_vpn_accessibilityno sensitive capability
  • compare_countriesno sensitive capability
  • get_active_incidentsno sensitive capability
  • get_alert_statsno sensitive capability
  • get_censorship_indexno sensitive capability
  • get_community_leaderboardno sensitive capability
  • get_community_probesno sensitive capability
  • get_country_statusno sensitive capability
  • get_domain_historyno sensitive capability
  • get_domain_statusno sensitive capability
  • get_election_riskno sensitive capability
  • get_high_risk_countriesno sensitive capability
  • get_incident_detailno sensitive capability
  • get_incident_evidenceno sensitive capability
  • get_incident_reportno sensitive capability
  • get_incident_statsno sensitive capability
  • get_incidents_sinceno sensitive capability
  • get_isp_risk_indexno sensitive capability
  • get_isp_statusno sensitive capability
  • get_most_censoredno sensitive capability
  • get_platform_riskno sensitive capability
  • get_probe_networkno sensitive capability
  • get_risk_forecastno sensitive capability
  • Global Censorship Indexno sensitive capability
  • Methodologyno sensitive capability
  • relay_infono sensitive capability
  • relay_peersno sensitive capability
  • verify_claimno sensitive capability
  • Voidly Pay overviewno sensitive capability
  • voidly_pay_overviewno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.17.0 latest A 93/100 2 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/voidly-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/voidly-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/voidly-mcp-server"><img src="https://mcptrustchecker.com/registry/voidly-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/voidly-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @voidly/mcp-server --online

Use the free API → How scoring works

More in Data Science & ML