P0: SEC filings and public contracts
REMOTE · X402-BAZAAR-RANK.X402-BAZAAR-RANK-WORKER.WORKERS.DEV
SEC EDGAR filings, key financials and public contract awards for AI agents, pay per call
Available components
Last scanned (22 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 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 Security63
- 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability55
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1026 tokens (~342/item across 3 items; 3 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 Management47
- Stability observed for 14 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- Tool “sec_filings_batch” rewrote its description, which is the text the model reads security
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
- Tool “sec_filings” rewrote its description, which is the text the model reads security
- Tool “sec_filings_batch” rewrote its description, which is the text the model reads security
- Tool “tenders_awards” rewrote its description, which is the text the model reads security
- Schema quality: 408 → 348 ▲ functional
- “tenders_awards” reworded the description of “q” cosmetic
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “sec_filings” rewrote its description, which is the text the model reads security
- Tool “sec_filings_batch” rewrote its description, which is the text the model reads security
- Tool “tenders_awards” rewrote its description, which is the text the model reads security
- Schema quality: 359 → 408 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- “sec_filings” reworded the description of “periods” cosmetic
- “sec_filings” reworded the description of “quarters” cosmetic
- “sec_filings_batch” reworded the description of “facts” 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 21 Nov 2026 · Probed https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sec-filings-tenders
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=x402-bazaar-rank-worker.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 8 Nov 2026 | 6 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6c09b073fe5d3fd83fd987465725765b6e5 |
| SANs: *.x402-bazaar-rank-worker.workers.dev, x402-bazaar-rank-worker.workers.dev | ||||||
| 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 x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | 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://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sec-filings-tenders | Verified | 200 | |
| http (plaintext) | http://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sec-filings-tenders | Served over HTTP | 200 |
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 →
sec_filings SEC filings ~346
Use when you need a US public company's SEC EDGAR filings and key financials by ticker or CIK: latest filings (form, dates, accession, link; filter by form, since) plus latest XBRL facts: revenue. Returns the paid x402 request for your input (GET /sec/filings, $0.003 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For several companies at once use sec_filings_batch. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | SEC Central Index Key, e.g. 320193 (send this or ticker) |
| facts | string | – | 0 = filings only |
| form | string | – | optional comma list of form types to keep, e.g. 10-K,10-Q,8-K |
| limit | integer | – | max filings returned |
| periods | integer | – | n = 1-10: also return the last n full fiscal years of every fact, plus ttm where it can be derived; the response grows with n; not with facts=0 |
| quarters | integer | – | n = 1-20: also return the last n quarters of every fact (quarter-only values, derived ones marked), plus ttm where it can be derived; the response grows with n; not with facts=0 |
| since | string | – | filed on/after YYYY-MM-DD |
| ticker | string | – | stock ticker, e.g. AAPL or BRK.B (send this or cik) |
No output schema declared.
No examples provided.
sec_filings_batch SEC filings batch ~264
Use when you need recent SEC EDGAR filings for several US public companies at once: up to 10 tickers or CIKs in one POST (duplicates removed). Returns the paid x402 request for your input (POST /sec/filings/batch, $0.03 per call; schema linked). POST that JSON body to the URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For one company use sec_filings.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | 1 to 10 tickers or CIKs; duplicates are removed |
| facts | string|integer | – | optional, for every company: 0 = filings only (no XBRL facts; smaller response; works for big banks too), default 1 (filings plus latest facts) |
| form | string | – | optional, for every company: comma list of form types, e.g. 10-K,10-Q,8-K |
| limit | string|integer | – | optional, for every company: max filings returned (all requested forms together, newest first), as in the single call |
| since | string | – | optional, for every company: only filings filed on/after this date, YYYY-MM-DD |
No output schema declared.
No examples provided.
tenders_awards Tenders awards ~229
Use when an agent needs recent public contract award notices with the winning companies: per award title, buyer, winner names, country, value, date and notice link. Returns the paid x402 request for your input (GET /tenders/awards, $0.01 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Buyer country, ISO alpha-2: EU/EEA member states and CH (TED), GB (Contracts Finder), US (USAspending). Omit with q to search all three. |
| days | integer | – | Look-back window in days, 1-60 (default 30). |
| limit | integer | – | Max awards returned, 1-25 (default 10). |
| q | string | – | Keywords (1-6 words, every word has to match), e.g. cloud hosting. Needed unless country is given. |
No output schema declared.
No examples provided.
How do I install the P0: SEC filings and public contracts MCP server?
P0: SEC filings and public contracts is a hosted endpoint at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sec-filings-tenders, 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 · x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev
claude mcp add --transport http dev-workers-x402-bazaar-rank-worker-x402-bazaar- 'https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sec-filings-tenders'
What is the P0: SEC filings and public contracts MCP server?
P0: SEC filings and public contracts is an MCP server listed in the public MCP registry as dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/sec-fi…. SEC EDGAR filings, key financials and public contract awards for AI agents, pay per call. This page covers its hosted endpoint (https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sec-filings-tenders).
Is the P0: SEC filings and public contracts MCP server safe to use?
P0: SEC filings and public contracts scores 68 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 P0: SEC filings and public contracts MCP server expose?
P0: SEC filings and public contracts exposes 3 tools: sec_filings, sec_filings_batch, tenders_awards. Their descriptions and schemas cost roughly 839 tokens of context every time the server is loaded.
Does the P0: SEC filings and public contracts MCP server require authentication?
No. We connected to P0: SEC filings and public contracts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the P0: SEC filings and public contracts MCP server still maintained?
P0: SEC filings and public contracts 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 P0: SEC filings and public contracts MCP server?
VerifyMCP ran 13 checks on P0: SEC filings and public contracts, 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.