Fetter MCP
Server Details
Real-time Python package and vulnerability data for AI coding agents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- fetter-io/fetter-mcp
- GitHub Stars
- 1
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
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.
Tool Definition Quality
Average 3.7/5 across 3 of 3 tools scored.
Each tool has a clearly distinct purpose: is_vulnerable checks a specific version for vulnerabilities, lookup provides general package/version information, and most_recent_not_vulnerable finds safe versions. There is no overlap in functionality—an agent can easily distinguish between checking a specific version, exploring available versions, and finding the latest safe version.
The naming is mostly consistent with a clear verb-based pattern (is_vulnerable, lookup, most_recent_not_vulnerable), though most_recent_not_vulnerable uses a descriptive phrase rather than a simple verb_noun format. This minor deviation does not hinder readability or predictability.
With 3 tools, the server is well-scoped for its purpose of package vulnerability checking. Each tool earns its place by covering distinct aspects: specific version checking, general lookup, and safe version discovery. This count is appropriate and avoids bloat or thinness.
The tool surface covers the core workflows for package vulnerability assessment: checking specific versions, exploring packages, and finding safe versions. A minor gap is the lack of bulk operations or historical trend analysis, but agents can work around this with sequential calls for basic use cases.
Available Tools
3 toolsis_vulnerableInspect
Check if a specific package version has known vulnerabilities. Requires an exact version specifier (e.g., 'requests==2.31.0').
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The exact package name and version (e.g., "requests==2.31.0", "numpy==1.24.0"). |
lookupInspect
Look up a package by name and (optionally) version number to find which versions are available and/or have vulnerabilities.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The package name to look up (e.g., "requests", "numpy>=2.0", "flask==3.0.0"). Note that when an exact "==" version is specified, the `limit` and `retain_passing` parameters have no effect. | |
| limit | No | When the name is not an exact version, limit the number of recent versions to check. | |
| cvss_filter | No | CVSS score filter: "all" to show all vulnerabilities, "max" to show only the maximum observed score, or a number (0.0-10.0) to filter by threshold | |
| retain_passing | No | 'When the name is not an exact version, setting this to True will return refernces for all packages, include those with no vulnerabilities (default: false) |
most_recent_not_vulnerableInspect
Find the most recent version of a package that has no known vulnerabilities.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The package name to look up (e.g., "requests", "numpy", "flask"). |
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!