Veridion Disclosures
REMOTE · WWW.VERIDIONMARKETS.COM
Congressional stock-trade reports and the President's OGE reports, each row linked to its filing.
Available components
Last scanned (7 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security80
- 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
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1089 tokens (~155/item across 7 items; 5 tools + 2 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 Management80
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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 (60% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40.
- 20 Oct 26 0
- Tool “search_disclosures” rewrote its description, which is the text the model reads security
- “search_disclosures” reworded the description of “limit” cosmetic
- 18 Oct 26 −1
- Stability: 0.47 → fail ▼ security
- A breaking change shipped without a version bump: still 1.20.0 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_coverage” rewrote its description, which is the text the model reads security
- Tool “get_disclosure_history” rewrote its description, which is the text the model reads security
- Tool “get_status” rewrote its description, which is the text the model reads security
- Tool “list_members” rewrote its description, which is the text the model reads security
- Tool “search_disclosures” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 60% ▼ functional
- Tool “get_coverage” dropped its output schema ▼ functional
- Tool “get_status” dropped its output schema ▼ functional
- MCP protocol: fail → pass ▲ functional
- Schema quality: excellent → good functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- “search_disclosures” reworded the description of “limit” cosmetic
- “search_disclosures” reworded the description of “member_id” cosmetic
- “search_disclosures” reworded the description of “within_statutory_window” cosmetic
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://www.veridionmarkets.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.veridionmarkets.com | CN=YR1,O=Let's Encrypt,C=US | 15 Sept 2026 | 14 Dec 2026 | RSA 2048 | SHA256-RSA | 6bf690a8dcb8f708c4ef7d2fdd7baf97fb0 |
| SANs: www.veridionmarkets.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.veridionmarkets.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| veridionmarkets.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://js.stripe.com https://cdnjs.cloudflare.com https://*.vercel-analytics.com https://va.vercel-scripts.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: blob: https://images.unsplash.com https://*.coingecko.com https://*.coin-images.com https://logo.clearbit.com https://flagcdn.com https://upload.wikimedia.org https://*.supabase.co; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://*.sentry.io https://api.coingecko.com https://*.vercel-analytics.com https://va.vercel-scripts.com; frame-src 'self' https://js.stripe.com https://hooks.stripe.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self' https:; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.veridionmarkets.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.veridionmarkets.com/api/mcp | HTTPS enforced | 308 | https://www.veridionmarkets.com/api/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 →
get_coverage ~31
Live coverage counts (rows, filers, per-source totals) measured from the serving views at request time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_disclosure_history ~103
Every observed version of one disclosure, oldest first. The change stream is append-only, so an amendment supersedes rather than overwrites -- the before and after of a restated filing are both here, each with its own change block and receipt.url. restated=true means content changed after first publication; each version records what changed and when.
| Name | Type | Req | Description |
|---|---|---|---|
| disclosure_id | string | yes | Permanent disclosure_id from search_disclosures. Identifiers survive restatement and are never reused. |
| Name | Type | Req | Description |
|---|---|---|---|
| access | – | yes | – |
| cache | – | yes | – |
| data | array | yes | Every observed version of this disclosure_id, oldest first. Each entry carries its own change block (upsert or supersede, active or withdrawn) and version_id. The last entry is the current state. |
| history | object | yes | – |
| notice | string | yes | – |
| version | string | yes | – |
No examples provided.
get_status ~91
Source freshness and bulk-snapshot health. This endpoint downgrades itself when its own arithmetic says stale — it never guesses green. When state is 'degraded', degraded_reasons names each cause with its measurement; sources[].index_reconciliation says whether the government's own index lists filings not yet served; bulk_export.merkle_root is the day's commitment over every row's content_hash, for verifying a bulk download.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_members ~160
List filers with official identity (congressional filers carry their Bioguide ID; executive-branch filers return null with an explanation — identifiers are never invented). Filter by bioguide, by the exact member_id a disclosure row carries, or by a substring of the name as filed. A name search can match several filers; each result carries member_id and bioguide for an exact match.
| Name | Type | Req | Description |
|---|---|---|---|
| bioguide | string | – | Official Bioguide ID, e.g. P000197 |
| member_id | string | – | Exact filer identifier from a disclosure row, e.g. nancy-pelosi |
| name | string | – | Case-insensitive substring of the filer's full name, e.g. pelosi |
| Name | Type | Req | Description |
|---|---|---|---|
| cache | object | yes | – |
| count | integer | yes | – |
| data | array | yes | – |
| directory | object | yes | Which relation answered and how old it is. Present on every directory response so a reader never has to assume the age of what they were served. |
| identity_join | string | yes | – |
| notice | string | yes | – |
| paper_transcriptions | object | yes | Paper queue visibility independent of the directory population and measurement timestamp. Completeness state describes the annual paper measurement, not roster coverage. |
| served_at | string | yes | – |
| version | string | yes | – |
No examples provided.
search_disclosures ~462
Search receipt-linked US government financial disclosures: both chambers of Congress under the STOCK Act, plus executive-branch OGE filings (chamber 'executive', which holds the President's disclosures). Every row carries receipt.url, the government's own document for that row: a PDF page for House and OGE filings, or the Senate eFD report page, which the Senate site opens behind its own access agreement (receipt.access 'gated'). Supports point-in-time reconstruction via as_of (rows observed on or before that timestamp; no look-ahead bias) and change polling via updated_since. Results are paged; page.next_cursor continues the listing.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | ISO timestamp: only rows first observed on/before this instant |
| chamber | string | – | Filter by filing body. 'house' and 'senate' are STOCK Act periodic transaction reports; 'executive' is executive-branch OGE filings, which is where the President's disclosures are. Omit to search all. |
| cursor | string | – | Opaque page.next_cursor from a previous call |
| limit | number | – | Rows per page: 10 when omitted; up to 25 without a key and 1000 with a licensed key. A larger request returns the maximum, not an error. |
| member_id | string | – | Filter to one filer by slug, e.g. donald-trump or nancy-pelosi. The same slug appears as member.member_id on every row. |
| min_delay_days | number | – | Only rows filed at least this many days after the transaction. The STOCK Act window is 45 days, so 46 returns filings outside it. Rows without a computed delay are excluded, not guessed at. |
| ticker | string | – | Filter by ticker symbol, e.g. NVDA |
| updated_since | string | – | ISO timestamp: only rows first observed after this instant |
| within_statutory_window | boolean | – | false returns only filings made outside the statutory window that applies to that row (served as statutory_window_days); true returns only filings inside it. Unlike min_delay_days, the boundary is ea… |
| Name | Type | Req | Description |
|---|---|---|---|
| access | – | yes | – |
| cache | – | yes | – |
| coverage | object | yes | – |
| data | array | yes | – |
| notice | string | yes | – |
| page | object | yes | – |
| version | string | yes | – |
No examples provided.
How do I install the Veridion Disclosures MCP server?
Veridion Disclosures is a hosted endpoint at https://www.veridionmarkets.com/api/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 · www.veridionmarkets.com
claude mcp add --transport http com-veridionmarkets-disclosures 'https://www.veridionmarkets.com/api/mcp'
What is the Veridion Disclosures MCP server?
Veridion Disclosures is an MCP server listed in the public MCP registry as com.veridionmarkets/disclosures. Congressional stock-trade reports and the President's OGE reports, each row linked to its filing. This page covers its hosted endpoint (https://www.veridionmarkets.com/api/mcp).
Is the Veridion Disclosures MCP server safe to use?
Veridion Disclosures scores 85 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 Veridion Disclosures MCP server expose?
Veridion Disclosures exposes 5 tools: search_disclosures, get_disclosure_history, list_members, get_coverage, get_status. Their descriptions and schemas cost roughly 847 tokens of context every time the server is loaded.
Does the Veridion Disclosures MCP server require authentication?
No. We connected to Veridion Disclosures without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Veridion Disclosures MCP server still maintained?
Veridion Disclosures 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.
What did VerifyMCP test on the Veridion Disclosures MCP server?
VerifyMCP ran 13 checks on Veridion Disclosures, 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.