Life Scientific product catalogue
REMOTE · LIFESCIENTIFIC.COM
Crop-protection products, active ingredients, approved uses and registrations per country.
Available components
Last scanned (23 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 4 Nov 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 Security80
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 824 tokens (~206/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 Management3
- Stability observed for 1 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 72
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 4 Nov 2026 · Probed https://lifescientific.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lifescientific.com | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | cef6512b1cd19e461314ee6246b23122 |
| SANs: lifescientific.com, www.lifescientific.com, *.www.lifescientific.com | ||||||
| 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 lifescientific.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| lifescientific.com. | 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 |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'self' https://lifescientific.com https://*.lifescientific.com |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lifescientific.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://lifescientific.com/api/mcp | HTTPS enforced | 301 | https://lifescientific.com/api/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 →
check_authorization Check market authorisation ~116
Check whether a product is authorised in a specific market/region and, if so, return its registration status, number, pack sizes and approved uses. Use this to answer "can I use product X in country Y?".
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language for localised prose (taglines, descriptions). Defaults to "en". Regulatory facts are never translated. |
| region | string | yes | ISO alpha-2 market code, e.g. "gb", "ie", "fr". |
| slug | string | yes | Product slug. |
No output schema declared.
No examples provided.
get_product Get product detail ~111
Get the full detail for one product by its slug: active ingredients with resistance-group codes (FRAC/HRAC/IRAC), formulation, key uses, and per-market registrations with approved crop/target uses, PHI, pack sizes and safety summary.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language for localised prose (taglines, descriptions). Defaults to "en". Regulatory facts are never translated. |
| slug | string | yes | Product slug (from search_products), e.g. "spinosad-50". |
No output schema declared.
No examples provided.
get_product_documents Get product documents (label / SDS) ~101
Get the current regulatory documents for a product — the official product label and safety data sheet (SDS) per registered market, with download URLs and versions. Labels are market-specific: always use the document for the market where the product will be applied.
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | – | Optional ISO alpha-2 market code (e.g. "gb", "ie") to fetch one market only. |
| slug | string | yes | Product slug (from search_products). |
No output schema declared.
No examples provided.
search_products Search products ~324
Search the Life Scientific crop-protection catalogue. Filter by free-text query (brand name, tagline, active ingredients, crops and pests), product type, crop, pest/disease/weed target, and/or market/region. Use this for problem-first questions like "what controls septoria in wheat in Ireland?". Returns a compact list of matching products. Pest/disease targets are not yet recorded for every market: if a target search in a market finds nothing, search that market by crop and type instead, and tell the user to confirm the target on the label (get_product_documents). Never conclude that no product controls it.
| Name | Type | Req | Description |
|---|---|---|---|
| crop | string | – | Crop name to match against approved uses (e.g. "wheat", "potatoes"). |
| limit | integer | – | Max results (default 25). |
| locale | string | – | Language for localised prose (taglines, descriptions). Defaults to "en". Regulatory facts are never translated. |
| query | string | – | Free-text search over name, tagline, active ingredients, crops and pests/diseases/weeds. Every word must match, in any order (e.g. "septoria wheat"). Best for pests and diseases. |
| region | string | – | ISO alpha-2 market code to restrict to (e.g. "gb", "ie", "fr"). |
| target | string | – | Pest, disease or weed on an approved use in that market (e.g. "septoria", "black-grass"). Singular or plural. |
| type | string | – | Restrict to one product type. |
No output schema declared.
No examples provided.
How do I install the Life Scientific product catalogue MCP server?
Life Scientific product catalogue is a hosted endpoint at https://lifescientific.com/api/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 · lifescientific.com
claude mcp add --transport http com-lifescientific-products 'https://lifescientific.com/api/mcp'
What is the Life Scientific product catalogue MCP server?
Life Scientific product catalogue is an MCP server listed in the public MCP registry as com.lifescientific/products. Crop-protection products, active ingredients, approved uses and registrations per country. This page covers its hosted endpoint (https://lifescientific.com/api/mcp).
Is the Life Scientific product catalogue MCP server safe to use?
Life Scientific product catalogue scores 73 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 Life Scientific product catalogue MCP server expose?
Life Scientific product catalogue exposes 4 tools: search_products, get_product, check_authorization, get_product_documents. Their descriptions and schemas cost roughly 652 tokens of context every time the server is loaded.
Does the Life Scientific product catalogue MCP server require authentication?
No. We connected to Life Scientific product catalogue without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Life Scientific product catalogue MCP server still maintained?
Life Scientific product catalogue is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.