Local MCP servers with a repository URL

What this category does not say

• Execution location is not declared but computed: from Transports (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.
• This category shares 16,720 of its 16,720 entries with "Locally executed MCP servers" (17,666). Both are measured from different original data; that they hit almost the same set is a finding, not a rule.

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 16,720 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&ausfuehrungsort=lokal&quelloffen_einsehbar=true&grenze=200"

The command carries exactly the condition of this page. 16,720 entries at 200 each are 84 requests; 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 16,720 entries
• Subscribe to this category as an Atom feed

https://tracevero.com/aenderungen.atom?thema=lokal-mit-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.