laboratory.love
REMOTE · WWW.LABORATORY.LOVE
Lab results for phthalates and bisphenols in consumer products, plus crowdfunded testing.
Available components
Last scanned (16 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Health and Science
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1349 tokens (~149/item across 9 items; 9 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 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.
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 68
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 18 Oct 2026 · Probed https://www.laboratory.love/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=laboratory.love | CN=WE1,O=Google Trust Services,C=US | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | e5f71dd9dbbb3b7413deb8a290a56d4c |
| SANs: laboratory.love, *.laboratory.love | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.laboratory.love. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| love. | present | 27205 | 13 | Verified |
| laboratory.love. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.laboratory.love/mcp | Verified | 200 | |
| http (plaintext) | http://www.laboratory.love/mcp | HTTPS enforced | 301 | https://www.laboratory.love/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 →
create_contribution_checkout Create contribution checkout link ~161
Write (treat as a sensitive, purchase-starting action; confirm the product and amount with the person first). Creates a secure Stripe-hosted checkout link for a contribution toward testing one crowdfunding product. Nothing is charged by this call: the person must open checkout_url and pay. Returns the amount, currency, seller, refund terms, and expiry. Use get_checkout_status to see whether they paid.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | yes | Whole US dollars; must be within the product’s contribution range (minimum $5, or less if less remains). |
| id | string | yes | Crowdfunding product id. |
| idempotency_key | string | – | Optional key; repeating a call with the same key and arguments returns the same checkout instead of a new one. |
No output schema declared.
No examples provided.
create_testing_checkout Create testing order checkout link ~146
Write (treat as a sensitive, purchase-starting action; confirm the tier, price, and product links with the person first). Saves a pending testing order and creates a secure Stripe-hosted checkout link for it. Nothing is charged by this call: the person must open checkout_url and pay. Use get_checkout_status to see whether they paid.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Optional key; repeating a call with the same key and arguments returns the same checkout. |
| products | array | yes | Products to test (at most the tier’s product count), each a public http(s) product page. |
| tier | string | yes | Tier id from list_testing_tiers. |
No output schema declared.
No examples provided.
get_checkout_status Get checkout status ~56
Check whether a checkout created by this connector is awaiting payment, paid, processing, or expired. Report "paid" only when this returns paid. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | string | yes | checkout_id returned by a checkout tool. |
No output schema declared.
No examples provided.
get_crowdfund_status Get crowdfunding status ~59
Get live funding status for one crowdfunding product id: goal, funded, remaining, allowed contribution range, and the result link once tested. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Crowdfunding product id from search_crowdfund. |
No output schema declared.
No examples provided.
get_result Get one test result ~132
Get the full public record for one result id from search_results: provenance, every sample with its lot and analyses, every analyte measurement with its status, LOQ where known, and Laboratory.love’s per-serving exposure ratings with their assumptions. When answering: name the source (commissioned vs PlasticList-derived), keep detected / below_limit_of_quantitation / not_detected / not_tested distinct, give sample counts, and do not call a product safe because values are low or not detected. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Result id such as "cf-116" or "pl-72". |
No output schema declared.
No examples provided.
list_analytes List analytes ~65
List the chemicals Laboratory.love reports (abbreviations such as DEHP, DBP, BPA, BPS), their categories, lab panels, and how each feeds the exposure ratings. Use it to explain abbreviations or to pick an analyte filter. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_testing_tiers List testing tiers ~48
List the direct testing packages a person can buy to have Laboratory.love test products they choose: price, number of products, samples, panels, turnaround, and refund terms. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_crowdfund Search crowdfunding products ~95
List products the public can fund toward laboratory testing, with goal, amount funded, amount remaining, and status. Defaults to products currently accepting contributions. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from a previous call with the same filters. |
| limit | integer | – | – |
| q | string | – | Words to match in the product name or brand. |
| status | string | – | Defaults to accepting_contributions. |
No output schema declared.
No examples provided.
search_results Search published test results ~364
Search Laboratory.love’s published product-test records. Use this before answering whether a product, brand, or category has been tested. Records are either Laboratory.love-commissioned tests or clearly labeled PlasticList-derived historical records; report which. Results describe the samples tested, not every unit of a product. Covers chemicals that come from plastics (phthalates, BPA and other bisphenols, and phthalate substitutes), the usual meaning of "plastic chemicals" in food; it does not measure microplastic particles, so say so if someone asks about microplastics. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| analyte | string | – | Analyte abbreviation or name from list_analytes, e.g. DEHP or BPA. Keeps only results where it was measured. |
| brand | string | – | Brand words. PlasticList records have no separate brand field, so this also matches their product name. |
| category | string | – | Category slug. |
| cursor | string | – | next_cursor from a previous call with the same filters. |
| detected | boolean | – | With analyte: true keeps results where that analyte was detected in at least one sample; false keeps results where it was measured but never detected. Without analyte: any analyte. |
| limit | integer | – | – |
| q | string | – | Words to match in the product name, brand, category, or tags, e.g. "Coca-Cola Zero" or "tofu". |
| sort | string | – | Defaults to relevance when q is given, otherwise tested_on_desc. |
| source | string | – | Only commissioned (Laboratory.love-commissioned) or plasticlist_derived records. |
| tag | string | – | A PlasticList source tag such as "sodas" or "baby_food". |
No output schema declared.
No examples provided.
How do I install the laboratory.love MCP server?
laboratory.love is a hosted endpoint at https://www.laboratory.love/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.laboratory.love
claude mcp add --transport http love-laboratory-laboratory-love 'https://www.laboratory.love/mcp'
What is the laboratory.love MCP server?
laboratory.love is an MCP server listed in the public MCP registry as love.laboratory/laboratory-love. Lab results for phthalates and bisphenols in consumer products, plus crowdfunded testing. This page covers its hosted endpoint (https://www.laboratory.love/mcp).
Is the laboratory.love MCP server safe to use?
laboratory.love scores 71 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 laboratory.love MCP server expose?
laboratory.love exposes 9 tools: search_results, get_result, list_analytes, search_crowdfund, get_crowdfund_status, and 4 more. Their descriptions and schemas cost roughly 1,126 tokens of context every time the server is loaded.
Does the laboratory.love MCP server require authentication?
No. We connected to laboratory.love without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the laboratory.love MCP server still maintained?
laboratory.love is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.