Proposition 65
REMOTE · PROP65.TOOLSTOP.DEV · 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 against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 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 Management10
- Stability observed for 3 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · prop65.toolstop.dev
claude mcp add --transport http dev-toolstop-prop65 https://prop65.toolstop.dev/
[mcp_servers.dev-toolstop-prop65] url = "https://prop65.toolstop.dev/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-toolstop-prop65": {
"type": "remote",
"url": "https://prop65.toolstop.dev/",
"enabled": true
}
}
} openclaw mcp add dev-toolstop-prop65 --url https://prop65.toolstop.dev/ --transport streamable-http
mcp_servers:
dev-toolstop-prop65:
url: "https://prop65.toolstop.dev/" {
"mcpServers": {
"dev-toolstop-prop65": {
"type": "http",
"url": "https://prop65.toolstop.dev/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 14 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 11 Aug 26 55
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 · Probed https://prop65.toolstop.dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=toolstop.dev | CN=WE1,O=Google Trust Services,C=US | 11 Aug 2026 | 9 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 3224be7337ba91a70e99bc8f3f6eaea3 |
| SANs: toolstop.dev, prop65.toolstop.dev, *.prop65.toolstop.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of prop65.toolstop.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| toolstop.dev. | absent | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://prop65.toolstop.dev | Verified | 200 | |
| http (plaintext) | http://prop65.toolstop.dev | 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.
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.