HimiTrace MCP Server
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_productA | Verify if a product exists on the HimiTrace blockchain and retrieve its basic information including name, origin, owner, and registration date. |
| get_trace_historyA | Get the complete supply chain timeline (events like harvest, process, ship) for a product registered on the Polygon blockchain. |
| get_certificatesA | Get all quality certificates (VietGAP, USDA Organic, Fair Trade) attached to a product, with IPFS download links. |
| get_batch_lineageB | Get the Bill of Materials (BOM) lineage for a batch showing merge/split history of ingredients. |
| check_product_existsA | Quick check if a product ID is registered on the blockchain. Returns boolean status. |
| get_system_statsA | Get overall statistics of the HimiTrace system, including total registered products, wallet balance, and contract info. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| HimiTrace Info | General information about HimiTrace system and capabilities |
| Contract Info | Smart contract and blockchain network information |
| Pricing Info | HimiTrace MCP Server pricing tiers |
TDQS
Scored across 6 tools
Each tool targets a distinct aspect: existence check, basic info, batch lineage, certificates, system stats, and supply chain timeline. No two tools have overlapping purposes.
All tools follow verb_noun pattern in snake_case, but there's a minor inconsistency with 'check_product_exists' vs 'verify_product' both dealing with existence using different verbs.
6 tools is well-scoped for a blockchain traceability domain, covering essential queries without being excessive or insufficient.
Covers main read operations: existence, details, batch lineage, certificates, history, and system stats. Missing write operations like registration or update, but for a query-focused server it's reasonably complete.