NEUS MCP
REMOTE · MCP.NEUS.NETWORK
The trust harness for AI agents. Set what an agent can do before it acts.
Available components
Last scanned (4 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 935 tokens (~233/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 −5
- Stability: pass → 0.60 functional
- 2 Nov 26 0
- Server version: 0.1.7 → 0.1.8 functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 +9
- Stability: fail → 0.97 functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 31.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 21 to 24.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 14 to 17.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 11.
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 5 Nov 2026 · Probed https://mcp.neus.network/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=neus.network | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7e4b6c14632aa61b139d32a683f3dce8 |
| SANs: neus.network, *.neus.network | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.neus.network. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| network. | present | 11416, 40414 | 8, 8 | Verified |
| neus.network. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource", scope="proofable:core proofable:profile proofable:secrets"
Bearer resource_metadata="https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource", scope="proofable:core proofable:profile proofable:secrets"Protected resource metadata
| Document | https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Problem | metadata_resource_mismatch |
| Resource | https://mcp.proofable.me/mcp |
| Authorisation server | https://proofable.me |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.neus.network/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.neus.network/mcp | HTTPS enforced | 301 | https://mcp.neus.network/mcp |
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 →
proofable_context Session context ~40
Return the signed-in Proofable profile and its current read-only context: proof index, agents, permissions, and verifier summary. Use once after sign-in.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| agentsError | string | – | – |
| agentsStatus | string | – | – |
| authenticated | boolean | – | – |
| contextIndex | – | – | – |
| error | string | – | – |
| message | string | – | – |
| profile | object | – | – |
| recommendedWorkflow | – | – | – |
| status | string|number | – | – |
| verifierSummary | array | – | – |
No examples provided.
proofable_proofs_check Check proofs ~199
Does this wallet already have the required proofs? Returns pass or fail, not records. Reading proof bodies needs a signed-in session, which is what unlocks proofable_proofs_get; signed-out callers get this check and can sign in to go further. Omit the wallet when signed in.
| Name | Type | Req | Description |
|---|---|---|---|
| gateId | string | – | Optional hosted gate or listing id. Signed-in owners still get eligible + matchedCount only. |
| handle | string | – | Optional handle filter for handle-based verifiers. |
| minCount | number | – | Minimum number of matching proofs. Default 1. |
| namespace | string | – | Optional namespace filter for handle checks. |
| requireAll | boolean | – | Require all listed verifiers. Default false accepts any one. |
| verifiers | array | yes | Verifier IDs from proofable_verifiers_catalog. |
| wallet | string | – | Wallet or DID to verify. Omit when signed in to use the current account. |
| Name | Type | Req | Description |
|---|---|---|---|
| eligible | boolean | – | – |
| error | string | – | – |
| matchedCount | number | – | – |
| message | string | – | – |
| satisfied | boolean | – | – |
| status | string|number | – | – |
| success | boolean | – | – |
| unknownVerifiers | array | – | – |
No examples provided.
proofable_verifiers_catalog Verifier catalog ~23
Return supported check definitions with the inputs and networks each requires.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| message | string | – | – |
| meta | – | – | – |
| metadata | object | – | – |
| status | string|number | – | – |
| verifiers | array | yes | – |
No examples provided.
proofable_verify_or_guide Verify or get next step ~159
Resolve a verification request for the selected Proofable checks. Returns current qualifying proofs when they exist; otherwise returns the single next step. This tool does not create a proof.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Optional network hint. Omit when Proofable can infer it from the wallet format. |
| data | object | – | Inputs for the selected verifiers. Used only when a new Proof is needed. |
| options | object | – | Optional verification options |
| requireAll | boolean | – | Require all listed verifiers. Default false accepts any one. |
| verifierIds | array | yes | Verifier IDs from proofable_verifiers_catalog. |
| walletAddress | string | – | Wallet or DID. Omit when signed in to use the current account. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| eligible | boolean | – | – |
| error | string | – | – |
| hostedVerifyUrl | string | – | – |
| matchedCount | number | – | – |
| message | string | – | – |
| proofs | array | – | – |
| status | string|number | – | – |
| success | boolean | – | – |
No examples provided.
How do I install the NEUS MCP server?
NEUS MCP is a hosted endpoint at https://mcp.neus.network/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 · mcp.neus.network
claude mcp add --transport http neus-neus-mcp 'https://mcp.neus.network/mcp'
What is the NEUS MCP server?
NEUS MCP is listed in the public MCP registry as io.github.neus/neus-mcp. The trust harness for AI agents. Set what an agent can do before it acts. This page covers its hosted endpoint (https://mcp.neus.network/mcp).
Is the NEUS MCP server safe to use?
NEUS MCP scores 81 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 NEUS MCP server expose?
NEUS MCP exposes 4 tools: proofable_context, proofable_verifiers_catalog, proofable_proofs_check, proofable_verify_or_guide. Their descriptions and schemas cost roughly 421 tokens of context every time the server is loaded.
Does the NEUS MCP server require authentication?
Yes. NEUS MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the NEUS MCP server still maintained?
NEUS MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.