← Back to search
npm-voidly/mcp-server

@voidly/mcp-server

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)

DECISION SUMMARY

Block For Production

Score
47.4
Top 87.3% of 73,519 scored public servers
Confidence
Medium
Based on evidence completeness, recency, and validation density.
Evidence age
3.2h old
Freshness: fresh. Snapshot trustsnap_d4e3a59035d9aac6.
Top risk drivers
  • Transport Compliance
  • Tool Surface Design
  • Tool Snapshot Churn
Recommended actions
  • Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card.
  • Allow initialize to succeed consistently, or return a deterministic auth-required response with clear metadata.
  • Fix the failing checks first, then revalidate to confirm the recovery path.
Production decision
Block for production
failing live status + score below evaluation threshold
Current score
47.4
Snapshot trustsnap_d4e3a59035d9aac6
Next action
revalidate, add safeguards, export policy
Claim the profile to add evidence, trigger validation, and configure monitoring.
Compare alternatives Export policy Open report JSON
Observed Attention
No observed attention
No observed attention in the current 30-day window.
  • No segmented attention signals observed in the current window.
Bucketed signal based on recent segmented Verify telemetry. Crawler and evaluator activity is not treated as confirmed human demand.
Status
Failing
Score
47.4
Transport
streamable-http
Tools
0

Current trust snapshot

Snapshot ID
trustsnap_d4e3a59035d9aac6
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
Aug 04, 2026 01:44:16 PM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
Aug 04, 2026 10:31:33 AM UTC
Age: 3.21h • freshness band: Verified in last 24h • display score: 47.42
Production trust decision
Block for production
failing live status + score below evaluation threshold
Readiness class
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.

Canonical machine links

SERVER OWNER FUNNEL

Own this MCP?

Claim ownership, prove control with a GitHub, DNS, HTTP, MCP metadata, or email-domain challenge, revalidate now, publish a badge, configure monitoring, and unlock a verified server profile.

1. Claim
unclaimed
with GitHub, DNS, or HTTP challenge instructions.
2. Revalidate
POST /v1/servers/npm-voidly/mcp-server/revalidate
Verified owners get priority queueing after proof succeeds.
3. Badge
Verified by MCP Verify badge
Verified by MCP Verify - score 47.4 - last checked Aug 4, 2026
4. Monitor
Continuous Verify plan is self-serve: choose a tier, configure watches, add authenticated validation, trigger revalidation, and use the badge.
Paid profile
Add verified publisher identity, security metadata, evidence packs, badge customization, and owner analytics without buying a better score.
Badge embed
[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/npm-voidly/mcp-server.svg)](https://verify.sentinelsignal.io/servers/npm-voidly/mcp-server)
PUBLISHER READINESS

Publisher readiness checklist

3/7 readiness checks currently pass. Paid status never changes the objective score; it can add evidence, monitoring, badge analytics, and authenticated validation.

Publisher readiness checks for this MCP server
CheckStatusHow to improve
Ownership verified Needs work Prove GitHub, DNS, HTTP, MCP metadata, or domain-email control.
Fresh validation Ready Keep public evidence inside the 48h publisher launch window.
Healthy endpoint Needs work Remote endpoint should initialize and list tools reliably.
Score threshold Needs work Aim for score >= 70 before using production-readiness language.
Metadata complete Ready Publish description, homepage/docs, remote URL, and support metadata.
Risk posture reviewed Needs work Address OAuth, write-action, destructive-tool, and protocol findings.
Badge ready Ready Publish score and freshness badges only when current evidence exists.

Scan or claim this server Open badge kit

MCP TrustOps

TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

Freshness band
Verified in last 24h
Policy SLA: 168.0h • confidence-weighted score: 31.4 • stale score suppressed:
Policy exports
Formats: json, rego, yaml, github_action, gateway_config, client_report
Runtime routing
/v1/decide
Returns allowed tools, blocked tools, approval requirement, and reason.
Hosted runtime
Deploy trusted servers from GitHub with secrets, egress controls, releases, rollback, and audit events.
Authenticated validation
Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.
Active trust badges
Freshly Validated Write-Safe No Critical Risk
Semantic benchmarks
available
Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.
Supply chain
metadata signal
Deep scan checks are marked separately from public metadata signals.
Compliance metadata
Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.
Alert subscription types
Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes

MCP Runtime hosting

Verify Hosted MCP turns a trusted server report into a managed remote MCP endpoint with GitHub deployment provenance, sandbox policy, encrypted secrets, release history, rollback, and audit/usage events.

Activation readiness
Trusted hosted runtimes require fresh validation, a passing server state, a remote endpoint, and a minimum score.
Minimum tier
TrustOps
Publisher claim plus paid TrustOps tier are required before secrets or releases can be created.
Hosted endpoint
/hosted/{namespace}/{name}/mcp
The endpoint enforces egress allowlists and records audit/usage events.
Blockers
score_below_hosting_threshold server_not_healthy_or_degraded latest_validation_not_passing
DeploymentStatusEndpointRelease
No hosted runtime deployments yet.

Production readiness class

Production readiness class
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Critical alerts
1
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score
66.2
Based on 1 recent validations, 26 captured checks, and validation age of 3.2 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
3.2h
Lower age means fresher evidence.

Recommended for

No recommendation profile is available yet.

Client compatibility verdicts

Client compatibility only means the server shape can work with a client. Production trust decision and write-action publishing are evaluated separately so a client-compatible server can still be blocked for production.

Client compatibility: ChatGPT
Not client-compatible
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Initialize must be reachable.; tools/list must succeed.; Transport compliance should be in good shape.; OAuth interoperability should be strong.
Confidence: medium (66.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeError
  • tools_listError
  • transport_compliance_probeError
  • step_up_auth_probeMissing
  • connector_replay_probeMissing — Frozen tool snapshots must survive refresh.
  • request_association_probeMissing — Roots, sampling, and elicitation should stay request-scoped.
Client compatibility: Claude
Not client-compatible
Initialize must succeed or cleanly request auth.; tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
Confidence: medium (66.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeError
  • tools_listError
  • transport_compliance_probeError
Write-action publishing
Publishing allowed
Current write surface is bounded enough for cautious review with production policy controls.
Confidence: medium (66.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probeOK
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: medium (66.25)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probeMissing
  • connector_replay_probeMissing

Why compatibility is limited by client

ChatGPT custom connector
Not client-compatible
Remediation checklist
  • OpenAI connectors expect OAuth for remote server auth.
  • Dynamic client registration materially improves connector setup.
  • Initialize must be reachable.
  • tools/list must succeed.
  • Transport compliance should be in good shape.
  • OAuth interoperability should be strong.
Claude remote MCP
Not client-compatible
Remediation checklist
  • Initialize must succeed or cleanly request auth.
  • tools/list must succeed.
  • Transport behavior should match Claude-compatible HTTP expectations.
  • A useful Claude integration needs at least one exposed tool.
  • search fetch only is not yet satisfied
  • write actions present is not yet satisfied
Write-safe publishing
Ready
Remediation checklist
  • No explicit blockers recorded.

Verdict traces

Production verdict
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Confidence: medium (66.25)
Winning source: live_validation
Triggering alerts
  • server_failing • critical • Latest validation is failing
  • official_registry_entry_drifted • medium • Official registry entry drifted
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Not client-compatible initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Not client-compatible initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions Publishing allowed action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none

Publishability policy profiles

ChatGPT custom connector compatibility
Compatible with review
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Initialize must be reachable.; tools/list must succeed.; Transport compliance should be in good shape.; OAuth interoperability should be strong. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Compatible with review
Initialize must succeed or cleanly request auth.; tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No

Compatibility fixtures

ChatGPT custom connector fixture
Degraded
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Initialize must be reachable.; tools/list must succeed.; Transport compliance should be in good shape.; OAuth interoperability should be strong.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Degraded
Initialize must succeed or cleanly request auth.; tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
  • remote_transport: Passes
  • tool_discovery: Likely to fail
  • auth_connect: Likely to fail
  • safe_write_review: Passes

Authenticated validation sessions

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

Latest profile
remote_mcp
Authenticated session used
Public score isolation
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview

Public server reputation

Validation success 7d
0.0
Validation success 30d
0.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0

Incident & change feed

TimestampEventDetails
Aug 04, 2026 10:31:33 AM UTC Latest validation: failing Score 47.4 with status failing.

Capabilities

Use-case taxonomy
finance automation

Security posture

Tools analyzed
0
High-risk tools
0
Destructive tools
0
Exec tools
0
Egress tools
0
Secret tools
0
Bulk-access tools
0
Risk distribution
none

Agent Commerce & Payment Readiness - Beta

Beta assessment. Verify separates commerce-adjacent context from observed payment execution. Usage, billing, pricing, card, wallet, or meter terms alone do not make a server payment-capable. This is not a certification of safety, compliance, or fraud prevention.

Overall
None
Auth posture
0
Payment readiness
10
Delegation safety
50
Tool risk
60
Commerce signal: weak Payment capable: none Payment execution: no Billing/usage context: no Quote/pricing context: no Numeric price context: yes Commercial quote context: no Checkout/charge signal: no Checkout term observed: no Human confirmation: unknown Spending policy: yes Receipt support: unknown Auth required: unknown Operator identity: declared Tool risk: unknown Delegation level: none
Detected payment rails
x402, crypto
Purchase stages
none detected
Evidence level
inferred
Confidence
low

Warnings

No commerce-specific warnings generated.

Evidence

FieldValueSourceMatched termsConfidence
commerce_signalweakserver_metadatalimit, ratelow
payment_railsx402, cryptotool_schemax402, cryptomedium

Recommended operator fixes

Tool capability & risk inventory

No tool inventory available from the latest validation run.

Write-action governance

Governance status
OK
Safe to publish
Auth boundary
public_or_unclear
Blast radius
Low
High-risk tools
0
Confirmation signals
none
Safeguard count
0

Status detail: No unsafe write-action governance gaps detected on the latest validation.

ToolRiskFlagsSafeguards
No high-risk tools were detected on the latest run.

Action-controls diff

Need at least two validation runs before diffing action controls.

Why this score?

Access & Protocol
18.5/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
15/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
25/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
9.61/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
20.45/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
4.38/8
Adoption clues and public evidence that the server is intended for external use.

Algorithmic score breakdown

Auth Operability
0/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
1.1/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
0/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
2/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
2.8/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
3/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
1.7/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
0.1/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
2.5/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
1.5/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
1.5/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
2/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
3/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
2/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
0/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
0/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
0/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
0/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0.9/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
4/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
0.5/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
3.5/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
2/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
3/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
3/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
0/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
3/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
2/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
2.4/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
0/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
3/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
3/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
3/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
3/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
3/4
Whether the server appears directly or indirectly in the official MCP registry.
Provenance Divergence
2/4
How closely official registry metadata, the live server card, and public repo/package signals agree with each other.
Safety Transparency
3/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
0/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
3/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
4/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
3/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
2/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
3/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
3.5/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
0/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
0/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

Compatibility profiles

OpenAI Connectors
33.3
blocked
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Initialize must be reachable.; tools/list must succeed.; Transport compliance should be in good shape.; OAuth interoperability should be strong.
Connector URL: https://voidly.ai/mcp
# No OAuth metadata detected.
# Server: npm-voidly/mcp-server
Claude Desktop
33.3
blocked
Initialize must succeed or cleanly request auth.; tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
{
  "mcpServers": {
    "mcp-server": {
      "command": "npx",
      "args": ["mcp-remote", "https://voidly.ai/mcp"]
    }
  }
}
Smithery
40.0
blocked
Tool discovery must succeed.; Initialize should work before execution.; Machine-readable failure semantics should be present.
smithery mcp add "https://voidly.ai/mcp"
Generic Streamable HTTP
50.0
blocked
Initialize must succeed.; tools/list must succeed.; Session behavior should be predictable.
curl -sS https://voidly.ai/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Actionable remediation

SeverityRemediationWhy it mattersRecommended action
Critical Ensure tools/list succeeds consistently Tools discovery is the minimum viable contract for most MCP clients and directories. Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card.
Playbook
  • Make `tools/list` deterministic across repeated calls.
  • Document or relax auth requirements for discovery routes.
  • Check that tool names, descriptions, and schemas remain stable across deploys.
Critical Make initialize deterministic and client-friendly If initialize fails or requires undocumented auth, many MCP clients cannot connect. Allow initialize to succeed consistently, or return a deterministic auth-required response with clear metadata.
Playbook
  • Allow `initialize` to succeed unauthenticated when possible.
  • If auth is required, return a deterministic auth-required response and matching metadata.
  • Retest against `https://voidly.ai/mcp` from a clean client session.
Critical Respond to latest validation is failing Core MCP flows did not validate successfully on the latest run. Fix the failing checks first, then revalidate to confirm the recovery path.
Playbook
  • Fix the failing checks first.
  • Review the latest incident feed and validation diff for the first regression.
  • Revalidate once the remediation lands.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Associate roots, sampling, and elicitation with active client requests Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Expose /.well-known/oauth-protected-resource Without a protected-resource document, OAuth clients cannot discover auth requirements reliably. Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Playbook
  • Serve `/.well-known/oauth-protected-resource` from the same host as the MCP endpoint.
  • Point it at the authorization server metadata URL.
  • Confirm clients receive consistent auth hints before tool execution.
High Keep connector refreshes backward compatible Managed connector clients freeze tool snapshots, so removed tools, new required args, and breaking output changes can break published integrations after refresh. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Publish OAuth authorization-server metadata Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.
Playbook
  • Publish `/.well-known/oauth-authorization-server` from the issuer.
  • Add `registration_endpoint` if DCR is supported.
  • Verify issuer, authorization, token, and jwks metadata are all reachable.
High Stop asking users to paste secrets directly Public MCP servers should prefer OAuth or browser-based auth guidance over in-band secret collection. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Document minimal scopes and return cleaner auth challenges Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.
Playbook
  • Advertise the narrowest viable scopes in OAuth metadata.
  • Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed.
  • Revalidate with both public discovery and auth-required flows.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Raise Interface Quality score How well the tool/resource interface communicates and behaves under automation. Improve schemas, error contracts, and recovery messages so agents can reason about the surface automatically.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Reconcile registry, server-card, and repository metadata Directory trust falls quickly when official registry fields drift from the live server card or public repo metadata. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Reduce tool-surface churn Frequent add/remove or output-shape drift makes published connectors and cached tool snapshots brittle. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Repair prompts/list or stop advertising prompts Prompt metadata should either work live or be removed from the advertised capability set. Only advertise prompts if prompts/list works and prompt arguments are documented.
Playbook
  • Only advertise prompts that are actually accessible.
  • Add prompt descriptions and argument docs.
  • Run a live `prompts/list` check after any prompt changes.
Medium Repair resources/list or stop advertising resources Resource metadata should either work live or be removed from the advertised capability set. Only advertise resources if resources/list works and resources expose stable URIs/types.
Playbook
  • Only advertise resources with stable URIs and read semantics.
  • Add MIME/type hints where possible.
  • Run a live `resources/list` and `resources/read` check after updates.
Medium Respond to official registry entry drifted Registry and live server-card provenance fields are currently out of sync. Update the official registry, server card, or repo metadata until provenance fields align again.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Support resumable HTTP sessions cleanly Modern MCP clients increasingly expect resumable session behavior on streamable HTTP transports. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
Low Publish newer MCP capability signals Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Publish or reconcile the server in the official MCP registry Official registry presence improves discovery confidence and cross-source consistency. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.

Point loss breakdown

ComponentCurrentPoints missing
Transport Compliance 0/4 -4.0
Tool Surface Design 0/4 -4.0
Tool Snapshot Churn 0/4 -4.0
Tool Namespace Clarity 0/4 -4.0
Tool Capability Clarity 0/4 -4.0
Session Semantics 0/4 -4.0
Schema Completeness 0/4 -4.0
Result Shape Stability 0/4 -4.0
OAUTH Interop 0/4 -4.0
Input Sanitization Safety 0/4 -4.0
Auth Operability 0/4 -4.0
Trust Confidence 0.1/4 -3.9

Validation diff

Need at least two validation runs before diffing changes.

Tool snapshot diff & changelog

Need at least two validation runs before building a tool changelog.

Connector replay

Status
Missing
Backward compatible
Would break after refresh
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.

Transport compliance drilldown

Probe status
Error
Transport
streamable-http
Session header
no
Protocol header
no
Bad protocol response
405
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no

Issues: missing_protocol_header, bad_protocol_not_rejected

Request association

Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none

Utility coverage

Probe status
Warning
Completions
advertised
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no

Benchmark tasks

Benchmark taskStatusEvidence
Discover tools Likely to fail
  • initializeError
  • tools_listError
Read-only fetch flow Likely to fail
  • resource_readMissing
  • read_only_tool_surfaceMissing
OAuth-required connect Degraded
  • oauth_protected_resourceError
  • step_up_auth_probeMissing
Safe write flow with confirmation Passes
  • action_safety_probeOK

Registry & provenance divergence

Probe status
Warning
Direct official match
no
Drift fields
title version
FieldRegistryLive server card
Title@voidly/mcp-servervoidly
Version2.17.02.10.0
Homepagen/ahttps://voidly.ai

Active alerts

Aliases & registry graph

IdentifierSourceCanonicalScore
npm-voidly/mcp-server npm_package_discovery yes 47.42

Alias consolidation

Canonical identifier
npm-voidly/mcp-server
Duplicate aliases
0
Registry sources
npm_package_discovery
Source disagreements
FieldWhat differsObserved values
No source disagreements detected.

Install snippets

Openai Connectors
Connector URL: https://voidly.ai/mcp
# No OAuth metadata detected.
# Server: npm-voidly/mcp-server
Claude Desktop
{
  "mcpServers": {
    "mcp-server": {
      "command": "npx",
      "args": ["mcp-remote", "https://voidly.ai/mcp"]
    }
  }
}
Smithery
smithery mcp add "https://voidly.ai/mcp"
Generic Http
curl -sS https://voidly.ai/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Agent access & tool surface

Live server tools
No live tool surface captured yet.
Observed from the latest live validation against https://voidly.ai/mcp. This is the target server surface, not Verify's own inspection tools.
Live capability counts
0 tools • 0 prompts • 0 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search fetch search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for npm-voidly/mcp-server.
Direct machine links

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions
0
Teams: none

Alert routing

Active watches
0
Generic webhooks
0
Slack routes
0
Teams routes
0
Email routes
0
WatchTeamChannelsMinimum severity
No active watch destinations.

Maintainer analytics

Validation Run Count
1
Average Latency Ms
2341.92
Healthy Run Ratio Recent
0.0
Registry Presence Count
1
Active Alert Count
2
Watcher Count
0
Verified Claim
False
Taxonomy Tags
finance, automation
Score Trend
47.42
Remediation Count
23
High Risk Tool Count
0
Destructive Tool Count
0
Exec Tool Count
0

Maintainer response quality

Score
33.33
Verified claim
Support contact
Changelog present
Incident notes present
Tool changes documented
Annotation history
Annotation count
0

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

No maintainer rebuttals or expected-behavior overrides are recorded yet.

Latest validation evidence

Latest summary
Failing
Validation profile
remote_mcp
Started
Aug 04, 2026 10:31:31 AM UTC
Latency
2341.9 ms

Failures

Checks

CheckStatusLatencyEvidence
action_safety_probe OK n/a No high-risk write, destructive, or exec tools detected.
advanced_capabilities_probe Warning n/a Only 1 capability signal(s): completions.
connector_publishability_probe Error n/a Publishability blockers: initialize, tools list, protocol version, transport compliance, +2 more.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe Missing n/a tools list unavailable
initialize Error 604.1 ms Client error '405 Method Not Allowed' for url 'https://voidly.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405
interactive_flow_probe Missing n/a Check completed
oauth_authorization_server Missing n/a no authorization server
oauth_protected_resource Error 244.4 ms Client error '404 Not Found' for url 'https://voidly.ai/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
official_registry_probe Warning n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 81.5 ms Fetched https://voidly.ai/robots.txt
prompt_get Missing n/a no prompt name
prompts_list Error 70.2 ms Client error '405 Method Not Allowed' for url 'https://voidly.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405
protocol_version_probe Missing n/a No protocol version was advertised.
provenance_divergence_probe Warning n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read Missing n/a no resource uri
resources_list Error 143.8 ms Client error '405 Method Not Allowed' for url 'https://voidly.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405
server_card OK 879.6 ms _voidly_pay, capabilities, description, documentation
session_resume_probe Missing n/a no session id
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe Missing n/a no tools
tools_list Error 146.7 ms Client error '405 Method Not Allowed' for url 'https://voidly.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405
transport_compliance_probe Error 115.8 ms Issues: missing protocol header, bad protocol not rejected (bad protocol=405).
utility_coverage_probe Warning 41.3 ms Completions advertised; no pagination evidence; tasks missing.

Raw evidence view

Show raw JSON evidence
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": false,
        "confirmation_signals": [],
        "safeguard_count": 0,
        "summary": {
          "bulk_access_tools": 0,
          "capability_distribution": {},
          "destructive_tools": 0,
          "egress_tools": 0,
          "exec_tools": 0,
          "high_risk_tools": 0,
          "risk_distribution": {
            "critical": 0,
            "high": 0,
            "low": 0,
            "medium": 0
          },
          "secret_tools": 0,
          "tool_count": 0
        }
      },
      "latency_ms": null,
      "status": "ok"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": true,
          "elicitation": false,
          "prompts": false,
          "resource_links": false,
          "resources": false,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [
          "completions"
        ],
        "enabled_count": 1,
        "initialize_capability_keys": []
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "initialize",
          "tools_list",
          "protocol_version",
          "transport_compliance",
          "tool_surface",
          "auth_flow"
        ],
        "criteria": {
          "action_safety": true,
          "auth_flow": false,
          "connector_replay": true,
          "initialize": false,
          "protocol_version": false,
          "remote_transport": true,
          "request_association": true,
          "server_card": true,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": false,
          "tools_list": false,
          "transport_compliance": false
        },
        "high_risk_tools": 0,
        "tool_count": 0,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "error"
    },
    "connector_replay_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "determinism_probe": {
      "details": {
        "reason": "tools_list_unavailable"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "initialize": {
      "details": {
        "error": "Client error '405 Method Not Allowed' for url 'https://voidly.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405",
        "headers": {
          "allow": "GET,HEAD",
          "content-type": "text/html; charset=utf-8",
          "strict-transport-security": "max-age=63072000; includeSubDomains"
        },
        "http_status": 405,
        "payload": {},
        "url": "https://voidly.ai/mcp"
      },
      "latency_ms": 604.14,
      "status": "error"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": false,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_authorization_server": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_protected_resource": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://voidly.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://voidly.ai/.well-known/oauth-protected-resource"
      },
      "latency_ms": 244.42,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": false,
        "official_identifiers": [
          "ai.ai-akari/one-minute-akari",
          "ai.llmintel/llmintel",
          "ai.artidrop/artidrop",
          "ai.justpublish/just-publish",
          "ai.pimea/pimea",
          "ai.afmr/discovery",
          "ai.boolsai/directory",
          "ai.agenticfabricationnetwork/ufp",
          "ai.agenticshelf/graffeo",
          "ac.tandem/docs-mcp"
        ],
        "official_peer_count": 10,
        "registry_source": "npm_package_discovery"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "text/plain; charset=utf-8"
        },
        "http_status": 200,
        "url": "https://voidly.ai/robots.txt"
      },
      "latency_ms": 81.55,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "no_prompt_name"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "error": "Client error '405 Method Not Allowed' for url 'https://voidly.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405",
        "headers": {
          "allow": "GET,HEAD",
          "content-type": "text/html; charset=utf-8",
          "strict-transport-security": "max-age=63072000; includeSubDomains"
        },
        "http_status": 405,
        "payload": {},
        "url": "https://voidly.ai/mcp"
      },
      "latency_ms": 70.15,
      "status": "error"
    },
    "protocol_version_probe": {
      "details": {
        "latest_known_version": "2025-11-25",
        "reason": "no_protocol_version",
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "provenance_divergence_probe": {
      "details": {
        "direct_official_match": false,
        "drift_fields": [
          "title",
          "version"
        ],
        "metadata_document_count": 3,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": "@voidly/mcp-server",
        "registry_version": "2.17.0",
        "server_card_homepage": "https://voidly.ai",
        "server_card_repository": null,
        "server_card_title": "voidly",
        "server_card_version": "2.10.0"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "reason": "no_resource_uri"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resources_list": {
      "details": {
        "error": "Client error '405 Method Not Allowed' for url 'https://voidly.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405",
        "headers": {
          "allow": "GET,HEAD",
          "content-type": "text/html; charset=utf-8",
          "strict-transport-security": "max-age=63072000; includeSubDomains"
        },
        "http_status": 405,
        "payload": {},
        "url": "https://voidly.ai/mcp"
      },
      "latency_ms": 143.84,
      "status": "error"
    },
    "server_card": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=31536000; includeSubDomains"
        },
        "http_status": 200,
        "payload": {
          "_voidly_pay": {
            "claim_did": "https://voidly.ai/pay/claim",
            "for_builders": "https://voidly.ai/pay/for-builders",
            "install": {
              "cli": "npm install -g @voidly/pay-cli",
              "langchain": "pip install voidly-pay-langchain",
              "mcp": "npx @voidly/pay-mcp",
              "python": "pip install voidly-pay",
              "typescript": "npm install @voidly/pay",
              "vercel_ai": "npm install @voidly/pay-vercel-ai"
            },
            "live_demo": "https://huggingface.co/spaces/emperor-mew/voidly-pay",
            "marketplace": "https://api.voidly.ai/v1/pay/marketplace",
            "note": "Voidly Pay is the open agent-to-agent payment rail. Claim a DID + 10 starter credits in 60s, or paywall any URL via the universal proxy with one query param.",
            "universal_proxy": {
              "example": "https://api.voidly.ai/v1/pay/proxy?u=<https-url>&to=did:voidly:<your-did>&price=0.01",
              "note": "Paywall any public HTTPS URL with one query param. No SDK install required.",
              "page": "https://voidly.ai/pay/proxy",
              "url": "https://api.voidly.ai/v1/pay/proxy"
            }
          },
          "capabilities": {
            "prompts": false,
            "resources": false,
            "tools": true
          },
          "description": "Global censorship intelligence + E2E encrypted agent messaging. Real-time monitoring across 130 countries with 2.2B+ measurements.",
          "documentation": "https://voidly.ai/api-docs",
          "homepage": "https://voidly.ai",
          "name": "voidly",
          "tools": [
            {
              "description": "Get the global censorship index with rankings for all monitored countries. Returns country scores, risk tiers, and measurement counts for 130 countries, aggregating 2.2B+ upstream OONI/IODA/CensoredPlanet measurements (the index is computed on the recent measurement window).",
              "name": "get_censorship_index"
            },
            {
              "description": "Get detailed censorship status for a specific country including blocked domains, anomaly rates, risk tier, and recent incidents.",
              "name": "get_country_status"
            },
            {
              "description": "Check if a specific domain is blocked in a country. Returns blocking status, evidence sources, confidence level, and blocking method (DNS, TCP, TLS, HTTP).",
              "name": "check_domain_blocked"
            },
            {
              "description": "Get citable censorship incidents (multi-source, evidence-backed) ranked best-first \u2014 real censorship events surface ahead of single-source IODA connectivity-outage signals. Each incident is citable with a human-readable ID (e.g., IR-2026-0142). Set citable=false to include raw outage signals.",
              "name": "get_active_incidents"
            },
            {
              "description": "Get detailed information about a specific censorship incident including evidence links, affected domains, blocking methods, and timeline.",
              "name": "get_incident_detail"
            },
            {
              "description": "Verify a censorship claim against real measurement data from OONI, CensoredPlanet, and IODA. Returns verdict with supporting evidence.",
              "name": "verify_claim"
            },
            {
              "description": "Get 7-day internet shutdown and censorship risk forecast for a country using XGBoost ML model trained on historical OONI data and political event calendar.",
              "name": "get_risk_forecast"
            },
            {
              "description": "Get censorship risk score for a specific platform across all monitored countries. Shows which countries block it and the overall global risk level.",
              "name": "get_platform_risk"
            },
            {
              "description": "Real-time check: is a domain/service accessible in a specific country right now? Returns blocking status, block rate across ISPs, and evidence.",
              "name": "check_service_accessibility"
            },
            {
              "description": "Get the most censored countries ranked by censorship severity score. Returns country name, score, risk tier, and top blocked categories.",
              "name": "get_most_censored"
            },
            {
              "description": "Get Voidly Agent Relay network statistics including total registered agents, 24-hour active agents, channel count, message volume, and capability registry.",
              "name": "agent_relay_stats"
            },
            {
              "description": "KeepItOn-validated 7-day shutdown probability for a country (gate-promoted model; live version in the response). Includes honest validation caveats inline.",
              "name": "get_shutdown_risk"
            },
            {
              "description": "All scored countries sorted by current 7-day shutdown probability, with risk bands and as-of dates.",
              "name": "get_shutdown_risk_leaderboard"
            },
            {
              "description": "Running public record of archived shutdown-risk predictions joined to actual KeepItOn outcomes \u2014 the model proves itself in the open.",
              "name": "get_shutdown_risk_accountability"
            },
            {
              "description": "Atlas Score v2 A\u2013F censorship grade(s). Pass country_code for one country; omit for all graded countries.",
              "name": "get_atlas_score"
            },
            {
              "description": "1/7/30-day censorship forecasts for a country with per-horizon SHAP top features and 90% conformal intervals.",
              "name": "get_multi_horizon_forecast"
            },
            {
              "description": "Single-call shutdown-risk heatmap across every watched country, sorted by risk.",
              "name": "get_global_heatmap"
            },
            {
              "description": "Countries whose 7-day forecast exceeds a risk threshold (default 0.5).",
              "name": "get_high_risk_countries"
            },
            {
              "description": "Election-aware censorship risk briefing for a country: upcoming elections joined with forecast and historical election-censorship correlation.",
              "name": "get_election_risk"
            },
            {
              "description": "Upcoming elections worldwide with censorship-risk overlay.",
              "name": "get_upcoming_elections"
            },
            {
              "description": "ISPs in a country ranked by composite censorship score (aggressiveness, category breadth, blocking methods).",
              "name": "get_isp_risk_index"
            },
            {
              "description": "All monitored platforms (WhatsApp, X, Telegram, \u2026) ranked by global censorship risk.",
              "name": "get_platform_scores"
            },
            {
              "description": "Aggregate incident statistics. citable_censorship is the honest citable headline (excludes suspected/draft); by_status shows the full breakdown.",
              "name": "get_incident_stats"
            },
            {
              "description": "Citable report for one incident. format: markdown (default), bibtex, or ris \u2014 ready to paste into an article or reference manager.",
              "name": "get_incident_report"
            },
            {
              "description": "Evidence permalinks backing one incident \u2014 the raw measurements a journalist can verify.",
              "name": "get_incident_evidence"
            },
            {
              "description": "Bulk export of the incident corpus (json, csv, or jsonl). Status column distinguishes corroborated vs suspected rows. Large outputs are truncated \u2014 filter by country or fetch the REST URL for the full file.",
              "name": "export_incidents"
            },
            {
              "description": "Incidents created or updated after an ISO timestamp (delta sync).",
              "name": "get_incidents_since"
            },
            {
              "description": "Country-day censorship classifier score (GradientBoosting v3.3, honest LOCO median F1 0.87).",
              "name": "get_classifier_score"
            },
            {
              "description": "Classifier transparency: version, training data, honest evaluation methodology and caveats.",
              "name": "get_classifier_info"
            },
            {
              "description": "Unsupervised DBSCAN second-opinion anomaly score for a country (CenDTect-style; AUC 0.65 \u2014 weaker than the supervised classifier, surfaces shape-anomalous days labels never saw).",
              "name": "get_anomaly_dbscan"
            },
            {
              "description": "Voidly probe network status: nodes, countries, test cadence, recent measurement volume.",
              "name": "get_probe_stats"
            },
            {
              "description": "Per-source data freshness receipts (OONI, IODA, CensoredPlanet, probes) \u2014 when each pipeline last delivered.",
              "name": "get_data_freshness"
            },
            {
              "description": "Public prediction track record across Voidly forecast products \u2014 hits, misses, and honest baselines.",
              "name": "get_prediction_track_record"
            },
            {
              "description": "Which AI services (ChatGPT, Claude, Gemini, HuggingFace, \u2026) are reachable per country \u2014 state blocking vs vendor geo-restriction, labeled separately.",
              "name": "get_ai_service_availability"
            },
            {
              "description": "Consolidated measured-censorship profile for a country in ONE call: data freshness (last measurement + band), 30-day measurement volume, censorship-technique mix (how they block), and the domains nationally blocked there (confirmed across >=3 networks). Best single call for a country overview.",
              "name": "get_country_profile"
            },
            {
              "description": "How a country censors, not just what \u2014 breakdown of blocking techniques (DNS manipulation, TCP-reset injection, Tor blocking, connection interference, DPI/middlebox, header manipulation). E.g. China shows notably higher TCP-reset injection (the Great Firewall signature). Omit country_code for a global all-country view.",
              "name": "get_censorship_techniques"
            },
            {
              "description": "How the censorship METHOD mix shifts over TIME \u2014 monthly percentage composition of blocking techniques (DNS manipulation, TCP-reset injection, Tor blocking, connection interference, DPI/middlebox). Companion to get_censorship_techniques (a snapshot); this is the trend. Shares are coverage-robust (not raw counts), so they are not skewed by growing measurement volume. Omit country_code for global; months defaults to 12.",
              "name": "get_censorship_technique_trend"
            },
            {
              "description": "How each CONTENT CATEGORY is blocked \u2014 the blocking-technique composition per content type (news, communication tools, anonymity/VPN, search, adult, etc.). Reveals content-targeted blocking: e.g. several censors reserve TCP-reset / connection-level interference for messaging while DNS-poisoning news. Omit country_code for a global view; add it to see one country.",
              "name": "get_censorship_by_category"
            },
            {
              "description": "Global leaderboard of the most-blocked domains, ranked by how many countries nationally block them. HONEST: the top is dominated by legal gambling/piracy/adult blocks, NOT political censorship \u2014 use category=ANON to isolate circumvention tools (ProtonVPN, Psiphon, Lantern), or category=NEWS for news sites.",
              "name": "get_most_blocked_domains"
            },
            {
              "description": "Per-country data-trustworthiness scores (0-100 + band high/medium/low) \u2014 how much to trust Voidly's censorship measurements for each country, derived from freshness, volume, stability, and source diversity. The observatory auditing its own data quality; use it to weight conclusions about sparsely-measured countries.",
              "name": "get_data_confidence"
            },
            {
              "description": "Censorship aggregated by world region (continent by default, or UN sub-region with level=subregion): countries measured, block fraction, and confirmed national blocks per region. HONEST: confirmed-block counts are a measurement-density map, not a censorship ranking (e.g. Africa shows 0 confirmed blocks despite a high block fraction, because the >=3-network confirmation gate needs dense coverage). Use block_fraction + countries_measured for context.",
              "name": "get_censorship_by_region"
            },
            {
              "description": "How recently Voidly measured each country \u2014 last-measurement timestamp + band (live/recent/aging/stale) across ALL monitored countries. Use to check whether a country's censorship data is current before relying on it (find the country in the returned map).",
              "name": "get_measurement_freshness"
            },
            {
              "description": "What each censor TARGETS: per-country category mix of nationally-blocked domains (confirmed across >=3 networks), rolled into three focus shares \u2014 political_speech (NEWS/POLR/HUMR), regulated_morality (GMB/PORN/ALDR), circumvention_tooling (ANON/VOIP) \u2014 plus the full category breakdown + primary_focus. Reveals WHY a country censors (Iran/Russia=speech, Indonesia/Thailand=morality). HONEST: China under-counted (GFW=anomaly not confirmed); shares are over tagged domains only. Pass country=XX for one country.",
              "name": "get_censorship_intent"
            },
            {
              "description": "Which countries most censor a given Citizen Lab content category \u2014 ranked by distinct domains nationally blocked (confirmed across >=3 networks), with example domains. E.g. category=LGBT -> Russia/Iran/Indonesia; also NEWS, HUMR, ANON, POLR, GMB, PORN. HONEST: anomaly-based censors (China GFW) under-counted; counts are a floor.",
              "name": "get_category_leaders"
            },
            {
              "description": "Country PAIRS that nationally block the same domains ('censorship twins') \u2014 shared blocklist size + Jaccard + the meaningful signal shared_political (NEWS/HUMR/POLR) and shared_tooling (ANON/VPN), which strips coincidental gambling/adult overlap. Iran-Russia share 135 domains incl. 23 of the same human-rights orgs + 25 of the same VPN tools (4.6x the next pair on political). HONEST: overlap is correlation, NOT proof of coordination; China under-counted.",
              "name": "get_co_blocking"
            },
            {
              "description": "Per-country measurement DEPTH: how many distinct ISP networks (ASNs) Voidly has evidence from \u2014 a proxy for how many independent vantage points back a country's data, which bounds what the >=3-network confirmed-block gate can confirm. RU 510 / IN 80 / IR 50 networks; ~42 countries carry ASN tags. HONEST: coverage depth, NOT a censorship score; an absent/shallow country is under-measured, not free. Pass country=XX for one country.",
              "name": "get_network_depth"
            },
            {
              "description": "How much of Voidly's measured-domain corpus carries a Citizen Lab content category (~69% via the 14k-domain Citizen Lab list) \u2014 the observatory disclosing its own categorization blind spot. Returns tagged/untagged counts + per-category domain counts. Use to gauge how complete any 'by category' analysis is.",
              "name": "get_category_coverage"
            },
            {
              "description": "One-call snapshot of the state of global censorship Voidly measures \u2014 countries measured, countries with confirmed national blocks, the deepest censor (Iran, ~789 domains), the broadest-blocked category, measurement depth + data coverage, and freshness, plus links to the per-metric endpoints. The ideal first call: 'give me the state of global censorship'. HONEST: most_blocked_category is broad legal gambling-blocking NOT political; China under-counted (GFW=anomaly).",
              "name": "get_censorship_summary"
            },
            {
              "description": "The COMPLETE list of domains a country blocks nationally (confirmed across >=3 independent networks) \u2014 the core 'what does country X block?' product. Returns restriction_map (full domain list), partial_map (sub-national 1-2 network blocks), and confirmed_block_layer (data-recency window). Use this for a full report; for a single domain use check_domain_blocked, for a summary use get_country_profile. HONEST: includes legal gambling/piracy blocks (not only political); a domain NOT listed is accessible OR not measured (absence is not 'accessible'); China under-counted (GFW=anomaly).",
              "name": "get_national_blocklist"
            },
            {
              "description": "Full-corpus block TIMELINE for one domain: when it was FIRST observed blocked in each country and how the blocking METHOD evolved over time, sorted earliest-first (censorship-spread order). The long-horizon companion to check_domain_blocked / get_domain_history (which show current/recent status). Use for 'when did country X start blocking Y?' and 'how did they block it (DNS vs TCP-reset vs blockpage)?'. Pass domain=twitter.com (optional country=IR to focus one country). HONEST: the evidence corpus begins 2026-02, so blocks predating it are not captured (first dates can cluster at corpus-start); a country absent from the list is accessible OR unmeasured.",
              "name": "get_domain_timeline"
            },
            {
              "description": "How accurate is Voidly's v3.3 censorship classifier? The honest answer under THREE evaluation regimes of increasing difficulty, in one call: stratified-random (in-distribution upper bound, AUC ~0.90 / F1 ~0.73), leave-country-out (cross-country generalization, F1 mean ~0.71 / median ~0.87 over 127 countries), and forward-temporal (train past / predict future, AUC ~0.67 / F1 ~0.47) \u2014 plus the generalization gap (delta AUC -0.23, 'DEGRADES forward') and which metric to cite for which use. Reads the live training sidecars. Use when asked 'how accurate is the model?' \u2014 never quote one number alone. HONEST: the retired v2 '0.998 F1' had country-tier leakage and is not a live claim.",
              "name": "get_classifier_scope"
            },
            {
              "description": "Per-ISP selective targeting: which CONTENT CATEGORIES a network (ASN) blocks vs leaves alone, separating targeted political censorship from blanket filtering. Pass country=XX&asn=NNNN for one network's per-category block rates + a blanket/selective/permissive/mixed label (e.g. KZ AS207446 blocks 94% of VPN/circumvention tools but 0% of news \u2014 a 'VPN-blocker'; RU AS47541 is the opposite, blocking news not VPNs); pass country=XX for the country's networks ranked. HONEST: block_rate is over MEASURED domains per category (a category absent is UNMEASURED, not 'allowed'); ASN coverage is dominated by CensoredPlanet DNS and is sparse for many networks, so most read 'blanket'.",
              "name": "get_isp_categories"
            },
            {
              "description": "Head-to-head censorship comparison of two countries: each one's nationally-blocked domain count + Citizen Lab category profile, the SHARED blocklist (domains both confirm-block nationally, incl. shared political news/human-rights and shared circumvention tooling), and a per-category side-by-side showing who blocks more in each category. Built on the confirmed-national layer (>=3 independent networks) \u2014 counts agree with get_national_blocklist + get_co_blocking (e.g. IR vs RU: IR 789 blocked, 135 shared, RU blocks more NEWS while IR blocks more human-rights/VPN). Use for 'how does country X's censorship differ from Y's?'. HONEST: counts are a floor over the confirmed layer, not a census; deliberately no 'uniquely blocked' lists (absence in one country's layer is unconfirmed, not accessible); China under-counted (GFW=anomaly).",
              "name": "get_country_compare"
            },
            {
              "description": "Citizen Lab content-category legend: maps every category code used across the censorship data (NEWS, POLR, HUMR, ANON, GMB, LGBT, REL, ...) to its human name plus how many domains carry it in the corpus, how many are confirmed blocked nationally somewhere, and how many countries block that category. The reference for interpreting any category code returned by get_category_leaders, get_censorship_intent, or the national blocklist. HONEST: national counts are over the >=3-network confirmed layer (a floor); China under-counted (GFW=anomaly).",
              "name": "get_categories"
            }
          ],
          "tools_count": 54,
          "transport": {
            "type": "streamable-http",
            "url": "https://api.voidly.ai/mcp"
          },
          "version": "2.10.0"
        },
        "url": "https://voidly.ai/.well-known/mcp/server-card.json"
      },
      "latency_ms": 879.65,
      "status": "ok"
    },
    "session_resume_probe": {
      "details": {
        "protocol_version": null,
        "reason": "no_session_id",
        "resume_expected": false,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": false,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tool_snapshot_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tools_list": {
      "details": {
        "error": "Client error '405 Method Not Allowed' for url 'https://voidly.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405",
        "headers": {
          "allow": "GET,HEAD",
          "content-type": "text/html; charset=utf-8",
          "strict-transport-security": "max-age=63072000; includeSubDomains"
        },
        "http_status": 405,
        "payload": {},
        "url": "https://voidly.ai/mcp"
      },
      "latency_ms": 146.69,
      "status": "error"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "allow": "GET,HEAD",
          "content-type": "text/html; charset=utf-8",
          "strict-transport-security": "max-age=63072000; includeSubDomains"
        },
        "bad_protocol_payload": {},
        "bad_protocol_status_code": 405,
        "delete_error": null,
        "delete_status_code": null,
        "expired_session_error": null,
        "expired_session_status_code": null,
        "issues": [
          "missing_protocol_header",
          "bad_protocol_not_rejected"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2025-03-26",
        "session_id_present": false,
        "transport": "streamable-http"
      },
      "latency_ms": 115.84,
      "status": "error"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": true,
          "live_probe": "not_executed",
          "sample_target": null
        },
        "initialize_capability_keys": [],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 405,
          "probe_status": "missing"
        }
      },
      "latency_ms": 41.31,
      "status": "warning"
    }
  },
  "failures": {
    "initialize": {
      "error": "Client error '405 Method Not Allowed' for url 'https://voidly.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405",
      "headers": {
        "allow": "GET,HEAD",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains"
      },
      "http_status": 405,
      "payload": {},
      "url": "https://voidly.ai/mcp"
    },
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '404 Not Found' for url 'https://voidly.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://voidly.ai/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "prompts_list": {
      "error": "Client error '405 Method Not Allowed' for url 'https://voidly.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405",
      "headers": {
        "allow": "GET,HEAD",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains"
      },
      "http_status": 405,
      "payload": {},
      "url": "https://voidly.ai/mcp"
    },
    "resources_list": {
      "error": "Client error '405 Method Not Allowed' for url 'https://voidly.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405",
      "headers": {
        "allow": "GET,HEAD",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains"
      },
      "http_status": 405,
      "payload": {},
      "url": "https://voidly.ai/mcp"
    },
    "tools_list": {
      "error": "Client error '405 Method Not Allowed' for url 'https://voidly.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405",
      "headers": {
        "allow": "GET,HEAD",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains"
      },
      "http_status": 405,
      "payload": {},
      "url": "https://voidly.ai/mcp"
    },
    "transport_compliance_probe": {
      "bad_protocol_error": null,
      "bad_protocol_headers": {
        "allow": "GET,HEAD",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains"
      },
      "bad_protocol_payload": {},
      "bad_protocol_status_code": 405,
      "delete_error": null,
      "delete_status_code": null,
      "expired_session_error": null,
      "expired_session_status_code": null,
      "issues": [
        "missing_protocol_header",
        "bad_protocol_not_rejected"
      ],
      "last_event_id_visible": false,
      "protocol_header_present": false,
      "requested_protocol_version": "2025-03-26",
      "session_id_present": false,
      "transport": "streamable-http"
    }
  },
  "remote_url": "https://voidly.ai/mcp",
  "server_card_payload": {
    "_voidly_pay": {
      "claim_did": "https://voidly.ai/pay/claim",
      "for_builders": "https://voidly.ai/pay/for-builders",
      "install": {
        "cli": "npm install -g @voidly/pay-cli",
        "langchain": "pip install voidly-pay-langchain",
        "mcp": "npx @voidly/pay-mcp",
        "python": "pip install voidly-pay",
        "typescript": "npm install @voidly/pay",
        "vercel_ai": "npm install @voidly/pay-vercel-ai"
      },
      "live_demo": "https://huggingface.co/spaces/emperor-mew/voidly-pay",
      "marketplace": "https://api.voidly.ai/v1/pay/marketplace",
      "note": "Voidly Pay is the open agent-to-agent payment rail. Claim a DID + 10 starter credits in 60s, or paywall any URL via the universal proxy with one query param.",
      "universal_proxy": {
        "example": "https://api.voidly.ai/v1/pay/proxy?u=<https-url>&to=did:voidly:<your-did>&price=0.01",
        "note": "Paywall any public HTTPS URL with one query param. No SDK install required.",
        "page": "https://voidly.ai/pay/proxy",
        "url": "https://api.voidly.ai/v1/pay/proxy"
      }
    },
    "capabilities": {
      "prompts": false,
      "resources": false,
      "tools": true
    },
    "description": "Global censorship intelligence + E2E encrypted agent messaging. Real-time monitoring across 130 countries with 2.2B+ measurements.",
    "documentation": "https://voidly.ai/api-docs",
    "homepage": "https://voidly.ai",
    "name": "voidly",
    "tools": [
      {
        "description": "Get the global censorship index with rankings for all monitored countries. Returns country scores, risk tiers, and measurement counts for 130 countries, aggregating 2.2B+ upstream OONI/IODA/CensoredPlanet measurements (the index is computed on the recent measurement window).",
        "name": "get_censorship_index"
      },
      {
        "description": "Get detailed censorship status for a specific country including blocked domains, anomaly rates, risk tier, and recent incidents.",
        "name": "get_country_status"
      },
      {
        "description": "Check if a specific domain is blocked in a country. Returns blocking status, evidence sources, confidence level, and blocking method (DNS, TCP, TLS, HTTP).",
        "name": "check_domain_blocked"
      },
      {
        "description": "Get citable censorship incidents (multi-source, evidence-backed) ranked best-first \u2014 real censorship events surface ahead of single-source IODA connectivity-outage signals. Each incident is citable with a human-readable ID (e.g., IR-2026-0142). Set citable=false to include raw outage signals.",
        "name": "get_active_incidents"
      },
      {
        "description": "Get detailed information about a specific censorship incident including evidence links, affected domains, blocking methods, and timeline.",
        "name": "get_incident_detail"
      },
      {
        "description": "Verify a censorship claim against real measurement data from OONI, CensoredPlanet, and IODA. Returns verdict with supporting evidence.",
        "name": "verify_claim"
      },
      {
        "description": "Get 7-day internet shutdown and censorship risk forecast for a country using XGBoost ML model trained on historical OONI data and political event calendar.",
        "name": "get_risk_forecast"
      },
      {
        "description": "Get censorship risk score for a specific platform across all monitored countries. Shows which countries block it and the overall global risk level.",
        "name": "get_platform_risk"
      },
      {
        "description": "Real-time check: is a domain/service accessible in a specific country right now? Returns blocking status, block rate across ISPs, and evidence.",
        "name": "check_service_accessibility"
      },
      {
        "description": "Get the most censored countries ranked by censorship severity score. Returns country name, score, risk tier, and top blocked categories.",
        "name": "get_most_censored"
      },
      {
        "description": "Get Voidly Agent Relay network statistics including total registered agents, 24-hour active agents, channel count, message volume, and capability registry.",
        "name": "agent_relay_stats"
      },
      {
        "description": "KeepItOn-validated 7-day shutdown probability for a country (gate-promoted model; live version in the response). Includes honest validation caveats inline.",
        "name": "get_shutdown_risk"
      },
      {
        "description": "All scored countries sorted by current 7-day shutdown probability, with risk bands and as-of dates.",
        "name": "get_shutdown_risk_leaderboard"
      },
      {
        "description": "Running public record of archived shutdown-risk predictions joined to actual KeepItOn outcomes \u2014 the model proves itself in the open.",
        "name": "get_shutdown_risk_accountability"
      },
      {
        "description": "Atlas Score v2 A\u2013F censorship grade(s). Pass country_code for one country; omit for all graded countries.",
        "name": "get_atlas_score"
      },
      {
        "description": "1/7/30-day censorship forecasts for a country with per-horizon SHAP top features and 90% conformal intervals.",
        "name": "get_multi_horizon_forecast"
      },
      {
        "description": "Single-call shutdown-risk heatmap across every watched country, sorted by risk.",
        "name": "get_global_heatmap"
      },
      {
        "description": "Countries whose 7-day forecast exceeds a risk threshold (default 0.5).",
        "name": "get_high_risk_countries"
      },
      {
        "description": "Election-aware censorship risk briefing for a country: upcoming elections joined with forecast and historical election-censorship correlation.",
        "name": "get_election_risk"
      },
      {
        "description": "Upcoming elections worldwide with censorship-risk overlay.",
        "name": "get_upcoming_elections"
      },
      {
        "description": "ISPs in a country ranked by composite censorship score (aggressiveness, category breadth, blocking methods).",
        "name": "get_isp_risk_index"
      },
      {
        "description": "All monitored platforms (WhatsApp, X, Telegram, \u2026) ranked by global censorship risk.",
        "name": "get_platform_scores"
      },
      {
        "description": "Aggregate incident statistics. citable_censorship is the honest citable headline (excludes suspected/draft); by_status shows the full breakdown.",
        "name": "get_incident_stats"
      },
      {
        "description": "Citable report for one incident. format: markdown (default), bibtex, or ris \u2014 ready to paste into an article or reference manager.",
        "name": "get_incident_report"
      },
      {
        "description": "Evidence permalinks backing one incident \u2014 the raw measurements a journalist can verify.",
        "name": "get_incident_evidence"
      },
      {
        "description": "Bulk export of the incident corpus (json, csv, or jsonl). Status column distinguishes corroborated vs suspected rows. Large outputs are truncated \u2014 filter by country or fetch the REST URL for the full file.",
        "name": "export_incidents"
      },
      {
        "description": "Incidents created or updated after an ISO timestamp (delta sync).",
        "name": "get_incidents_since"
      },
      {
        "description": "Country-day censorship classifier score (GradientBoosting v3.3, honest LOCO median F1 0.87).",
        "name": "get_classifier_score"
      },
      {
        "description": "Classifier transparency: version, training data, honest evaluation methodology and caveats.",
        "name": "get_classifier_info"
      },
      {
        "description": "Unsupervised DBSCAN second-opinion anomaly score for a country (CenDTect-style; AUC 0.65 \u2014 weaker than the supervised classifier, surfaces shape-anomalous days labels never saw).",
        "name": "get_anomaly_dbscan"
      },
      {
        "description": "Voidly probe network status: nodes, countries, test cadence, recent measurement volume.",
        "name": "get_probe_stats"
      },
      {
        "description": "Per-source data freshness receipts (OONI, IODA, CensoredPlanet, probes) \u2014 when each pipeline last delivered.",
        "name": "get_data_freshness"
      },
      {
        "description": "Public prediction track record across Voidly forecast products \u2014 hits, misses, and honest baselines.",
        "name": "get_prediction_track_record"
      },
      {
        "description": "Which AI services (ChatGPT, Claude, Gemini, HuggingFace, \u2026) are reachable per country \u2014 state blocking vs vendor geo-restriction, labeled separately.",
        "name": "get_ai_service_availability"
      },
      {
        "description": "Consolidated measured-censorship profile for a country in ONE call: data freshness (last measurement + band), 30-day measurement volume, censorship-technique mix (how they block), and the domains nationally blocked there (confirmed across >=3 networks). Best single call for a country overview.",
        "name": "get_country_profile"
      },
      {
        "description": "How a country censors, not just what \u2014 breakdown of blocking techniques (DNS manipulation, TCP-reset injection, Tor blocking, connection interference, DPI/middlebox, header manipulation). E.g. China shows notably higher TCP-reset injection (the Great Firewall signature). Omit country_code for a global all-country view.",
        "name": "get_censorship_techniques"
      },
      {
        "description": "How the censorship METHOD mix shifts over TIME \u2014 monthly percentage composition of blocking techniques (DNS manipulation, TCP-reset injection, Tor blocking, connection interference, DPI/middlebox). Companion to get_censorship_techniques (a snapshot); this is the trend. Shares are coverage-robust (not raw counts), so they are not skewed by growing measurement volume. Omit country_code for global; months defaults to 12.",
        "name": "get_censorship_technique_trend"
      },
      {
        "description": "How each CONTENT CATEGORY is blocked \u2014 the blocking-technique composition per content type (news, communication tools, anonymity/VPN, search, adult, etc.). Reveals content-targeted blocking: e.g. several censors reserve TCP-reset / connection-level interference for messaging while DNS-poisoning news. Omit country_code for a global view; add it to see one country.",
        "name": "get_censorship_by_category"
      },
      {
        "description": "Global leaderboard of the most-blocked domains, ranked by how many countries nationally block them. HONEST: the top is dominated by legal gambling/piracy/adult blocks, NOT political censorship \u2014 use category=ANON to isolate circumvention tools (ProtonVPN, Psiphon, Lantern), or category=NEWS for news sites.",
        "name": "get_most_blocked_domains"
      },
      {
        "description": "Per-country data-trustworthiness scores (0-100 + band high/medium/low) \u2014 how much to trust Voidly's censorship measurements for each country, derived from freshness, volume, stability, and source diversity. The observatory auditing its own data quality; use it to weight conclusions about sparsely-measured countries.",
        "name": "get_data_confidence"
      },
      {
        "description": "Censorship aggregated by world region (continent by default, or UN sub-region with level=subregion): countries measured, block fraction, and confirmed national blocks per region. HONEST: confirmed-block counts are a measurement-density map, not a censorship ranking (e.g. Africa shows 0 confirmed blocks despite a high block fraction, because the >=3-network confirmation gate needs dense coverage). Use block_fraction + countries_measured for context.",
        "name": "get_censorship_by_region"
      },
      {
        "description": "How recently Voidly measured each country \u2014 last-measurement timestamp + band (live/recent/aging/stale) across ALL monitored countries. Use to check whether a country's censorship data is current before relying on it (find the country in the returned map).",
        "name": "get_measurement_freshness"
      },
      {
        "description": "What each censor TARGETS: per-country category mix of nationally-blocked domains (confirmed across >=3 networks), rolled into three focus shares \u2014 political_speech (NEWS/POLR/HUMR), regulated_morality (GMB/PORN/ALDR), circumvention_tooling (ANON/VOIP) \u2014 plus the full category breakdown + primary_focus. Reveals WHY a country censors (Iran/Russia=speech, Indonesia/Thailand=morality). HONEST: China under-counted (GFW=anomaly not confirmed); shares are over tagged domains only. Pass country=XX for one country.",
        "name": "get_censorship_intent"
      },
      {
        "description": "Which countries most censor a given Citizen Lab content category \u2014 ranked by distinct domains nationally blocked (confirmed across >=3 networks), with example domains. E.g. category=LGBT -> Russia/Iran/Indonesia; also NEWS, HUMR, ANON, POLR, GMB, PORN. HONEST: anomaly-based censors (China GFW) under-counted; counts are a floor.",
        "name": "get_category_leaders"
      },
      {
        "description": "Country PAIRS that nationally block the same domains ('censorship twins') \u2014 shared blocklist size + Jaccard + the meaningful signal shared_political (NEWS/HUMR/POLR) and shared_tooling (ANON/VPN), which strips coincidental gambling/adult overlap. Iran-Russia share 135 domains incl. 23 of the same human-rights orgs + 25 of the same VPN tools (4.6x the next pair on political). HONEST: overlap is correlation, NOT proof of coordination; China under-counted.",
        "name": "get_co_blocking"
      },
      {
        "description": "Per-country measurement DEPTH: how many distinct ISP networks (ASNs) Voidly has evidence from \u2014 a proxy for how many independent vantage points back a country's data, which bounds what the >=3-network confirmed-block gate can confirm. RU 510 / IN 80 / IR 50 networks; ~42 countries carry ASN tags. HONEST: coverage depth, NOT a censorship score; an absent/shallow country is under-measured, not free. Pass country=XX for one country.",
        "name": "get_network_depth"
      },
      {
        "description": "How much of Voidly's measured-domain corpus carries a Citizen Lab content category (~69% via the 14k-domain Citizen Lab list) \u2014 the observatory disclosing its own categorization blind spot. Returns tagged/untagged counts + per-category domain counts. Use to gauge how complete any 'by category' analysis is.",
        "name": "get_category_coverage"
      },
      {
        "description": "One-call snapshot of the state of global censorship Voidly measures \u2014 countries measured, countries with confirmed national blocks, the deepest censor (Iran, ~789 domains), the broadest-blocked category, measurement depth + data coverage, and freshness, plus links to the per-metric endpoints. The ideal first call: 'give me the state of global censorship'. HONEST: most_blocked_category is broad legal gambling-blocking NOT political; China under-counted (GFW=anomaly).",
        "name": "get_censorship_summary"
      },
      {
        "description": "The COMPLETE list of domains a country blocks nationally (confirmed across >=3 independent networks) \u2014 the core 'what does country X block?' product. Returns restriction_map (full domain list), partial_map (sub-national 1-2 network blocks), and confirmed_block_layer (data-recency window). Use this for a full report; for a single domain use check_domain_blocked, for a summary use get_country_profile. HONEST: includes legal gambling/piracy blocks (not only political); a domain NOT listed is accessible OR not measured (absence is not 'accessible'); China under-counted (GFW=anomaly).",
        "name": "get_national_blocklist"
      },
      {
        "description": "Full-corpus block TIMELINE for one domain: when it was FIRST observed blocked in each country and how the blocking METHOD evolved over time, sorted earliest-first (censorship-spread order). The long-horizon companion to check_domain_blocked / get_domain_history (which show current/recent status). Use for 'when did country X start blocking Y?' and 'how did they block it (DNS vs TCP-reset vs blockpage)?'. Pass domain=twitter.com (optional country=IR to focus one country). HONEST: the evidence corpus begins 2026-02, so blocks predating it are not captured (first dates can cluster at corpus-start); a country absent from the list is accessible OR unmeasured.",
        "name": "get_domain_timeline"
      },
      {
        "description": "How accurate is Voidly's v3.3 censorship classifier? The honest answer under THREE evaluation regimes of increasing difficulty, in one call: stratified-random (in-distribution upper bound, AUC ~0.90 / F1 ~0.73), leave-country-out (cross-country generalization, F1 mean ~0.71 / median ~0.87 over 127 countries), and forward-temporal (train past / predict future, AUC ~0.67 / F1 ~0.47) \u2014 plus the generalization gap (delta AUC -0.23, 'DEGRADES forward') and which metric to cite for which use. Reads the live training sidecars. Use when asked 'how accurate is the model?' \u2014 never quote one number alone. HONEST: the retired v2 '0.998 F1' had country-tier leakage and is not a live claim.",
        "name": "get_classifier_scope"
      },
      {
        "description": "Per-ISP selective targeting: which CONTENT CATEGORIES a network (ASN) blocks vs leaves alone, separating targeted political censorship from blanket filtering. Pass country=XX&asn=NNNN for one network's per-category block rates + a blanket/selective/permissive/mixed label (e.g. KZ AS207446 blocks 94% of VPN/circumvention tools but 0% of news \u2014 a 'VPN-blocker'; RU AS47541 is the opposite, blocking news not VPNs); pass country=XX for the country's networks ranked. HONEST: block_rate is over MEASURED domains per category (a category absent is UNMEASURED, not 'allowed'); ASN coverage is dominated by CensoredPlanet DNS and is sparse for many networks, so most read 'blanket'.",
        "name": "get_isp_categories"
      },
      {
        "description": "Head-to-head censorship comparison of two countries: each one's nationally-blocked domain count + Citizen Lab category profile, the SHARED blocklist (domains both confirm-block nationally, incl. shared political news/human-rights and shared circumvention tooling), and a per-category side-by-side showing who blocks more in each category. Built on the confirmed-national layer (>=3 independent networks) \u2014 counts agree with get_national_blocklist + get_co_blocking (e.g. IR vs RU: IR 789 blocked, 135 shared, RU blocks more NEWS while IR blocks more human-rights/VPN). Use for 'how does country X's censorship differ from Y's?'. HONEST: counts are a floor over the confirmed layer, not a census; deliberately no 'uniquely blocked' lists (absence in one country's layer is unconfirmed, not accessible); China under-counted (GFW=anomaly).",
        "name": "get_country_compare"
      },
      {
        "description": "Citizen Lab content-category legend: maps every category code used across the censorship data (NEWS, POLR, HUMR, ANON, GMB, LGBT, REL, ...) to its human name plus how many domains carry it in the corpus, how many are confirmed blocked nationally somewhere, and how many countries block that category. The reference for interpreting any category code returned by get_category_leaders, get_censorship_intent, or the national blocklist. HONEST: national counts are over the >=3-network confirmed layer (a floor); China under-counted (GFW=anomaly).",
        "name": "get_categories"
      }
    ],
    "tools_count": 54,
    "transport": {
      "type": "streamable-http",
      "url": "https://api.voidly.ai/mcp"
    },
    "version": "2.10.0"
  },
  "server_identifier": "npm-voidly/mcp-server"
}

Known versions

Validation history

Trend history appears after at least two validation runs. This avoids presenting a one-point validation as a trend.

Validation timeline

ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
Aug 04, 2026 10:31:33 AM UTC Failing 47.4 unknown unknown 0 0 none

Recent validation runs

Recent validation runs for this MCP server
StartedStatusSummaryLatencyChecks
Aug 04, 2026 10:31:31 AM UTC Completed Failing 2341.9 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe