Remote MCP servers with a repository URL

Execution location remote and a listed repository URL. Whether the endpoint code lives there is not stated: the URL is never fetched.

What this excerpt selects

A derived value carries its raw declaration beside it; the derivation rule is published, with a version, on the methodology page.

What this excerpt 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.
• None of this is verified. This registry fetches no repository URL, no endpoint and no package index. What is measured is what a manifest declares, not what a piece of software does.

Every sentence here follows from the condition above, not from an assessment.

How this excerpt is distributed

Per property, the measured values inside this excerpt. The share refers to the 6,497 entries of the excerpt, not to the registry.

The same excerpt through the interface

curl -s "https://tracevero.com/api/v1/eintraege?art=mcp_server&ausfuehrungsort=entfernt&quelloffen_einsehbar=true&grenze=200"

The command carries exactly the condition of this page. 6,497 entries at 200 each are 33 requests; the total is in the X-Gesamt header.

• This excerpt as JSON
• This excerpt as CSV

Excerpts sharing entries with this one

Per neighbour its own size and the counted number of shared entries. An excerpt without a single shared entry is not listed here.

Entries

Entries 2,151 to 2,200 of 6,497

All 6,497 entries in the list, with filters and pagination

tracevero · https://tracevero.com/en/themen/entfernt-mit-repository?seite=44