deprecation-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 |
|---|---|
| check_deprecationA | Look up whether a provider's API or SDK is active, deprecated, or sunset. Covers a curated set of high-traffic providers (Stripe, Twilio, AWS, GitHub, OpenAI, Slack, SendGrid, Shopify, Auth0, PayPal). Returns 'unknown' for anything not tracked. |
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 has a clear, specific purpose: querying deprecation status for known providers.
A single tool name is inherently consistent. 'check_deprecation' follows a clear verb_noun pattern and accurately describes the action.
One tool is slightly below the typical 3-15 range, but it is perfectly suited to the server's narrow purpose of checking deprecation status. The scope does not feel artificially limited.
The core lookup operation is fully covered. A minor gap is the absence of a way to programmatically list supported providers; the agent must rely on the static description to know which providers are tracked.