Ariadne Nexus Provenance & Underwriting MCP server
com.ariadnenexus/mcp-serverariadnenexus.comstreamable-httpv0.1.8Scanned
Deterministic SHA-256 collateral checks, optical forensics, and ZK provenance proofs.
7 tools: 5 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Ariadne Nexus Provenance & Underwriting MCP server can do
The Ariadne Nexus Provenance & Underwriting MCP server is published by ariadnenexus.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (5 tools: generate_zk_provenance_proof, verify_zk_provenance_proof, batch_underwrite_portfolio, verify_underwriting_compliance and 1 more), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 0.1.8.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 5Claude Code: ask
batch_underwrite_portfolioComputes 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- title: Batch Merton Jump-Diffusion Portfolio Underwriting Engine
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
enroll_optical_scanEnrolls a zero-PII physical surface-BRDF microtopography and 8-band VNIR/SWIR pigment spectral descriptor pair (baseline_descriptor + intake_descriptor) into the append-only Ariadn…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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).
Annotations the server declares
- title: Zero-PII Physical Surface-BRDF & Spectral Optical Scan Enrollment
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
generate_zk_provenance_proofComputes a 0x01-prefixed SHA-256 custodial Merkle root, optical microtopography score (7200-9985 bps), underwriting recommendation, and Ed25519-signed ZK_PROV_V1 zero-PII provenanc…1 finding
Why it is in this group
- The name "generate_zk_provenance_proof" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "generate_zk_provenance_proof" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_zk_provenance_proof" says "generate": a word for a change.
Description, as the server wrote it 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).
Annotations the server declares
- title: Ed25519 Zero-PII Provenance Proof & Optical Score Generator
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_underwriting_complianceAudits 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_…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- title: Underwriting LTV Cap & Oracle Root-of-Trust Verifier
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_zk_provenance_proofVerifies 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 …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- title: Ed25519 Zero-PII Provenance Certificate & Merkle Verifier
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
inspect_manifest_schemaReturns 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…No findings
Why it is in this group
- The name "inspect_manifest_schema" says "inspect": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Collateral Manifest Schema & Field Validator
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_asset_hashValidates and normalizes a 64-character hexadecimal SHA-256 collateral manifest digest and derives its deterministic specialty-title registry commitment ID (cmt_*) for fine art, bu…No findings
Why it is in this group
- The description's first verb is "validate": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Collateral SHA-256 Digest & Commitment Verifier
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:18 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.ariadnenexus.com/mcp: tools/list returned 6 tools to an anonymous client, including generate_zk_provenance_proof (write), verify_zk_provenance_proof (write), batch_underwrite_portfolio (write), verify_underwriting_compliance (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "generate_zk_provenance_proof" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_zk_provenance_proof" says "generate": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added.+1 addedView diff
- Added:enroll_optical_scanChanges things
Tools2 added, 4 changed.+2 added~4 changedView diff
- Added:verify_underwriting_complianceChanges things
- Added:verify_zk_provenance_proofChanges things
- Changed:batch_underwrite_portfolioChanges thingstitledescriptioninputSchemaannotations
- Changed:generate_zk_provenance_proofChanges thingstitledescriptioninputSchemaannotations
- Changed:inspect_manifest_schemaOnly readstitledescriptioninputSchemaannotations
- Changed:verify_asset_hashOnly readstitledescriptioninputSchemaannotations
Install
Pinned to version 0.1.8. Values in angle brackets are yours to fill in.
claude mcp add --transport http ariadnenexus https://mcp.ariadnenexus.com/mcpclaude mcp add --transport http ariadnenexus https://mcp.ariadnenexus.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ariadnenexus__inspect_manifest_schema",
"mcp__ariadnenexus__verify_asset_hash"
],
"ask": [
"mcp__ariadnenexus__generate_zk_provenance_proof",
"mcp__ariadnenexus__verify_zk_provenance_proof",
"mcp__ariadnenexus__batch_underwrite_portfolio",
"mcp__ariadnenexus__verify_underwriting_compliance",
"mcp__ariadnenexus__enroll_optical_scan"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ariadnenexus. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.ariadnenexus/mcp-server/verify?hash=914b1439dc9f29876644ce0ecf648dadd7689b19ca288dcb5501b494eb969b0d" | jq -e '.changed == false'Pinned hash 914b1439dc9f, from Nov 21, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.ariadnenexus/mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.ariadnenexus/mcp-server)Source: MCP Registry · repository. Synced Nov 21, 2026, 02:17 UTC.
Ariadne Nexus Provenance & Underwriting MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Ariadne Nexus Provenance & Underwriting MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Ariadne Nexus Provenance & Underwriting MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Ariadne Nexus Provenance & Underwriting MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Ariadne Nexus Provenance & Underwriting MCP server have?
- 7 tools: 5 write, 2 read. generate_zk_provenance_proof, verify_zk_provenance_proof, batch_underwrite_portfolio, verify_underwriting_compliance, enroll_optical_scan, inspect_manifest_schema and verify_asset_hash.
Does the Ariadne Nexus Provenance & Underwriting MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Ariadne Nexus Provenance & Underwriting MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Ariadne Nexus Provenance & Underwriting MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.