Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine

REMOTE · ARIADNENEXUS.COM

SEC Form TCR whistleblower forensics, Beneish M-Score XBRL detection, and APA docket synthesis.

Available components

+4 this week 73 Trust /100

Last scanned (14 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3015 tokens (~274/item across 11 items; 7 tools + 4 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 Management33
  • Stability observed for 10 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 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

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 →

Changelog

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1
    • Schema quality: 2517 → 3015 ▼ functional
    • Server version: 1.3.2 → 1.3.3 functional
    • New tool “audit_broker_dealer_forensics” functional
  • 13 Nov 26 −2
    • HSTS header: pass → fail ▼ security
  • 12 Nov 26 +1
    • Tool “get_sovereign_policy_brief” rewrote its description, which is the text the model reads security
    • Tool “screen_ofac_entity” rewrote its description, which is the text the model reads security
    • Tool “synthesize_regulatory_docket” rewrote its description, which is the text the model reads security
    • Schema quality: 279 → 251 ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.3.0 → 1.3.2 functional
    • “generate_sec_tcr_bounty_dossier” dropped the optional parameter “apiKey” cosmetic
    • “generate_sec_tcr_bounty_dossier” dropped the optional parameter “paymentToken” cosmetic
    • “get_sovereign_policy_brief” dropped the optional parameter “apiKey” cosmetic
    • “get_sovereign_policy_brief” dropped the optional parameter “paymentToken” cosmetic
    • “screen_ofac_entity” dropped the optional parameter “apiKey” cosmetic
    • “screen_ofac_entity” dropped the optional parameter “paymentToken” cosmetic
    • “synthesize_regulatory_docket” dropped the optional parameter “apiKey” cosmetic
    • “synthesize_regulatory_docket” dropped the optional parameter “paymentToken” cosmetic
  • 11 Nov 26 70

    First indexed and scored.

Diagnostics

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://ariadnenexus.com/mcp/sec-forensics-whistleblower

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 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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ariadnenexus.com/mcp/sec-forensics-whistleblower Verified 200
http (plaintext) http://ariadnenexus.com/mcp/sec-forensics-whistleblower HTTPS enforced 301 https://ariadnenexus.com/mcp/sec-forensics-whistleblower
MCP tools · 7 exposed · ~2,655 tokens

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 →

Tool Tokens
audit_broker_dealer_forensics ~498

Synthesizes structured broker-dealer counterparty and prime-clearing forensics combining SEC Form X-17A-5 (FOCUS Report) balance sheet and Rule 15c3-1 net capital cushion multiples, SEC Form 13F-HR institutional equity/option book telemetry, FINRA BrokerCheck SRO enforcement dockets, and SHA-256 OFAC sanctions Merkle attestations by CIK, FINRA CRD, or entity name. Use when: auditing a registered broker-dealer, quantitative market maker, or clearing counterparty (e.g., HRT Financial LP CIK 0001475597 / CRD 152144, HRT Execution Services LLC CIK 0001263128 / CRD 128491, or any SEC-filing broker-dealer CIK) for Rule 15c3-1 excess net capital, repo leverage, 13F concentration, or SRO regulatory history. Do not use when: screening a non-broker-dealer entity solely against OFAC SDN sanctions (use screen_ofac_entity instead) or computing corporate issuer Beneish M-Score whistleblower bounties (use generate_sec_tcr_bounty_dossier instead). Behavior: Read-only, deterministic forensic synthesis ($2.50 USD per call via HTTP header x-api-key or x-payment-token; returns an x402/MPP paymentChallenge without charging if credentials are omitted).

NameTypeReqDescription
cikstring–10-digit SEC Central Index Key (CIK) of the registered broker-dealer or institutional investment manager (e.g., "0001475597" for HRT Financial LP or "0001263128" for HRT Execution Services LLC).
crdstring–Optional FINRA BrokerCheck Central Registration Depository (CRD) number (e.g., "152144" or "128491").
entity_namestring–Optional legal or common name of the broker-dealer firm used when CIK or CRD is omitted (e.g., "Hudson River Trading", "HRT Financial LP").
include_sro_docketsboolean–Whether to include itemized FINRA and exchange SRO AWC/consent enforcement dockets (default: true).
top_holdings_limitnumber–Maximum number of ranked SEC Form 13F-HR holdings to return between 1 and 50 (default: 10).
NameTypeReqDescription
entity_profileobjectyesResolved broker-dealer CIK, CRD, LEI, auditor, credit ratings, and prime brokers.
finra_sro_enforcement_matrixobject–FINRA BrokerCheck SRO disclosure summary and itemized enforcement dockets.
focus_x17a5_net_capital_forensicsobject–SEC Form X-17A-5 balance sheet, repo leverage, and Rule 15c3-1 net capital cushion.
form_13f_institutional_telemetryobject–SEC Form 13F-HR equity, put, and call book summary plus ranked holdings.
ofac_sanctions_attestationobjectyesOFAC SDN screening status and SHA-256 Merkle proof.
receiptstring–Cryptographic payment or API key settlement receipt ID.
toolstringyesExecuted MCP tool identifier ("audit_broker_dealer_forensics").

No examples provided.

generate_sec_tcr_bounty_dossier ~280

Computes the 8-variable Beneish M-Score, first-digit Benford Chi-Square statistic, Halliburton II event-study t-statistic, Dodd-Frank § 922 (10%-30%) SEC Whistleblower bounty projection, and PSLRA litigation syndicate recovery model for a public issuer. Use when: a litigation finance fund, securities class-action counsel, or whistleblower syndicate requires quantitative accounting anomaly and event-study verification under 17 CFR § 240.21F-4(b)(3). Do not use when: pricing standard fixed-income CUSIP bonds or running macro interest rate stress tests (use get_cusip_valuation or run_portfolio_stress_test instead). Behavior: Read-only, deterministic quantitative forensic calculation with zero external side effects.

NameTypeReqDescription
docket_idstring–Forensic docket identifier (e.g., "TCR-2026-0891", "TCR-2026-0914", "TCR-2026-0942", "TCR-2026-0978").
dsrinumber–Days Sales in Receivables Index (DSRI).
estimated_sec_sanction_usdnumber–Estimated SEC monetary sanction in USD.
tatanumber–Total Accruals to Total Assets (TATA).
NameTypeReqDescription
beneish_m_scorenumberyesComputed 8-variable Beneish M-Score.
checkout_endpointstring–One-time Stripe Checkout syndication endpoint.
docket_idstringyesForensic docket identifier.
manipulation_flagbooleanyesTrue when M-Score exceeds -1.78 threshold.
receiptstring–Cryptographic payment settlement receipt ID.
sec_bounty_max_30pct_usdnumber–30% statutory maximum SEC whistleblower bounty.
sec_bounty_mid_20pct_usdnumberyes20% midpoint SEC whistleblower bounty.
sec_bounty_min_10pct_usdnumber–10% statutory minimum SEC whistleblower bounty.
statutory_authoritystring–Applicable SEC and PSLRA statutory authority.
syndicate_exclusive_retainer_usdnumber–Upfront exclusive syndicate retainer in USD.
toolstringyesExecuted MCP tool identifier.

No examples provided.

get_sovereign_policy_brief ~281

Generates the Weekly Sovereign Macro-Prudential & Sanctions Monitor for Federal Reserve (FOMC / Financial Stability), U.S. Treasury (OFR / OFAC / FinCEN), and SEC DERA policy desks, combining Dual-Track monetary stability indicators (10Y-3M yield curve inversion, FINRA TRACE G-SIB credit spread dislocations, H.8 bank credit impulse) and autonomous x402 sanctions enforcement telemetry. Use when: synthesizing macro-prudential systemic risk briefings, monitoring aggregate sanctions enforcement trends, or evaluating FAR Subpart 13.2 ($9,500 GPC Micro-Purchase) policy data procurement options. Do not use when: screening a specific individual or corporate counterparty against the OFAC SDN list (use screen_ofac_entity instead), or drafting a formal APA 5 U.S.C. § 553 public comment letter for a specific agency rulemaking docket (use synthesize_regulatory_docket instead). Behavior: Read-only, deterministic intelligence report generator ($1.00 USD per call via HTTP header x-api-key or x-payment-token; returns an x402/MPP paymentChallenge without charging if credentials are omitted).

NameTypeReqDescription
include_markdownboolean–When true, includes the complete publication-ready Markdown policy brief in markdown_body alongside structured JSON telemetry (default: true).
NameTypeReqDescription
brief_idstringyesUnique weekly policy brief identifier.
cadence_schedulestring–Publication cadence schedule.
executive_summarystringyesHigh-level macro-prudential and illicit-finance synthesis.
generated_atstring–ISO-8601 generation timestamp.
illicit_finance_track_findingsarrayyesTrack 2 Treasury FinCEN / OFAC autonomous x402 sanctions findings.
markdown_bodystring–Full formatted Markdown policy brief (present when include_markdown is true).
monetary_track_findingsarrayyesTrack 1 Federal Reserve / OFR monetary and credit liquidity findings.
policy_directivesarrayyesActionable regulatory policy recommendations.
procurement_optionsobject–FAR Subpart 13.2 ($9,500 GPC Micro-Purchase) and x402 procurement channels.
receiptstring–Cryptographic payment or API key settlement receipt ID.
reporting_weekstring–ISO reporting week label.
snapshotobject–Underlying quantitative macro and sanctions telemetry snapshot.
subtitlestring–Target regulatory desk subtitle.
titlestringyesFormal policy brief title.
toolstringyesExecuted tool identifier ("get_sovereign_policy_brief").

No examples provided.

provision_agent_key ~556

Returns pricing specifications, monthly query quotas, rate limits (RPM), 1-click Stripe Checkout links (starting at $10/mo MCP Builder Pass up to $9,500/yr FAR 13.2 GPC & Unlimited Closing Blanket licenses), Stripe Projects CLI commands (`stripe provision ariadnenexus`), and optional live Stripe Checkout session URLs (`mint_stripe_session: true`) for obtaining a live Ariadne Nexus Developer API key (`nexus_live_...`). Use when: an agent, developer, escrow attorney, or litigation desk needs pricing comparisons or a direct clickable Stripe Checkout URL after encountering a paymentChallenge on paid tools. Do not use when: redeeming an already-paid Stripe Checkout `cs_...` session ID for its API key (use redeem_checkout_session instead), or estimating basis-point RWA clearing take-rates (use calculate_clearing_fee instead). Behavior: Free discovery and checkout-link generator ($0.00 USD). Does not charge any payment method on invocation; billing only occurs if the human completes payment at the returned Stripe Checkout URL.

NameTypeReqDescription
client_namestring–Optional organization, law firm, fund, or autonomous agent harness name to pre-populate in checkout metadata (default: "Autonomous Agent Desk").
emailstring–Optional billing or technical contact email address to pre-populate in Stripe Checkout for automated API key fulfillment (default: "agent-ops@example.com").
mint_stripe_sessionboolean–When true and paired with a valid buyer email, creates and returns a live checkout.stripe.com session URL alongside the 1-click redirect link (default: false).
symbolstring–Optional target ticker, 9-digit CUSIP, certificate ID, or SEC TCR docket reference for one-time institutional SKUs (default: "GS.30").
tierstring–Target subscription tier or one-time SKU: "EVAL_PASS" ($10/mo, 250 calls), "STARTER" ($99/mo, 10k calls), "QUANT_PRO" ($499/mo, 100k calls), "ENTERPRISE_CFO" ($2,499/mo, 1M calls), "SAFE_HARBOR_CERT_…
NameTypeReqDescription
checkout_endpointstringyesHTTP endpoint to create a live Stripe Checkout session.
checkout_session_idstring–Created Stripe Checkout session ID (cs_...) when mint_stripe_session is true.
cli_provision_commandstringyesStripe Projects CLI command for instant API key provisioning.
client_namestring–Resolved client organization name.
emailstring–Resolved billing contact email.
eval_pass_10_usd_urlstring–1-click checkout URL for the $10/mo MCP Builder & Evaluation Pass (250 calls/mo).
live_stripe_checkout_urlstring–Direct checkout.stripe.com URL when mint_stripe_session is true.
messagestringyesOnboarding and instant checkout instructions summary.
one_click_checkout_urlstringyesClickable 1-click URL that opens a live Stripe Checkout session in the browser.
persona_procurement_tracksobject–Tailored procurement tracks across developer, HUD-1 escrow pass-through, and FAR 13.2 / litigation personas.
post_checkout_next_stepstring–Instructions to redeem the paid cs_... session ID via redeem_checkout_session.
selected_tierobjectyesPricing, quota, and rate-limit metadata for the requested tier or SKU.

No examples provided.

redeem_checkout_session ~243

Verifies a completed Stripe Checkout session (`cs_...`) directly against Ariadne Nexus billing and deterministically returns the buyer’s live HMAC-signed `nexus_live_...` API key, monthly quota, and 1-click Cursor / VS Code / Claude Code installation links. Use when: a user has just completed payment at Stripe Checkout and wants to immediately claim and activate their `nexus_live_...` API key inside Claude, Cursor, VS Code, or an autonomous agent without waiting for email delivery. Do not use when: the user has not yet paid or needs a checkout link first (use provision_agent_key instead). Behavior: Free, read-only, deterministic verification and HMAC credential derivation ($0.00 USD; idempotent across repeated invocations for the same paid `cs_...` session ID).

NameTypeReqDescription
emailstring–Optional billing email address used during Stripe Checkout (required when re-redeeming sessions older than 24 hours).
session_idstringyesPaid Stripe Checkout Session identifier starting with "cs_" (e.g., "cs_live_..." from the /billing/success redirect URL or Stripe receipt).
NameTypeReqDescription
amount_paid_usdnumber–Total settled USD amount.
api_keystring–Live HMAC-signed Ariadne Nexus API key ("nexus_live_...").
deliverable_unlock_urlstring–Direct URL to any unlocked closing certificate, CUSIP vault, or forensic workpaper.
errorstring–Diagnostic message if session is unpaid or invalid.
ide_quick_installobject–Pre-authenticated 1-click Cursor, VS Code, and Claude Code CLI installation commands.
included_queries_per_monthnumber–Monthly included MCP and REST tool calls.
purchased_skustring–Settled subscription tier or one-time institutional SKU.
rate_limit_per_minutenumber–Maximum requests per minute (RPM).
session_idstring–Verified Stripe Checkout session ID.
statusnumberyesHTTP-equivalent verification status code (200 on paid settlement, 402 if unpaid).
successbooleanyesTrue when payment is verified and the live API key is issued.
tierstring–Activated API quota tier ("EVAL_PASS", "STARTER", "QUANT_PRO", or "ENTERPRISE_CFO").

No examples provided.

screen_ofac_entity ~366

Screens a corporate entity or individual counterparty against the U.S. Treasury OFAC Specially Designated Nationals (SDN) and consolidated sanctions registries using exact identifier matching (LEI/CIK/CRN) and Jaro-Winkler fuzzy phonetic resolution, returning a compliance verdict and SHA-256 Merkle audit proof. Use when: verifying whether a specific company, vessel, wallet counterparty, or individual is sanctioned before onboarding or settlement. Do not use when: retrieving macro-level weekly sanctions policy trends (use get_sovereign_policy_brief instead) or drafting regulatory comment letters on FinCEN/OFAC rulemakings (use synthesize_regulatory_docket instead). Behavior: Read-only, deterministic compliance check ($0.50 USD per call via HTTP header x-api-key or x-payment-token; returns an x402/MPP paymentChallenge without charging if credentials are omitted).

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 two-letter jurisdiction code of incorporation or residence (e.g., "US", "RU", "IR", "GB"; default: "US").
entity_namestringyesFull legal name of the corporation, financial institution, vessel, or individual to screen (e.g., "Vnesheconombank", "Blackstone Inc.").
fuzzy_thresholdnumber–Jaro-Winkler string similarity threshold between 0.60 (broad alias capture) and 0.95 (strict match) required to flag a match (default: 0.85).
registration_numberstring–Optional 20-character Legal Entity Identifier (LEI), Corporate Registration Number (CRN), or 10-digit SEC Central Index Key (CIK) for exact registry matching.
NameTypeReqDescription
entity_namestringyesScreened legal entity name.
receiptstring–Cryptographic payment or API key settlement receipt ID.
toolstringyesExecuted tool identifier ("screen_ofac_entity").
verdictobjectyesForensic sanctions screening result and cryptographic proof.

No examples provided.

synthesize_regulatory_docket ~431

Drafts a formal Administrative Procedure Act (APA, 5 U.S.C. § 553) Public Comment Letter cited with empirical Ariadne Nexus FINRA TRACE G-SIB spread and x402 OFAC SDN screening telemetry for active Federal Reserve/OFR, FinCEN/OFAC, SEC DERA, or FSOC rulemaking dockets. Use when: preparing a statutory public comment submission or empirical policy memorandum for a specific federal financial regulatory docket (`FED_TREASURY_OFR`, `FINCEN_OFAC_X402`, `SEC_DERA_TRACE`, or `FSOC_NONBANK_CONTAGION`). Do not use when: reading the weekly macro-prudential policy monitor (use get_sovereign_policy_brief instead) or screening an entity against OFAC sanctions lists (use screen_ofac_entity instead). Behavior: Read-only local document synthesis ($2.50 USD per call via HTTP header x-api-key or x-payment-token). Does NOT automatically transmit or file comments with regulations.gov or any external agency; returns the structured comment text and cryptographic SHA-256 citation hash for human review.

NameTypeReqDescription
agency_idstring–Target federal regulatory docket identifier: "FED_TREASURY_OFR" (Treasury OFR / Fed Systemic Liquidity), "FINCEN_OFAC_X402" (FinCEN/OFAC Autonomous Agent AML/Sanctions), "SEC_DERA_TRACE" (SEC DERA Fi…
custom_focus_notestring–Optional custom empirical observation or policy emphasis paragraph to embed into the statutory comment letter.
submitter_entitystring–Legal name of the submitting institution or research division (default: "Ariadne Nexus Sovereign Intelligence & Quantitative Research").
submitter_signatorystring–Name and title of the signing officer or division signatory (default: "Office of Sovereign Policy & Quantitative Strategy").
NameTypeReqDescription
agency_idstringyesTarget regulatory agency docket key.
agency_namestring–Full federal regulatory agency name.
cryptographic_attestation_hashstringyesSHA-256 integrity digest of the synthesized letter and telemetry.
docket_numberstringyesOfficial federal rulemaking docket number.
empirical_citationsarray–Quantitative FINRA TRACE and x402 telemetry citations embedded in the letter.
letter_idstring–Unique generated APA comment letter identifier.
markdown_letterstringyesComplete formatted APA public comment letter in Markdown.
policy_recommendationsarray–Numbered statutory rulemaking recommendations.
receiptstring–Cryptographic payment or API key settlement receipt ID.
rinstring–Regulation Identifier Number (RIN).
rule_titlestring–Formal federal register rulemaking title.
statutory_authoritystringyesGoverning statutory citation (e.g., "5 U.S.C. § 553").
submitter_entitystring–Submitting organization name.
submitter_signatorystring–Signatory officer or division title.
toolstringyesExecuted tool identifier ("synthesize_regulatory_docket").

No examples provided.

Install

How do I install the Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine MCP server?

Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine is a hosted endpoint at https://ariadnenexus.com/mcp/sec-forensics-whistleblower, 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 · ariadnenexus.com

# add to Claude Code
claude mcp add --transport http com-ariadnenexus-sec-forensics-whistleblower 'https://ariadnenexus.com/mcp/sec-forensics-whistleblower'
Common questions

What is the Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine MCP server?

Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine is an MCP server listed in the public MCP registry as com.ariadnenexus/sec-forensics-whistleblower. SEC Form TCR whistleblower forensics, Beneish M-Score XBRL detection, and APA docket synthesis. This page covers its hosted endpoint (https://ariadnenexus.com/mcp/sec-forensics-whistleblower).

Is the Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine MCP server safe to use?

Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine scores 73 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 SEC Form TCR Forensics & Whistleblower Engine MCP server expose?

Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine exposes 7 tools: screen_ofac_entity, get_sovereign_policy_brief, synthesize_regulatory_docket, provision_agent_key, redeem_checkout_session, and 2 more. Their descriptions and schemas cost roughly 2,655 tokens of context every time the server is loaded.

Does the Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine MCP server require authentication?

No. We connected to Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine MCP server still maintained?

Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine 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 SEC Form TCR Forensics & Whistleblower Engine MCP server?

VerifyMCP ran 13 checks on Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine, 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.