Search

Name, task, package or address.

Filter results

Execution locationRequired secrets declaredRepository URL listed

Package, transport and version

Transports (raw)Package registries (raw)Declared version

Option counts apply to this search and the other filters. Transport and package source match the complete declaration, including combinations.

Nothing searched yet.

What the search will find

The search runs over name and identifier, across both sections of the registry, and additionally over the namespaces. Three forms that pay off:

A name or part of a name
A whole namespace – then the set below it is shown first
A complete identifier

Examples from the current directory:

If you are not searching but narrowing down, the selections, the guided chooser and the cross table will take you further.

Search rules and data sources

Find, compare and configure MCP servers. Search by task, name, package, address or a launch command from your configuration file.

The search covers the name, the identifier and the description text. If the input looks like a web address, also the repository URL, the remote endpoints and the homepage. 42,239 of the 42,239 published entries carry a description.

The description text is taken verbatim from the source and is not translated. Measured, it exists in this language: en.

At most 25 matches per section are shown here; the full set is in the list.

Results are ordered by WHERE the search text occurs: a literal match in the name, the identifier or the package coordinate comes first, a match in the namespace alone comes last. Within one step the order is alphabetical, so the same search always returns the same order. Age, adoption and attribute values play no part – the step describes the match, not the entry.

tracevero · https://tracevero.com/suche