Identify a server
A line from your config back to its registry entry
How it works
Your configuration holds a start line and you want to know what is behind it. Drop it in here: the registry extracts the package coordinate and looks up the entry.
From the registry, to try out: npx -y i1n
Nothing dropped in yet.
The rules used to extract
The column on the right shows the FORM a rule matches. It is not a suggestion: whether this registry holds the entry named there is a separate question.
| koordinate | A package coordinate in the form this registry itself prints: source, colon, identifier pypi:unraid-mcp |
|---|---|
| purl | A package URL in purl notation pkg:npm/@modelcontextprotocol/server-filesystem |
| npx | A start command using npx, minus its flags npx -y @modelcontextprotocol/server-filesystem |
| uvx | A start command using uvx or pipx run uvx mcp-server-git |
| pip | An install with pip or uv pip pip install mcp-server-git |
| docker | A container image from a docker or podman command docker run -i --rm mcp/everything |
| dnx | A start command using dnx dnx Some.Mcp.Server |
| registername | Two parts separated by a slash - the shape of a registry identifier. The rule describes the shape, not the origin io.github.modelcontextprotocol/servers |
| bezeichner | A bare package name, with or without a scope @modelcontextprotocol/server-filesystem |
| eingebettet | a scoped package name inside the text "args": ["-y", "@modelcontextprotocol/server-filesystem", "/tmp"] |
Version of the extraction rules: 4. The search runs only over the column the source supplied; at most 20 matches per section, with the same publication barrier as the list.
tracevero · https://tracevero.com/werkzeuge/koordinate