renfield-mcp-tracking
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DHL_API_KEY | No | DHL Developer Portal app key (the DHL-API-Key). | |
| UPS_CLIENT_ID | No | UPS developer app credentials. | |
| FEDEX_CLIENT_ID | No | FedEx developer app credentials. | |
| UPS_CLIENT_SECRET | No | UPS developer app credentials. | |
| FEDEX_CLIENT_SECRET | No | FedEx developer app credentials. | |
| DHL_TRACKING_BASE_URL | No | Override API base for DHL (test environments). | |
| UPS_TRACKING_BASE_URL | No | Override API base for UPS (test environments). | |
| FEDEX_TRACKING_BASE_URL | No | Override API base for FedEx (test environments). | |
| TRACKING_DEFAULT_CARRIER | No | Fallback when auto-detect is inconclusive (default dhl). |
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 |
|---|---|
| track_parcelA | Track a parcel and return its current status, ETA and event history. Args: tracking_number: The carrier tracking number / piece code. carrier: Carrier code (dhl, ups, fedex, dpd, hermes, gls) or "auto" to detect from the number format. Default "auto". Returns a normalized result with: status (pre_transit / transit / out_for_delivery / delivered / exception / unknown / not_found / link_only / not_configured / error), status_description, estimated_delivery, events (newest first), web_url, and success. |
| list_carriersA | List supported carriers and whether each is configured/usable. 'api' carriers need credentials (configured=False means missing keys). 'link' carriers always work but only return a web tracking link. |
| detect_carrierA | Guess the carrier from a tracking-number format (best effort). Confident only for UPS ('1Z…') and DHL ('JJD…/JD…'). For ambiguous numeric numbers it returns the configured fallback carrier and confident=False. Args: tracking_number: The number to classify. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ebongard/renfield-mcp-tracking'
If you have feedback or need assistance with the MCP directory API, please join our Discord server