A
licenseA
qualityC
maintenanceProvides accurate, source-grounded breaking-change briefings for npm packages by reading real GitHub release notes and CHANGELOGs, helping coding agents avoid hallucinated dependency migrations.
3
15
MIT
DepFeed
by dev.depfeed
Server Details
Change intelligence for coding agents: sourced breaking changes for npm, PyPI, and Rust packages.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.3/5.0
Tool DescriptionsA
Average 4.7/5 across 19 of 19 tools scored. Lowest: 3.5/5.
Server CoherenceA
Disambiguation5/5
Each tool has a clear, distinct purpose with explicit cross-references to avoid confusion (e.g., check_breaking_changes vs get_api_diff vs plan_upgrade; get_maintenance_status vs get_package_health). The descriptions even clarify when to use one tool over another for overlapping concepts.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (get_, check_, list_, register_, delete_, plan_, submit_). Even the batch variant get_package_updates_batch fits the pattern. Naming is predictable and makes tool purpose evident from the name alone.
Tool Count4/5
19 tools is slightly above the typical well-scoped range, but each tool earns its place for a dependency-intelligence server covering updates, breaking changes, API diffs, compatibility, health, security, webhooks, and planning. The count feels justified rather than bloated.
Completeness4/5
The surface comprehensively covers the dependency lifecycle: checking updates, breaking changes, compatibility, migration, health, vulnerabilities, and webhook subscriptions. Minor gaps exist (e.g., no webhook update tool, no direct 'get package metadata' tool), but these are not critical dead ends.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- FlicenseAqualityAmaintenanceBreaking-change diffs for npm packages, served over REST and MCP, so coding agents stop writing code against outdated API knowledge.2
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to identify exactly what broke between two dependency versions, with citations for every claim, and to verify package existence to catch typosquatting, all without requiring an API key.MIT
- FlicenseNot gradedqualityCmaintenanceProvides structured migration briefs for LLM coding agents covering breaking changes, codemod coverage, and hallucination warnings for major version bumps of packages like tailwindcss, next, and react.