Skip to content
FixedIn logo

FixedIn MCP server

Which MCP servers are FixedIn's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to FixedIn

Whose server it is
  • Registry namedev.fixedin/fixedinverified in the MCP registry

The registry name sits under fixedin.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools3
  • Server calls itselffixedin
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 691 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check whether a software version is vulnerable; find the version that fixes a known vulnerability; check up to fifty versions at once.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • For "check whether a software version is vulnerable", the likely first call is check_version.
  • For "find the version that fixes a known vulnerability", the likely first call is check_version.
  • For "check up to fifty versions at once", the likely first call is check_stack.
  • Parameters are untyped or undescribed in 1 of 3 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer769 ms
  • Space in an agent's context≈ 359 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsA · 94 of 100
  • Typed results3 of 3 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 3

What an agent can do with it

  • can do · check whether a software version is vulnerable
  • can do · find the version that fixes a known vulnerability
  • can do · check up to fifty versions at once

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-29
  • check_version

    Check one product version for known vulnerabilities, active exploitation and end of life, and get the version that fixes it.

  • check_stack

    Check up to 50 product versions, e.g. everything in a Dockerfile, docker-compose.yml or server inventory.

  • list_products

    List the products FixedIn covers, with their newest known release.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "fixedin": {
      "type": "http",
      "url": "https://fixedin.dev/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http fixedin https://fixedin.dev/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://fixedin.dev/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.