MCP servers with uvx as their only runtime hint
The manifest names uvx and nothing else as the way to run the package. The category is small and stands here because the registry measures it.
1,568 servers 3.7% of 41,867 in the directory
This category in numbers
- 1,261 80 % Required secrets declared: no
- 1,446 92 % Path argument present: no
- 1,431 91 % Delivery form (raw): package
- 1,511 96 % Icon formats (raw): nothing declared
The most frequent value per property, counted across the entries of this category. The full distribution is further down.
Entries
Filter further
- Execution location: local
- Execution location: remote
- Required secrets declared: no
- Required secrets declared: yes
- Repository URL listed: yes
- Repository URL listed: no
- recently updated first
Entries 1,251 to 1,300 of 1,568
All 1,568 entries in the list, with filters and pagination
What this category selects
| Runtime hints (raw) | uvx measured directly |
|---|
A derived value carries its original data beside it; the derivation rule is published, with a version, on the methodology page.
Caveats, distribution and query
What this category does not say
- Runtime hints (raw) is the complete, sorted enumeration of what a manifest declares. So "uvx" means exactly that and nothing else: an entry that also declares something different is not in this category.
What is measured is what a manifest declares, not what a piece of software does. This registry fetches no repository URL, no endpoint and no package index; nothing here is verified. Which value comes from which source, and by which rule it was formed, is set out in the Methodology.
Every sentence here follows from the condition above, not from an assessment.
How this category is distributed
Required secrets declared
1,568| no | 1,261 80 % |
|---|---|
| yes | 307 20 % |
Delivery form (raw)
1,568| package | 1,431 91 % |
|---|---|
| package and remote | 137 8.7 % |
Path argument present
1,568| no | 1,446 92 % |
|---|---|
| yes | 122 7.8 % |
Schema version of the raw record (raw)
1,568| https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json | 1,500 96 % |
|---|---|
| https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json | 44 2.8 % |
| https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json | 18 1.1 % |
| https://static.modelcontextprotocol.io/schemas/2025-09-16/server.schema.json | 4 0.3 % |
| https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json | 2 0.1 % |
Icon formats (raw)
1,568| nothing declared | 1,511 96 % |
|---|---|
| image/png | 35 2.2 % |
| image/svg+xml | 13 0.8 % |
| image/png, image/svg+xml | 8 0.5 % |
| image/jpeg | 1 0.1 % |
Repository platform (raw)
1,568| github | 1,517 97 % |
|---|---|
| nothing declared | 47 3.0 % |
| gitlab | 4 0.3 % |
Per property, the measured values inside this category. The share refers to the 1,568 entries of the category, not to the registry. Shown are 6 of 8 properties: those whose values spread the most inside this category.
The same category through the interface
curl -s "https://api.tracevero.com/v1/eintraege?art=mcp_server&roh_laufzeithinweise=uvx&grenze=200"
The command carries exactly the condition of this page. 1,568 entries at 200 each are 8 requests; the total is in the X-Gesamt header.
Changes to these entries
https://tracevero.com/aenderungen.atom?thema=laufzeit-uvx
Both addresses narrow the change stream to exactly the entries in this category. The feed carries an identifier of its own, so a feed reader keeps it apart from the full stream.
Categories sharing entries with this one
Per neighbour its own size and the counted number of shared entries. A category without a single shared entry is not listed here.
tracevero · https://tracevero.com/themen/laufzeit-uvx?seite=26