MCP servers for email

MCP servers whose description mentions email, a mailbox or a sending service.

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

• Field of use is not declared but computed: from Description (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 515 entries of the excerpt, not to the registry. Shown are 6 of 8 properties: those whose values spread the most inside this excerpt.

The same excerpt through the interface

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

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

• This excerpt as JSON
• This excerpt as CSV

Changes to these entries

• Change stream, narrowed to these 515 entries
• Subscribe to this excerpt as an Atom feed

https://tracevero.com/aenderungen.atom?thema=einsatz-epost

Both addresses narrow the change stream to exactly the entries in this excerpt. The feed carries an identifier of its own, so a feed reader keeps it apart from the full stream.

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 51 to 100 of 515

All 515 entries in the list, with filters and pagination

tracevero · https://tracevero.com/themen/einsatz-epost?seite=2