Suparch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Alternative environment variable for HTTP port; same as SUPARCH_PORT. | |
| SUPARCH_HOST | No | HTTP bind host for streamable-http or SSE transport. | |
| SUPARCH_PORT | No | HTTP port for streamable-http or SSE transport. | |
| SUPARCH_DB_PATH | No | Path to a read-only SQLite catalog file. | |
| SUPARCH_MCP_PATH | No | Streamable HTTP endpoint path; default /mcp. | |
| SUPARCH_TRANSPORT | No | Transport protocol: stdio, sse, or streamable-http. | |
| SUPARCH_CATALOG_URL | No | HTTPS URL to an SQLite catalog artifact downloaded on startup. | |
| SUPARCH_CATALOG_SHA256 | No | Optional artifact checksum for SUPARCH_CATALOG_URL. | |
| SUPARCH_CATALOG_CACHE_PATH | No | Download destination for catalog artifact; default /tmp/suparch/catalog.sqlite. | |
| SUPARCH_CATALOG_POINTER_URL | No | URL to an official pointer containing an immutable catalog URL and SHA-256. | |
| SUPARCH_CATALOG_MANIFEST_URL | No | Optional custom manifest URL; defaults to <catalog URL>.manifest.json. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsC | Search supplement labels using objective product and ingredient filters. |
| get_productB | Return one complete normalized supplement label record. |
| get_catalog_infoA | Return catalog version, product count, and snapshot metadata. |
| compare_productsA | Compare per-serving label facts across two or more products. |
| calculate_stackB | Sum known label amounts for a user-supplied product and serving combination. |
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 5 tools
Each tool has a clearly distinct purpose: searching, retrieving a single product, accessing catalog metadata, comparing multiple products, and calculating aggregated amounts. There is no overlap between these operations.
All tool names follow a consistent verb_noun pattern (search_products, get_product, get_catalog_info, compare_products, calculate_stack). The convention is uniform and predictable.
With 5 tools, the server is well-scoped for its purpose of accessing and analyzing supplement label data. Each tool serves a distinct function without redundancy or bloat.
The tool set covers the full range of expected operations for a read-only supplement label API: discovery, retrieval, metadata, comparison, and aggregation. No critical gaps are apparent for the stated domain.