io.github.carrotly-ai/disclosures
NPM · DISCLOSURES
Corporate disclosures from 26 official sources across 21 jurisdiction routes via ten tools.
Available components
Last scanned (2 hours ago)
Scores higher than 99% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to carrotly-ai/disclosures). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 46 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 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 4459 tokens (~139/item across 32 items; 10 tools + 22 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 (10% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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.
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 15 Oct 26 −2
- Stability: pass → 0.80 functional
- 14 Oct 26 0
- Stability: 0.97 → pass security
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 −2
- Stability: pass → 0.80 functional
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 17 Oct 2026 · Analysed npm/disclosures@0.8.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | carrotly-ai/disclosures |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/carrotly-ai/disclosures/.github/workflows/release.yml@refs/tags/v0.8.0 |
| Rekor log index | 2660700460 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ef858e92b10144ed90976663184b543eba8314f1746851555979c488d3ce957b1f2c7f48009499b1d85a734da0747149cc00de6684916dc9da44b6e37 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
CompanyCharges ~159
Registered charges (mortgages) filed against a UK company at Companies House. Without charge_id it lists the charge register with the register's own total/satisfied/part-satisfied counts; filter with status ("outstanding" is the common case). With charge_id it returns one charge's full detail: status and dates, persons entitled, particulars (fixed/floating charge, whether it covers all property, negative-pledge and bare-trustee flags), classification, and the linked filing transactions. Companies-House-specific (no jurisdiction parameter).
| Name | Type | Req | Description |
|---|---|---|---|
| charge_id | string | – | A specific charge id for full detail |
| company | string | yes | Company name or number |
| status | string | – | Filter the charge list by status (default "all") |
No output schema declared.
No examples provided.
CompanyDocument ~436
Fetch one filed document by a jurisdiction-specific transaction id. Mode "metadata" lists available renditions; "xhtml" returns paged extracted text where available; "pdf" saves a bounded local file and returns its path. Identifier schemes and extraction guarantees vary by route—read disclosures://jurisdictions/{code}. Scanned, protected, or unreadable documents are reported honestly rather than fabricated.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name or route-specific identifier. Some document ids are self-contained; the company value then labels the response context. |
| document_id | string | – | GB Companies House document id (alternative to transaction_id), or US document filename within the filing (defaults to the primary document); unused for JP/KR |
| jurisdiction | string | – | "GB" (Companies House, default), "US" (SEC EDGAR), "JP" (EDINET), "KR" (OpenDART), "FR" (info-financiere OAM), "HK" (HKEXnews), "CN" (cninfo SSE/SZSE), "TR" (KAP, by numeric disclosure id), "AE" (DFM… |
| mode | string | – | "metadata" (default), "xhtml" text, or "pdf" download |
| output_path | string | – | Where to save the PDF (mode=pdf); defaults to a temp file |
| text_offset | integer | – | mode=xhtml only: character offset to start the 50,000-character text window at (default 0); the response says what offset to pass next when more text remains |
| transaction_id | string | – | Jurisdiction-specific document id, usually returned by CompanyFilings. TR uses a numeric KAP disclosure id; AE uses a DFM efsah r_path; PH uses a PSE edge_no; AU uses an ASX documentKey. Read the sel… |
No output schema declared.
No examples provided.
CompanyFilings ~520
Search a company's regulatory filings in the selected jurisdiction. Filter by form type and date range; supported modes and identifier chaining vary by route and are documented at disclosures://jurisdictions/{code}. Returns filing metadata, identifiers, and official links, never document text; pass a compatible transaction id to CompanyDocument where supported.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name or jurisdiction-specific identifier: ticker/CIK (US), Companies House company number (GB), OpenDART 8-digit corp code or 6-digit stock code (KR), EDINET code (E + 5 digits), 4/5-digit se… |
| end_date | string | – | Latest filing date (YYYY-MM-DD); default is today |
| forms | array | – | Form-type filter, e.g. ["10-K"] or ["8-K", "DEF 14A"] |
| jurisdiction | string | – | Jurisdiction route. Omit for the US default. Read disclosures://jurisdictions/{code} before use for identifiers, credentials, supported intents, source licences, and access caveats. PH/PSE and AU/ASX… |
| limit | integer | – | Maximum filings to return (default 20) |
| mode | string | – | "search" (default), latest annual/quarterly report metadata, or "insolvency" (GB only) for insolvency-case history |
| start_date | string | – | Earliest filing date (YYYY-MM-DD); default is six years ago |
No output schema declared.
No examples provided.
CompanyFinancials ~434
Return as-filed headline financial facts from the selected jurisdiction's structured XBRL feed or bounded filing parser. Concepts, periods, currency, consolidation basis, and degradation behavior vary by route and are stated in each response. See disclosures://jurisdictions/{code} for the source and coverage contract; unsupported routes explain why rather than guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name or jurisdiction-specific identifier: ticker/CIK (US), Companies House company number (GB), OpenDART 8-digit corp code or 6-digit stock code (KR), EDINET code (E + 5 digits), 4/5-digit se… |
| concepts | array | – | Concepts to fetch (default: all) |
| jurisdiction | string | – | Jurisdiction route. Omit for the US default. Read disclosures://jurisdictions/{code} before use for identifiers, credentials, supported intents, source licences, and access caveats. PH/PSE and AU/ASX… |
| periods | integer | – | Fiscal years per concept (default 5) |
No output schema declared.
No examples provided.
CompanyInsiders ~391
List the selected jurisdiction's available insider, officer, director, or manager disclosures. The underlying regime and meaning vary by route; each response states its recency and completeness caveats, and unsupported routes explain why. See disclosures://jurisdictions/{code} before use.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name or jurisdiction-specific identifier: ticker/CIK (US), Companies House company number (GB), OpenDART 8-digit corp code or 6-digit stock code (KR), EDINET code (E + 5 digits), 4/5-digit se… |
| jurisdiction | string | – | Jurisdiction route. Omit for the US default. Read disclosures://jurisdictions/{code} before use for identifiers, credentials, supported intents, source licences, and access caveats. PH/PSE and AU/ASX… |
No output schema declared.
No examples provided.
CompanyOwners ~458
List the selected jurisdiction's available major-holder, control-register, threshold-crossing, or custodian disclosures. Every response names its threshold regime and limitations. These are filed disclosures, not a complete cap table or UBO tracing; see disclosures://jurisdictions/{code}.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name or jurisdiction-specific identifier: ticker/CIK (US), Companies House company number (GB), OpenDART 8-digit corp code or 6-digit stock code (KR), EDINET code (E + 5 digits), 4/5-digit se… |
| end_date | string | – | Latest date for the JP EDINET large-holding scan (YYYY-MM-DD); default today. Ignored by other jurisdictions. |
| jurisdiction | string | – | Jurisdiction route. Omit for the US default. Read disclosures://jurisdictions/{code} before use for identifiers, credentials, supported intents, source licences, and access caveats. PH/PSE and AU/ASX… |
| start_date | string | – | Earliest date for the JP EDINET large-holding scan (YYYY-MM-DD); default ~1 year ago. Ignored by other jurisdictions. |
No output schema declared.
No examples provided.
CompanyResolve ~391
Resolve a company name, ticker, or register identifier to canonical candidates with identifier sets and match reasons. Ambiguous matches are listed, never silently merged. Start here, then read the selected route's disclosures://jurisdictions/{code} card for coverage and access caveats.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name or jurisdiction-specific identifier: ticker/CIK (US), Companies House company number (GB), OpenDART 8-digit corp code or 6-digit stock code (KR), EDINET code (E + 5 digits), 4/5-digit se… |
| jurisdiction | string | – | Jurisdiction route. Omit for the US default. Read disclosures://jurisdictions/{code} before use for identifiers, credentials, supported intents, source licences, and access caveats. PH/PSE and AU/ASX… |
No output schema declared.
No examples provided.
OwnershipChain ~339
GLEIF Level 2 relationship data for an entity (global): direct and ultimate accounting-consolidating parents and known direct children, resolved from an LEI or legal name. Reporting exceptions (e.g. natural-person owners, non-consolidating structures) are stated explicitly. Consolidation parents are not market-disclosure ownership and not UBO tracing.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name or jurisdiction-specific identifier: ticker/CIK (US), Companies House company number (GB), OpenDART 8-digit corp code or 6-digit stock code (KR), EDINET code (E + 5 digits), 4/5-digit se… |
| Name | Type | Req | Description |
|---|---|---|---|
| children | array | yes | – |
| directParent | object | – | – |
| entity | object | – | – |
| goldenCopyPublishedAt | string | – | – |
| query | string | – | – |
| resolved | boolean | – | – |
| sourceJurisdiction | string | yes | – |
| ultimateParent | object | – | – |
No examples provided.
PersonAppointments ~401
Look up a person (not a company): cross-company roles and disqualification/enforcement lookups. jurisdiction: GB (Companies House, default), US (SEC reporting owners — surfaces private issuers too), DE (BaFin dealings persons), FR (recherche-entreprises dirigeants), AU (ASIC banned/disqualified persons — "disqualifications" mode only; AU has no free person→companies directorship index). Mode "search" finds people by name and returns their person ids; "appointments" takes one of those ids as officer_id (GB officer id, US person CIK, DE meldepflichtigerId, FR surname/"surname|first names") and lists every company/issuer the person is linked to; "disqualifications" searches the GB register, or returns a safe public-lookup link (US SALI) / an honest not-available note (DE, FR). One person holds several ids and homonyms are common — match by name and context, not a single id.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | – | "GB" (Companies House, default), "US" (SEC EDGAR reporting owners), "DE" (BaFin Directors' Dealings persons), "FR" (recherche-entreprises dirigeants), or "AU" (ASIC's CC-BY Banned and Disqualified Pe… |
| limit | integer | – | Max results (default 35, cap 100) |
| mode | string | – | "search" (default), "appointments", or "disqualifications" |
| officer_id | string | – | Person id for appointments: a GB officer id, or (US) the person's SEC CIK |
| officer_type | string | – | GB only: disqualified-officer type for officer_id detail (default natural) |
| query | string | – | Person name (for search / disqualifications search) |
No output schema declared.
No examples provided.
PrivateRaises ~389
Return US SEC Form D exempt-offering filings: amounts offered and sold, investor counts, industry, first-sale date, and named related persons. This capability is US-only; every explicit non-US route returns a specific unsupported explanation rather than substituting ordinary company filings.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name or jurisdiction-specific identifier: ticker/CIK (US), Companies House company number (GB), OpenDART 8-digit corp code or 6-digit stock code (KR), EDINET code (E + 5 digits), 4/5-digit se… |
| jurisdiction | string | – | Jurisdiction route. Omit for the US default. Read disclosures://jurisdictions/{code} before use for identifiers, credentials, supported intents, source licences, and access caveats. PH/PSE and AU/ASX… |
No output schema declared.
No examples provided.
How do I install the io.github.carrotly-ai/disclosures MCP server?
io.github.carrotly-ai/disclosures runs locally as an npm package, launched with npx -y disclosures. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · disclosures
claude mcp add carrotly-ai-disclosures -- npx -y disclosures
What is the io.github.carrotly-ai/disclosures MCP server?
io.github.carrotly-ai/disclosures is an MCP server listed in the public MCP registry as io.github.carrotly-ai/disclosures. Corporate disclosures from 26 official sources across 21 jurisdiction routes via ten tools. This page covers its npm package (disclosures).
Is the io.github.carrotly-ai/disclosures MCP server safe to use?
io.github.carrotly-ai/disclosures scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.carrotly-ai/disclosures MCP server expose?
io.github.carrotly-ai/disclosures exposes 10 tools: CompanyResolve, CompanyFilings, CompanyInsiders, CompanyOwners, CompanyFinancials, and 5 more. Their descriptions and schemas cost roughly 3,918 tokens of context every time the server is loaded.
Is the io.github.carrotly-ai/disclosures MCP server still maintained?
io.github.carrotly-ai/disclosures is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.carrotly-ai/disclosures MCP server under?
io.github.carrotly-ai/disclosures declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.