Mcpdeprecation MCP

What mcpdeprecation-mcp does

The mcpdeprecation-mcp MCP server supports workflows around MCP tool deprecation. It is hosted at https://mcpdeprecation.clauxel.com/mcp and is documented as a remote service rather than a package containing deployable production source code.

Its documented audience includes AI product teams, operations leads, workflow owners, and technical evaluators. The service is intended for cases where a team needs to examine whether a tool is deprecated, identify a possible replacement, create evidence for a deprecation event, maintain tool registry information, or export a record of deprecation activity.

The repository describes structured tool-call output, receipt-oriented evidence export, and audit logs as part of the service. It also publishes a server card and registry metadata for discovery and evaluation.

How it works

Clients connect to the streamable HTTP MCP endpoint rather than launching a local process from this repository. Production calls use bearer-token access. After connecting, an MCP client can invoke the server’s five documented tools:

• check_tool_deprecation
• suggest_replacement_tool
• issue_deprecation_receipt
• sync_tool_registry
• export_deprecation_log

The names indicate the workflow areas covered by the endpoint: inspecting deprecation status, finding a replacement, creating a receipt, updating registry state, and exporting a log. The supplied documentation does not specify the input schemas, response fields, receipt format, registry source, or replacement-selection rules, so those details should be verified through the service documentation or server metadata before implementation.

Setup and configuration

Use an MCP client that supports streamable HTTP, configure the endpoint as https://mcpdeprecation.clauxel.com/mcp, and provide the bearer-token credentials required for production access. The repository does not document a required environment-variable name, local installation command, package manager, or self-hosting procedure.

The project publishes a server card at https://mcpdeprecation.clauxel.com/server-card.json and lists the registry name as com.clauxel.mcpdeprecation/mcpdeprecation-mcp. These resources can help with client configuration or registry-oriented evaluation.

Limitations and notes

The mcpdeprecation-mcp MCP server’s public repository is a documentation project. It explicitly does not include production source code, credentials, payment configuration, Cloudflare configuration, customer records, private analytics, or local machine paths.

The provided material does not state whether the service can be run locally, which pricing tier is required, how long logs or receipts are retained, or which external tool registry it synchronizes. It also does not provide a detailed security model, request examples, or per-tool schemas in the supplied excerpt. Review the linked quickstart, evaluation, workflow, security, and pricing materials before relying on it in a production process.