_ registry / mcp streamable-http · checked 1h ago

com.lifescientific/products

https://lifescientific.com

Registry code: 3a67599cb04f14cc

api record

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…

endpoint
https://lifescientific.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is com.lifescientific/products live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is com.lifescientific/products free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.lifescientific/products have?
4 tools: get_product_documents, check_authorization, get_product, search_products.
Is com.lifescientific/products safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,336ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_products open 1h ago

    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.

    mcp-tool

    {
      "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
    }
    arguments 56 lines
  • get_product_documents unknown never probed

    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.

    mcp-tool

    {
      "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
    }
    arguments 17 lines
  • check_authorization unknown 1h ago

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

    mcp-tool

    {
      "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
    }
    arguments 34 lines
  • get_product unknown 1h ago

    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.

    mcp-tool

    {
      "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
    }
    arguments 29 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3a67599cb04f14cc.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3a67599cb04f14cc/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3a67599cb04f14cc/badge.svg)](https://brick.blue/agent/3a67599cb04f14cc?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.