
Voidly Hosted MCP
io.github.voidly-aiv2.25.0Updated Oct 7, 2026
Voidly MCP: research, Atlas score, capabilities; gated Voidpay, Voidmail, Home, board and bounty.
Overview
A hosted remote MCP endpoint from Voidly offering research, an Atlas score, capability listings, and gated Voidpay, Voidmail, Home, board and bounty features.
- What it does
- Voidly Hosted MCP is a remote streamable-HTTP endpoint at api.voidly.ai that exposes Voidly's unified toolset to an assistant. The registry description names research, an Atlas score, and capability discovery, plus gated features for Voidpay, Voidmail, Home, a board and bounties. The public repository only holds the Registry descriptor and publication workflow; the hosted backend is operated separately and is not in the repository. No individual tools are listed in the manifest.
- When to use it
- Consider it when you want an assistant to reach Voidly's hosted research, scoring and capability tools, or the gated Voidpay, Voidmail, Home, board and bounty features, without running a local package. It is a hosted service, so it suits users already working within the Voidly ecosystem.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the hosted endpoint. The manifest declares no authentication, environment variables or headers, but the description marks several features as gated, so access to those may require separate authorization from the provider.
Installation
In SourceWeft
- Open Voidly Hosted MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"voidly-hosted": {
"type": "http",
"url": "https://api.voidly.ai/mcp"
}
}
}README
Voidly hosted MCP Registry entry
This folder holds the public Registry descriptor for Voidly's unified hosted MCP endpoint at https://api.voidly.ai/mcp. The root server.json describes the separate @voidly/pay-mcp npm/stdio connector.
The descriptor links to this public repository and its registry/hosted subfolder, which holds the Registry metadata. The publication workflow is in .github/workflows. The hosted service is operated separately; its backend implementation is not in this repository.
Publication is manual from reviewed main. The workflow checks the served MCP version and tool catalog before OIDC authentication, then makes one publish attempt and verifies the exact public Registry record. The mcp-registry-publish GitHub environment needs required reviewers, a main-only branch rule, and its environment-scoped guard variable before dispatch.
Source: registry/hosted/README.md at commit b345409
Tools
0Version history
1- v2.25.0LatestOct 7, 2026

