MCP servers for infrastructure without a repository URL

What this category does not say

• Field of use, derived from the vendor description is not declared but computed: from Description (raw). The rule is published, with a version, on the methodology page.
• Repository URL listed is not declared but computed: from Repository (raw). The rule is published, with a version, on the methodology page.

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

Per property, the measured values inside this category. The share refers to the 41 entries of the category, not to the registry.

The same category through the interface

curl -s "https://api.tracevero.com/v1/eintraege?art=mcp_server&einsatzgebiet=infrastruktur&quelloffen_einsehbar=false&grenze=200"

The command carries exactly the condition of this page. 41 entries at 200 each are a single request; the total is in the X-Gesamt header.

• This category as JSON
• This category as CSV

Changes to these entries

• Change stream, narrowed to these 41 entries
• Subscribe to this category as an Atom feed

https://tracevero.com/aenderungen.atom?thema=einsatz-infrastruktur-ohne-repository

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.