
nexus0-agent-rail
io.github.MikeHunt69702Published by GitHub account MikeHunt69702v0.2.0Updated Oct 24, 2026
Pay-per-call DNS/TLS truth and npm/PyPI breakage checks via x402. No account or API key.
Overview
A remote pay-per-call server that checks DNS and TLS records and detects npm/PyPI package breakage, with no account or API key needed.
- What you can do
- Check DNS and TLS records for a domain to confirm what is actually published and trusted. Check npm and PyPI packages for breakage. Each call is billed individually through the x402 payment scheme rather than an account or API key.
- When to use it
- Useful when an assistant needs to verify DNS or TLS facts for a domain, or confirm whether a published npm or PyPI package is broken, without setting up an account.
- Requirements
- A remote streamable HTTP endpoint; no account, API key, environment variable or header is declared. Calls are paid per use through x402, so a payment-capable client or wallet arrangement is implied.
Installation
In SourceWeft
- Open nexus0-agent-rail 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.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.MikeHunt69702%2Fagent-gateway/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"nexus0-agent-rail": {
"type": "http",
"url": "https://nexus-zero.xyz/agent/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v0.2.0LatestSep 16, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.