scern-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| evaluate_productA | Evaluate a product's health score, ingredient safety, corporate ownership, and regulatory flags using the Scern database. Pass a UPC or EAN barcode value. |
| compare_productsA | Compare 2–5 products by health score. Returns all evaluations, a ranking by health score (descending), and the best-scoring barcode. Products not found are included as { value, status: 'not_found' } and excluded from the ranking. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one evaluates a single product, the other compares multiple products. There is no ambiguity between them.
Both tools follow the consistent verb_noun pattern: evaluate_product and compare_products. The naming is predictable and clear.
With only 2 tools, the surface feels thin even for a focused purpose. While it covers the core functions, additional tools like search or product details would round it out.
The tools cover evaluation and comparison, but are missing basic operations like retrieving a product's full details without evaluation or searching by name. The set is minimally functional.