SYD MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SYD_API_KEY | Yes | Your SYD API key | |
| SYD_API_URL | No | API endpoint (defaults to https://api.syd.io/v1/mcp) |
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 |
|---|---|
| get_batch_statusA | Returns the SYD Digital Twin (status, traceability, compliance) for a batch ID. |
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 1 tool
With only one tool, there is no possibility of confusion. The tool's purpose is clearly defined via its name and description.
The tool name follows a conventional verb_noun pattern (get_batch_status). As the only tool, naming consistency is trivially maintained.
At one tool, the server feels underdeveloped for a general-purpose MCP server. However, if the intended scope is limited to batch status retrieval, the count may be justified, though it remains borderline.
The tool aggregates status, traceability, and compliance into a single response, covering the immediate needs for batch information. Yet, the absence of related operations like listing batches or updating status creates notable gaps for a broader workflow.