Remotely executed MCP servers

MCP servers for which the registry lists only remotes or HTTP transports. The rule behind this is published, with a version, on the methodology page.

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.
• This excerpt shares 5,223 of its 5,239 entries with "MCP servers without a declared package registry" (5,255). Both are measured from different raw declarations; that they hit almost the same set is a finding, not a rule.
• 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 5,239 entries of the excerpt, not to the registry. Shown are 6 of 7 properties: those whose values spread the most inside this excerpt.

The same excerpt through the interface

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

The command carries exactly the condition of this page. 5,239 entries at 200 each are 27 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 901 to 950 of 5,239

All 5,239 entries in the list, with filters and pagination

tracevero · https://tracevero.com/en/themen/entfernt?seite=19