Developer · Remote MCP server
Fetter MCP
Real-time Python package and vulnerability data for AI coding agents.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.fetter-io/fetter-mcp- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-02-26
- Updated
- 2026-02-26
- Publisher
- fetter-io (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/fetter-io) · how
- Website
- fetter.io/mcp
- Repository
- github.com/fetter-io/fetter-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.fetter.io/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- fetter-mcp 1.0.1 · protocol 2025-03-26
- Tools discovered
- 3:
is_vulnerable,most_recent_not_vulnerable,lookup - Checked on
- 2026-10-05
How to connect Fetter MCP
Fetter MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.fetter.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Ferritin - Rust documentationSearch and read Rust documentation for the standard library and any crate on crates.io. | Remote · HTTPLive check: ✓ handshake |
| FetcherThe web capability layer for AI agents: render, extract, DNS, SSL, WHOIS & more via x402. | Remote · HTTPLive check: ✓ handshake |
| FetchSandboxA deterministic verification engine for agents. Proves a fix: fails on the old code, passes on new. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| FetchV2Fetch and extract web pages, discover links, and read llms.txt documentation indexes. | Local · stdio |
| FettleUptime monitoring for developers - monitors, incidents, heartbeats and status pages. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Figma Context MCPGive your coding agent access to your Figma data. Implement designs in any framework in one-shot. | Local · stdio |
| Figma MCP RustFigma MCP server in Rust: plugin bridge, no API token, no rate limits, 73 tools. | Local · stdio |
| Figma MCP RustFigma MCP server in Rust: plugin bridge, no API token, no rate limits, 73 tools. | Local · stdio |