MCP servers for version control without a repository URL
Of the 428 MCP servers in the measured field of use Version control, the registry lists no repository URL for 51 – markedly fewer than the 96 the comparison group would lead one to expect.
51 servers 0.2% of 26,983 in the directory
This category in numbers
- 39 76 % Delivery form (raw): remote
- 40 78 % Execution location: remote
- 41 80 % Schema version of the raw record (raw): https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json
- 41 80 % Required secrets declared: no
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
- recently updated first
Entries 51 to 51 of 51
| searchcode | com.searchcode/mcp |
|---|
All 51 entries in the list, with filters and pagination
What this category selects
| Field of use, derived from the vendor description | Version control derived from: Description (raw) |
|---|---|
| Repository URL listed | no derived from: Repository (raw) |
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
- 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
Delivery form (raw)
51| remote | 39 76 % |
|---|---|
| package | 11 22 % |
| neither | 1 2.0 % |
Execution location
51| remote | 40 78 % |
|---|---|
| local | 11 22 % |
Schema version of the raw record (raw)
51| https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json | 41 80 % |
|---|---|
| https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json | 4 7.8 % |
| https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json | 3 5.9 % |
| https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json | 3 5.9 % |
Required secrets declared
51| no | 41 80 % |
|---|---|
| yes | 10 20 % |
Icon formats (raw)
51| nothing declared | 48 94 % |
|---|---|
| image/png | 1 2.0 % |
| image/png, image/svg+xml | 1 2.0 % |
| image/svg+xml | 1 2.0 % |
Per property, the measured values inside this category. The share refers to the 51 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=versionsverwaltung&quelloffen_einsehbar=false&grenze=200"
The command carries exactly the condition of this page. 51 entries at 200 each are a single request; the total is in the X-Gesamt header.
Changes to these entries
https://tracevero.com/aenderungen.atom?thema=einsatz-versionsverwaltung-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.
Categories sharing entries with this one
Per neighbour its own size and the counted number of shared entries. An category without a single shared entry is not listed here.
tracevero · https://tracevero.com/themen/einsatz-versionsverwaltung-ohne-repository?seite=2