nexus0-agent-rail
REMOTE · NEXUS-ZERO.XYZ
Pay-per-call DNS/TLS truth and npm/PyPI breakage checks via x402. No account or API key.
Available components
Last scanned (2 months ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 27 Jul 2026.
Category Testing and QA
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security14
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Aug 2026 · Probed https://nexus-zero.xyz/agent/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of nexus-zero.xyz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| nexus-zero.xyz. | present | 59110 | 13 | Verified |
| nexus-zero.xyz. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nexus-zero.xyz/agent/mcp | Unreachable | ||
| http (plaintext) | http://nexus-zero.xyz/agent/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agent_catalog ~24
List the payable cells/tools, their prices, input schemas and endpoints. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
blacksignal_check_upgrade_safety ~101
[$0.05 USDC/Solana per call] Is this specific upgrade safe? Analyzes a package's from_version → to_version for breaking changes, with registry evidence. Cheaper than run_canary because the range is explicit.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | pypi | npm |
| from_version | string | yes | Current version |
| package | string | yes | Package name |
| to_version | string | yes | Target version |
No output schema declared.
No examples provided.
blacksignal_get_breakage_feed ~101
[$0.01 USDC/Solana per call] Evidence-backed public npm/PyPI breakage feed from BlackSignal platform monitors. Returns only platform-public incidents; private tenant monitor findings are never exposed.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Optional registry filter |
| limit | integer | – | – |
| package | string | – | Optional exact package name |
| severity | string | – | Optional severity filter |
| status | string | – | Optional lifecycle filter |
No output schema declared.
No examples provided.
blacksignal_run_canary ~107
[$0.10 USDC/Solana per call] BlackSignal release-breakage canary for an npm/PyPI package: analyzes the latest release (or an explicit range) for yanks, deprecations, major version bumps, tightened runtime requirements and dependency churn — with registry evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | pypi | npm |
| from_version | string | – | – |
| package | string | yes | Package name |
| to_version | string | – | – |
No output schema declared.
No examples provided.
dns_truth_analyze_domain ~78
[$0.05 USDC/Solana per call] Passive DNS/domain truth report: nameservers, A/AAAA, MX, SPF, DMARC, DNSSEC plus certificate and deliverability signals. SSRF-safe, anonymous — no domain authorization required.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to analyze (public/passive checks only) |
No output schema declared.
No examples provided.
get_job_status ~37
Check the status/result of a paid job by its job_id (the settlement tx signature). Free.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the nexus0-agent-rail MCP server?
nexus0-agent-rail is a hosted endpoint at https://nexus-zero.xyz/agent/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · nexus-zero.xyz
claude mcp add --transport http mikehunt69702-agent-gateway 'https://nexus-zero.xyz/agent/mcp'
What is the nexus0-agent-rail MCP server?
nexus0-agent-rail is an MCP server listed in the public MCP registry as io.github.MikeHunt69702/agent-gateway. Pay-per-call DNS/TLS truth and npm/PyPI breakage checks via x402. No account or API key. This page covers its hosted endpoint (https://nexus-zero.xyz/agent/mcp).
Is the nexus0-agent-rail MCP server safe to use?
nexus0-agent-rail scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the nexus0-agent-rail MCP server expose?
nexus0-agent-rail exposes 6 tools: dns_truth_analyze_domain, blacksignal_run_canary, blacksignal_check_upgrade_safety, blacksignal_get_breakage_feed, get_job_status, agent_catalog. Their descriptions and schemas cost roughly 448 tokens of context every time the server is loaded.
Does the nexus0-agent-rail MCP server require authentication?
Its publisher declares no required credentials for nexus0-agent-rail. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the nexus0-agent-rail MCP server still maintained?
nexus0-agent-rail has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 27 July 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.