Koskamo

Life Scientific MCP

An official MCP server operated by Life Scientific that provides read-only access to their crop-protection product catalogue. It enables AI agents to search for products by crop, pest, or market; retrieve detailed formulation and registration data; check authorization status; and access official labels and safety data sheets.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Life Scientific MCP logo, by Life ScientificVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by Life Scientific
MCP endpoint (Streamable HTTP)
https://lifescientific.com/api/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (4)

4 of 4 have a description · 4 of 4 declare behavior hints · 4 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to lifescientific.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search for products by crop, pest, or market
  • Get product formulation and registration details
  • Check product authorization in specific countries
  • Retrieve official labels and safety data sheets

Source and maintenance

Vendor evidenceRegistry 0.2.0
mcp-registry: com.lifescientific/products@0.2.0Project website

Protocol and capabilities

Server
com.lifescientific/products 0.2.0
MCP protocol negotiated in check
2025-11-25
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Query the Life Scientific crop-protection catalogue directly — no API key required. Start with search_products to find a product by crop, target pest/disease, product type or market; call get_product for its full formulation, active ingredients (with FRAC/HRAC/IRAC resistance-group codes) and per-market registrations; check_authorization to confirm a product is approved for use in a specific market; and get_product_documents for the official label and safety data sheet. Pass a locale (en, es, fr, de, it, nl, pt, pl, ro, uk) to receive taglines and descriptions in that language — regulatory facts such as registration numbers, dose rates and pre-harvest intervals are authoritative and returned untranslated. Registration numbers, dose rates, PHI and resistance-group codes are authoritative facts and are not translated.

Tools

4 advertised

search_products — Search products
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

search_products input schema
{
  "type": "object",
  "properties": {
    "crop": {
      "type": "string",
      "description": "Crop name to match against approved uses (e.g. \"wheat\", \"potatoes\")."
    },
    "type": {
      "enum": [
        "insecticide",
        "herbicide",
        "fungicide",
        "fertilizer",
        "growth-regulator",
        "other"
      ],
      "type": "string",
      "description": "Restrict to one product type."
    },
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Max results (default 25)."
    },
    "query": {
      "type": "string",
      "description": "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."
    },
    "locale": {
      "enum": [
        "en",
        "es",
        "fr",
        "de",
        "it",
        "nl",
        "pt",
        "pl",
        "ro",
        "uk"
      ],
      "type": "string",
      "description": "Language for localised prose (taglines, descriptions). Defaults to \"en\". Regulatory facts are never translated."
    },
    "region": {
      "type": "string",
      "description": "ISO alpha-2 market code to restrict to (e.g. \"gb\", \"ie\", \"fr\")."
    },
    "target": {
      "type": "string",
      "description": "Pest, disease or weed on an approved use in that market (e.g. \"septoria\", \"black-grass\"). Singular or plural."
    }
  },
  "additionalProperties": false
}
search_products annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
get_product — Get product detail
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_product input schema
{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Product slug (from search_products), e.g. \"spinosad-50\"."
    },
    "locale": {
      "enum": [
        "en",
        "es",
        "fr",
        "de",
        "it",
        "nl",
        "pt",
        "pl",
        "ro",
        "uk"
      ],
      "type": "string",
      "description": "Language for localised prose (taglines, descriptions). Defaults to \"en\". Regulatory facts are never translated."
    }
  },
  "additionalProperties": false
}
get_product annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
check_authorization — Check market authorisation
Advertised by the server during the last successful anonymous check.
Advertised read-only

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?".

check_authorization input schema
{
  "type": "object",
  "required": [
    "slug",
    "region"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Product slug."
    },
    "locale": {
      "enum": [
        "en",
        "es",
        "fr",
        "de",
        "it",
        "nl",
        "pt",
        "pl",
        "ro",
        "uk"
      ],
      "type": "string",
      "description": "Language for localised prose (taglines, descriptions). Defaults to \"en\". Regulatory facts are never translated."
    },
    "region": {
      "type": "string",
      "description": "ISO alpha-2 market code, e.g. \"gb\", \"ie\", \"fr\"."
    }
  },
  "additionalProperties": false
}
check_authorization annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
get_product_documents — Get product documents (label / SDS)
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_product_documents input schema
{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Product slug (from search_products)."
    },
    "region": {
      "type": "string",
      "description": "Optional ISO alpha-2 market code (e.g. \"gb\", \"ie\") to fetch one market only."
    }
  },
  "additionalProperties": false
}
get_product_documents annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
2543 ms
95th percentile latency
2543 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 2543 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http life-scientific-mcp https://lifescientific.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add life-scientific-mcp --url https://lifescientific.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable life-scientific-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "life-scientific-mcp": {
      "url": "https://lifescientific.com/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "life-scientific-mcp": {
      "type": "streamableHttp",
      "url": "https://lifescientific.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start life-scientific-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "life-scientific-mcp": {
      "type": "http",
      "url": "https://lifescientific.com/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http life-scientific-mcp https://lifescientific.com/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://lifescientific.com/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "life-scientific-mcp": {
      "serverUrl": "https://lifescientific.com/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Life Scientific MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 6,206

Do you run Life Scientific MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing