Ariadne Nexus Provenance & Underwriting MCP
REMOTE · MCP.ARIADNENEXUS.COM
Deterministic SHA-256 collateral checks, optical forensics, and ZK provenance proofs.
Available components
Last scanned (19 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
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 Security89
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2421 tokens (~345/item across 7 items; 7 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 Management10
- Stability observed for 3 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Server version: 0.1.6 → 0.1.8 functional
- 20 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 2046 → 2421 ▼ functional
- Server version: 0.1.5 → 0.1.6 functional
- Server version: 0.1.4 → 0.1.5 functional
- New tool “enroll_optical_scan” functional
- 19 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.3 → 0.1.4 functional
- Server version: 0.1.2 → 0.1.3 functional
- 18 Nov 26 75
First indexed and scored.
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 21 Nov 2026 · Probed https://mcp.ariadnenexus.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ariadnenexus.com | CN=YE2,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5f2e0e951b60f97f7d4c0a0d43395657d53 |
| SANs: *.ariadnenexus.com, ariadnenexus.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.ariadnenexus.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| ariadnenexus.com. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.ariadnenexus.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.ariadnenexus.com/mcp | HTTPS enforced | 301 | https://mcp.ariadnenexus.com/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 →
batch_underwrite_portfolio Batch Merton Jump-Diffusion Portfolio Underwriting Engine ~322
Computes per-asset optical scores (bps), Merton jump-diffusion 99% stressed values, approved advances in integer USD cents, and effective LTV (bps) across 1-100 collateral items. Use when: sizing a fine-art or RWA credit facility from appraised cent values, optical scan digests, custody depth, and horizon days. Do not use when: signing a single-asset proof (use generate_zk_provenance_proof instead) or auditing an underwriting summary against LTV caps (use verify_underwriting_compliance instead). Behavior: Read-only actuarial solver (p99=910ms; $2.50 USD / 250 cents via X-API-Key or X-Payment; unbilled 402 quote if unentitled).
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | yes | List of 1 to 100 specialty collateral items to underwrite under Merton jump-diffusion 99% tail stress. |
| horizon_days | integer | – | Credit facility tenor and liquidation stress horizon in calendar days from 30 to 1825 (default: 365). |
| portfolio_id | string | yes | Institutional credit facility or collateral schedule identifier, 3-64 chars (e.g., "port_fine_art_2026_q4"). |
| target_advance_rate_bps | integer | – | Requested gross loan-to-value (LTV) advance rate in integer basis points from 1000 (10.00%) to 8500 (85.00%); defaults to 5000 (50.00%). |
| Name | Type | Req | Description |
|---|---|---|---|
| asset_count | integer | yes | Number of collateral items underwritten. |
| assets | array | yes | Per-asset optical scores, stressed values, and approved cent advances. |
| effective_portfolio_ltv_bps | integer | yes | Portfolio-level approved advance divided by appraised value in bps. |
| execution_latency_ms | number | yes | Server-side execution duration in milliseconds. |
| horizon_days | integer | yes | Liquidation stress horizon in calendar days. |
| portfolio_id | string | yes | Evaluated portfolio or credit facility identifier. |
| tier | string | yes | Commercial execution tier ("gated_production"). |
| tool | string | yes | Executed tool identifier ("batch_underwrite_portfolio"). |
| total_appraised_value_cents | integer | yes | Aggregate appraised portfolio value in integer USD cents. |
| total_approved_advance_cents | integer | yes | Aggregate approved loan advance in integer USD cents. |
| total_merton_stressed_value_cents | integer | yes | Aggregate Merton 99% tail-stressed value in integer USD cents. |
No examples provided.
enroll_optical_scan Zero-PII Physical Surface-BRDF & Spectral Optical Scan Enrollment ~330
Enrolls a zero-PII physical surface-BRDF microtopography and 8-band VNIR/SWIR pigment spectral descriptor pair (baseline_descriptor + intake_descriptor) into the append-only Ariadne Nexus optical forensics ledger (ANX-RFC-001). Enforces genesis baseline immutability, verifies optional ariadne-hash-optical SHA-256 commitments, and returns a deterministic basis-point concordance breakdown. Use when: registering a conservation lab or freeport scan before calling generate_zk_provenance_proof or batch_underwrite_portfolio. Do not use when: generating a signed ZK certificate (use generate_zk_provenance_proof instead) or checking manifest schema (use inspect_manifest_schema instead). Behavior: Idempotent append-only write requiring an active X-API-Key at $0.00 meter charge (60 RPM; rejects conflicting genesis baselines with HTTP 409).
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Non-PII collateral asset identifier (3-64 alphanumeric/underscore/hyphen/colon chars). |
| baseline_descriptor | object | yes | Immutable genesis or initial freeport intake physical optical scan descriptor. |
| expected_optical_scan_sha256 | string | – | Optional 32-byte SHA-256 hex digest pre-computed locally via ariadne-hash-optical. |
| intake_descriptor | object | yes | Current conservation lab or freeport inspection optical scan descriptor. |
| scanner_facility_ref | string | – | Optional non-PII conservation lab or freeport bay code (e.g. "GVA-FREEPORT-BAY-04"). |
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Enrolled collateral asset identifier. |
| baseline_newly_created | boolean | yes | True if this call created the asset's genesis baseline row; false on idempotent match. |
| baseline_sha256 | string | yes | 0x-prefixed canonical SHA-256 commitment of the immutable genesis baseline. |
| concordance_preview | object | yes | Deterministic fixed-point physical optical concordance breakdown. |
| enrolled | boolean | yes | Always true when baseline and intake scan commitments are durably enrolled. |
| execution_latency_ms | number | yes | Server-side execution duration in milliseconds. |
| intake_newly_created | boolean | yes | True if this call inserted a new intake scan row; false on idempotent retry. |
| optical_scan_sha256 | string | yes | 0x-prefixed canonical SHA-256 commitment of the enrolled intake scan. |
| verified_caller_sa | string | yes | Verified internal VPC OIDC caller service account or canary label. |
No examples provided.
generate_zk_provenance_proof Ed25519 Zero-PII Provenance Proof & Optical Score Generator ~343
Computes a 0x01-prefixed SHA-256 custodial Merkle root, optical microtopography score (7200-9985 bps), underwriting recommendation, and Ed25519-signed ZK_PROV_V1 zero-PII provenance certificate. Use when: generating a pre-bind title attestation for an asset_id and policy_ref from custodial SHA-256 digests. Do not use when: verifying an existing certificate (use verify_zk_provenance_proof instead) or sizing multi-asset portfolio loans (use batch_underwrite_portfolio instead). Behavior: Read-only attestation (p99=380ms; $2.50 USD / 250 cents via X-API-Key or X-Payment; returns an unbilled 402 quote if unentitled).
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Unique alphanumeric collateral or vault asset identifier, 3-64 chars allowing underscores, colons, or hyphens (e.g., "art_vault_basquiat_09"). |
| custody_event_hashes | array | – | Ordered list of up to 128 SHA-256 hex digests of prior custodial transfers folded into the 0x01 Merkle root; defaults to a genesis leaf if empty. |
| optical_scan_sha256 | string | – | Optional 64-character hex SHA-256 digest of the raking-light or XRF optical microtopography scan; derived from asset_id when omitted. |
| policy_ref | string | yes | Underwriting binder or specialty title policy reference ID, 3-64 chars (e.g., "POL-CHUBB-2026-441"). |
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Attested collateral identifier. |
| custody_chain_depth | integer | yes | Number of custodial transfer leaves folded into the Merkle tree. |
| execution_latency_ms | number | yes | Server-side execution duration in milliseconds. |
| optical_forensic_score_bps | integer | yes | Surface microtopography concordance score in basis points (7200-9985). |
| policy_ref | string | yes | Bound underwriting policy or binder reference. |
| tier | string | yes | Commercial execution tier ("gated_production"). |
| title_lien_clearance_merkle_root | string | yes | 0x-prefixed 64-hex SHA-256 Merkle root with 0x01 internal node separation. |
| tool | string | yes | Executed tool identifier ("generate_zk_provenance_proof"). |
| underwriting_recommendation | string | yes | Deterministic specialty-title bind recommendation. |
| zk_attestation_certificate | object | yes | Ed25519-signed ZK_PROV_V1 zero-PII attestation envelope. |
No examples provided.
inspect_manifest_schema Collateral Manifest Schema & Field Validator ~232
Returns required ANX-RFC-001 (ZK_PROV_V1) manifest fields for a collateral class and validates an optional candidate manifest object, listing missing keys and attestation readiness. Use when: checking required manifest keys or pre-validating a candidate JSON payload before SHA-256 hashing. Do not use when: validating an existing 64-hex SHA-256 digest (use verify_asset_hash instead), signing a provenance certificate (use generate_zk_provenance_proof instead), or auditing portfolio LTV caps (use verify_underwriting_compliance instead). Behavior: Read-only, stateless, deterministic schema check (p99=28ms; free discovery tier at 60 RPM without billing).
| Name | Type | Req | Description |
|---|---|---|---|
| collateral_class | string | – | Specialty collateral category whose ANX-RFC-001 manifest schema is inspected (default: "fine_art"). |
| manifest_payload | object | – | Optional candidate collateral manifest JSON object validated for required ANX-RFC-001 keys (asset_id, collateral_class, optical_scan_sha256, custody_event_hashes, appraised_value_cents). Omit to list… |
| Name | Type | Req | Description |
|---|---|---|---|
| collateral_class | string | yes | Evaluated specialty collateral classification. |
| execution_latency_ms | number | yes | Server-side execution duration in milliseconds. |
| missing_fields | array | yes | Required manifest keys absent from manifest_payload. |
| payload_checked | boolean | yes | True when a candidate manifest_payload object was supplied. |
| ready_for_zk_attestation | boolean | yes | True when manifest_payload was supplied and missing_fields is empty. |
| required_manifest_fields | array | yes | Required ANX-RFC-001 top-level manifest keys. |
| tier | string | yes | Commercial execution tier ("free_discovery"). |
| tool | string | yes | Executed tool identifier ("inspect_manifest_schema"). |
No examples provided.
verify_asset_hash Collateral SHA-256 Digest & Commitment Verifier ~243
Validates and normalizes a 64-character hexadecimal SHA-256 collateral manifest digest and derives its deterministic specialty-title registry commitment ID (cmt_*) for fine art, bullion, manuscripts, or collectibles. Use when: confirming manifest SHA-256 digest conformance and commitment binding prior to paid underwriting. Do not use when: checking unhashed JSON manifest fields (use inspect_manifest_schema instead) or verifying a signed ZK_PROV_V1 certificate (use verify_zk_provenance_proof instead). Behavior: Read-only, stateless, deterministic computation (p99=42ms; free discovery tier at 30 RPM without billing).
| Name | Type | Req | Description |
|---|---|---|---|
| asset_sha256 | string | yes | 64-character hexadecimal SHA-256 digest of the canonical collateral manifest JSON, with optional 0x prefix (e.g., "0x9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08"). |
| collateral_class | string | – | Specialty collateral classification bound into the cmt_* registry commitment ID (default: "fine_art"). |
| Name | Type | Req | Description |
|---|---|---|---|
| collateral_class | string | yes | Bound specialty collateral classification. |
| execution_latency_ms | number | yes | Server-side execution duration in milliseconds. |
| locked_production_fields | array | yes | Gated attestation fields unlocked via generate_zk_provenance_proof. |
| manifest_sha256 | string | yes | Normalized lowercase 0x-prefixed 64-hex SHA-256 digest. |
| registry_commitment_id | string | yes | Deterministic specialty-title commitment identifier prefixed with cmt_. |
| schema_conformance_valid | boolean | yes | True when the digest conforms to ANX-RFC-001 32-byte SHA-256 rules. |
| tier | string | yes | Commercial execution tier ("free_discovery"). |
| tool | string | yes | Executed tool identifier ("verify_asset_hash"). |
No examples provided.
verify_underwriting_compliance Underwriting LTV Cap & Oracle Root-of-Trust Verifier ~359
Audits a portfolio underwriting summary against the ANX-RFC-001 55% (5500 bps) Merton stressed advance cap, classifies optical forensic score thresholds, and returns the active ZK_PROV_V1 Ed25519 oracle public key and SHA-256 fingerprint. Use when: validating credit-committee LTV compliance on a batch_underwrite_portfolio quote or retrieving the oracle public key for pinning in verify_zk_provenance_proof. Do not use when: computing stressed collateral values from raw asset schedules (use batch_underwrite_portfolio instead), verifying an Ed25519 certificate signature (use verify_zk_provenance_proof instead), or checking JSON manifest fields (use inspect_manifest_schema instead). Behavior: Read-only, stateless compliance check (p99=15ms; free discovery tier at 60 RPM without billing).
| Name | Type | Req | Description |
|---|---|---|---|
| min_optical_forensic_score_bps | integer | – | Minimum item-level optical forensic score across the portfolio in basis points (0-10000; default: 8500). |
| portfolio_id | string | yes | Portfolio or credit facility identifier audited for statutory LTV compliance (e.g., "port_fine_art_2026_q4"). |
| proposed_advance_cents | integer | yes | Proposed loan advance in exact integer USD cents tested against the ANX-RFC-001 55% (5500 bps) Merton stressed advance ceiling. |
| total_appraised_value_cents | integer | yes | Aggregate appraised portfolio value in exact integer USD cents (>= 1). |
| total_merton_stressed_value_cents | integer | yes | Aggregate Merton 99% tail-stressed liquidation value in integer USD cents returned by batch_underwrite_portfolio. |
| Name | Type | Req | Description |
|---|---|---|---|
| compliant | boolean | yes | True when proposed_advance_cents <= 55% of stressed value, stressed value <= appraised value, and min_optical_forensic_score_bps >= 8000. |
| execution_latency_ms | number | yes | Server-side execution duration in milliseconds. |
| gross_ltv_bps | integer | yes | Proposed advance divided by total appraised value in basis points. |
| headroom_cents | integer | yes | Signed integer USD cents remaining under ceiling (negative indicates cap breach). |
| max_compliant_advance_cents | integer | yes | Maximum ANX-RFC-001 compliant loan advance in integer USD cents (5500 bps of stressed value). |
| optical_policy_tier | string | yes | Underwriting policy tier determined by min_optical_forensic_score_bps. |
| oracle_trust_anchor | object | yes | Active ANX-RFC-001 Ed25519 oracle root-of-trust metadata for key pinning. |
| portfolio_id | string | yes | Audited portfolio or credit facility identifier. |
| stressed_ltv_bps | integer | yes | Proposed advance divided by Merton 99% stressed value in basis points. |
| tier | string | yes | Commercial execution tier ("free_discovery"). |
| tool | string | yes | Executed tool identifier ("verify_underwriting_compliance"). |
No examples provided.
verify_zk_provenance_proof Ed25519 Zero-PII Provenance Certificate & Merkle Verifier ~369
Verifies an ariadne-zk-ed25519-v1 (ZK_PROV_V1) provenance certificate across Ed25519 signature validity, zero-PII enforcement, signed claim parity, optional pinned oracle key, and optional 0x01 SHA-256 custodial Merkle recomputation. Use when: auditing a certificate from generate_zk_provenance_proof before policy bind or loan closing. Do not use when: generating a new proof (use generate_zk_provenance_proof instead), checking a manifest digest (use verify_asset_hash instead), or auditing portfolio LTV cap compliance (use verify_underwriting_compliance instead). Behavior: Read-only, stateless cryptographic check (p99=18ms; free discovery tier at 60 RPM without billing).
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | – | Optional outer asset_id cross-checked against the signed asset claim. |
| custody_event_hashes | array | – | Optional ordered custodial SHA-256 digests used to independently recompute and verify the 0x01-prefixed Merkle root. |
| optical_forensic_score_bps | integer | – | Optional outer optical score (0-10000 bps) cross-checked against signed optical_bps. |
| pinned_oracle_pubkey_b64 | string | – | Optional out-of-band pinned base64 Ed25519 oracle public key enforced during verification. |
| policy_ref | string | – | Optional outer policy_ref cross-checked against the signed policy claim. |
| title_lien_clearance_merkle_root | string | – | Optional outer 64-hex Merkle root cross-checked against signed merkle_root. |
| zk_attestation_certificate | object | yes | Signed ZK_PROV_V1 certificate object emitted by generate_zk_provenance_proof. |
| Name | Type | Req | Description |
|---|---|---|---|
| execution_latency_ms | number | yes | Server-side execution duration in milliseconds. |
| failure_code | string | yes | Verification disposition code ("NONE" when verified is true). |
| failure_detail | string | – | Diagnostic explanation populated when verified is false. |
| merkle_chain_independently_recomputed | boolean | yes | True when custody_event_hashes were supplied and matched signed merkle_root. |
| oracle_pubkey_ed25519_b64 | string | yes | Base64 Ed25519 public key extracted from the certificate. |
| oracle_pubkey_sha256_hex | string | yes | Lowercase 64-hex SHA-256 fingerprint of the raw 32-byte Ed25519 public key. |
| pinned_key_enforced | boolean | yes | True when pinned_oracle_pubkey_b64 was supplied and matched. |
| scheme | string | yes | Evaluated certificate scheme identifier. |
| signature_valid | boolean | yes | True when the Ed25519 signature over public_statement verified cleanly. |
| signed_claims | object | yes | Parsed key-value claims from the signed ZK_PROV_V1 statement. |
| tier | string | yes | Commercial execution tier ("free_discovery"). |
| tool | string | yes | Executed tool identifier ("verify_zk_provenance_proof"). |
| verified | boolean | yes | True only when signature, zero-PII, claims, pinned key, and Merkle checks all pass. |
| zero_pii_confirmed | boolean | yes | True when seller_pii_exposed is strictly false. |
No examples provided.
How do I install the Ariadne Nexus Provenance & Underwriting MCP server?
Ariadne Nexus Provenance & Underwriting MCP is a hosted endpoint at https://mcp.ariadnenexus.com/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.ariadnenexus.com
claude mcp add --transport http com-ariadnenexus-mcp-server 'https://mcp.ariadnenexus.com/mcp'
What is the Ariadne Nexus Provenance & Underwriting MCP server?
Ariadne Nexus Provenance & Underwriting MCP is listed in the public MCP registry as com.ariadnenexus/mcp-server. Deterministic SHA-256 collateral checks, optical forensics, and ZK provenance proofs. This page covers its hosted endpoint (https://mcp.ariadnenexus.com/mcp).
Is the Ariadne Nexus Provenance & Underwriting MCP server safe to use?
Ariadne Nexus Provenance & Underwriting MCP scores 76 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 Ariadne Nexus Provenance & Underwriting MCP server expose?
Ariadne Nexus Provenance & Underwriting MCP exposes 7 tools: inspect_manifest_schema, verify_asset_hash, generate_zk_provenance_proof, verify_zk_provenance_proof, batch_underwrite_portfolio, and 2 more. Their descriptions and schemas cost roughly 2,198 tokens of context every time the server is loaded.
Does the Ariadne Nexus Provenance & Underwriting MCP server require authentication?
Yes. Ariadne Nexus Provenance & Underwriting 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 Ariadne Nexus Provenance & Underwriting MCP server still maintained?
Ariadne Nexus Provenance & Underwriting MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Ariadne Nexus Provenance & Underwriting MCP server?
VerifyMCP ran 13 checks on Ariadne Nexus Provenance & Underwriting MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.