MCP servers as an npm package only

MCP servers whose manifest declares npm as its only package registry. For them the registry holds a package coordinate from which a start command can be built.

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

• Package registries (raw) is the complete, sorted enumeration of what a manifest declares. So "npm" means exactly that and nothing else: an entry that also declares something different is not in this excerpt.
• This excerpt shares 901 of its 909 entries with "Local MCP servers as an npm package only" (901). 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 909 entries of the excerpt, not to the registry. Shown are 6 of 11 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&roh_paketquellen=npm&grenze=200"

The command carries exactly the condition of this page. 909 entries at 200 each are 5 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 651 to 700 of 909

All 909 entries in the list, with filters and pagination

tracevero · https://tracevero.com/en/themen/paket-npm?seite=14