Proposition 65
NPM · @TOOLSTOP/PROP65 · 2 COMPONENTS · SCANNED AUG 14
Is a chemical on California's Proposition 65 list, and does it need a warning?
Available components
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 →
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 toolstop/toolstop). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 905 tokens (~226/item across 4 items; 4 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @toolstop/prop65
claude mcp add dev-toolstop-prop65 -- npx -y @toolstop/prop65
codex mcp add dev-toolstop-prop65 -- npx -y @toolstop/prop65
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-toolstop-prop65": {
"type": "local",
"command": [
"npx",
"-y",
"@toolstop/prop65"
],
"enabled": true
}
}
} openclaw mcp add dev-toolstop-prop65 --command npx --arg -y --arg @toolstop/prop65
mcp_servers:
dev-toolstop-prop65:
command: "npx"
args: ["-y", "@toolstop/prop65"] {
"mcpServers": {
"dev-toolstop-prop65": {
"command": "npx",
"args": [
"-y",
"@toolstop/prop65"
]
}
}
} 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.
- 12 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Aug 26 61
First indexed and scored.
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 14 Aug 2026 · Analysed npm/@toolstop/prop65@0.1.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 | toolstop/toolstop |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/toolstop/toolstop/.github/workflows/deploy.yml@refs/heads/main |
| Rekor log index | 2417265942 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:04f3a61b7b74a9dcedfa6e9a65fabbc84323658e9c53fbc2d26a959b35e0f3743fdcef067f0d224dd9219eed3ab0168ac86986001263ff3d02c839440 |
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
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.
check_prop65 Is this chemical on the Proposition 65 list ~146
Look up a chemical by CAS number or name and report whether it is on California's Proposition 65 list. Use this when deciding whether a product sold into California needs a warning label. Returns every matching entry with the toxicity endpoint, the listing mechanism, the date listed and the safe-harbour level where one has been adopted, plus whether the entry has since been delisted. A `not_found` result does not mean the chemical is safe or unregulated: it means this edition of this one list has no entry under that name or number.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A CAS number such as 71-43-2, or a chemical name such as Benzene. |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | – | Possible chemicals, when the name matched several entries. |
| delistedOnly | boolean | – | True when every matching entry was listed and later removed. |
| edition | string | – | The edition of the list this answer came from. |
| entries | array | – | Each matching entry, including delisted ones, with its endpoint and safe-harbour level. |
| listed | boolean | – | Whether an active (not delisted) entry exists. Present when status is `ok`. |
| notCovered | array | – | What this answer does not establish. Present on both hits and misses. |
| status | string | yes | Outcome of the lookup. `not_found` is not a clearance. `ambiguous` means the name matched several entries and you should pick one or use a CAS number. |
No examples provided.
describe_prop65_list What this list is and what it covers ~111
Report the size and edition of the embedded Proposition 65 list, and what the listing-mechanism codes mean. Use this to check how current the data is before relying on a lookup, or to interpret the `AB`, `SQE`, `FR` and `LC` codes on an entry. Returns counts of total, active and delisted entries, how many carry a CAS number, and the edition date. It reports on the data only and cannot tell you whether any product requires a warning.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| active | number | – | Entries currently listed. |
| delisted | number | – | Entries listed and later removed. |
| edition | string | – | Edition date of the OEHHA list. |
| mechanisms | object | – | Listing-mechanism codes and their meanings. |
| status | string | yes | Always ok. |
| total | number | – | Entries in the embedded list, including delisted ones. |
| withCas | number | – | Entries carrying at least one CAS number. |
No examples provided.
list_recent_listings Chemicals added to the list since a year ~125
List the chemicals added to Proposition 65 on or after a given year. Use this to find recent additions, which matters because a warning is generally required twelve months after a chemical is listed, so a new entry starts a compliance clock. Returns active listings only, newest first, with their dates, and reports how many entries carry no parseable date and are therefore missing from the answer. It does not tell you whether any particular product is affected.
| Name | Type | Req | Description |
|---|---|---|---|
| since | number | yes | Four-digit year, from 1986 onwards. Prop 65 listings begin in 1987. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | How many active chemicals were listed on or after that year. |
| edition | string | – | The edition of the list this answer came from. |
| results | array | – | The chemicals, newest first. |
| status | string | yes | Outcome of the lookup. `not_found` is not a clearance. `ambiguous` means the name matched several entries and you should pick one or use a CAS number. |
| undatedEntries | number | – | Active entries with no parseable listing date, absent from this answer. |
No examples provided.
search_prop65 Find listed chemicals by partial name ~155
Search the Proposition 65 list for chemicals whose name contains a fragment. Use this when you do not have an exact name or a CAS number, or to survey a family of related substances. Returns matching chemicals with their CAS numbers, toxicity endpoints, listing dates and delisted flags, capped at a limit with `truncated` set when there were more. It searches names only, so it will not find a chemical listed under a synonym you did not search for, and a result here is not a determination that a warning is required.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum results to return. Defaults to 25. |
| term | string | yes | A fragment of a chemical name, such as 'benz' or 'chromium'. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | How many entries matched in total. |
| edition | string | – | The edition of the list this answer came from. |
| results | array | – | The matching chemicals. |
| status | string | yes | Outcome of the lookup. `not_found` is not a clearance. `ambiguous` means the name matched several entries and you should pick one or use a CAS number. |
| truncated | boolean | – | Whether more matched than were returned. |
No examples provided.