Sendermap
PYPI · SENDERMAP
Maps every service that sends email as a domain, with the public record behind each one.
Available components
Last scanned (18 hours ago)
Scores higher than 81% of PyPI servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 13 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to marmot7775/sendermap). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 875 tokens (~218/item across 4 items; 2 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 81
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Analysed pypi/sendermap@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | marmot7775/sendermap |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/marmot7775/sendermap/.github/workflows/publish.yml@refs/tags/v0.1.2 |
| Rekor log index | 3259432337 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:223b28a01ab08d84a9abb777f95fa118e509c3cd81540bd2b988cee1a548e32f |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 13 packages
| Packages resolved | 13 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sendermap_map Map a domain's email senders ~302
Maps the services that send email as a domain from public records (DNS, certificate logs and the domain's homepage), each with a tier, the record that shows it and the vendor's documented setup. Use it to find who sends mail as a domain, or, with claimed, to hold the services the domain's owner says they use against what the records show. domain is the domain to map; claimed is the service names the owner gave; website reads the homepage and subprocessor page; subdomains searches for sending subdomains (email, mg and the like); certificate_log also reads crt.sh and resolves every logged name, which is slow; detail is summary (each service's deciding claim and setups) or full (every claim, and what was asked at each name). It does not return sending volume, reputation or proof that a DKIM key is in use, and a service it does not show may sit behind one of the gaps it lists.
| Name | Type | Req | Description |
|---|---|---|---|
| certificate_log | boolean | – | Also read crt.sh and resolve every logged name. Slow. |
| claimed | array | – | Service names the domain's owner says they use. |
| detail | string | – | summary: each service's deciding claim. full: everything. |
| domain | string | yes | The domain to map, such as example.com. |
| subdomains | boolean | – | Search for sending subdomains, such as email and mg. |
| website | boolean | – | Read the homepage and subprocessor page. |
| Name | Type | Req | Description |
|---|---|---|---|
| absences | array | – | Questions answered with 'not there'. |
| checked | array | – | What was asked at each name. |
| ct | object | – | How the certificate transparency source went. |
| domain | string | yes | The domain mapped, cleaned to its ASCII form. |
| findings | array | yes | What needs attention, risks first. |
| gaps | array | yes | Questions that got no usable answer. |
| historical | array | – | Possible past vendors from certificate logs. |
| logo | string|null | – | The BIMI logo's URL, if the domain publishes one. Not evidence. |
| reconciliation | – | – | The client's list of services against the map; null, or left out, when nothing was claimed. |
| run | object | yes | When and how the map was made. Two runs over the same DNS answers differ here only. |
| schema | – | yes | The contract this map keeps. |
| services | array | yes | The services found, strongest first; reporting services last. |
| story | string | – | One paragraph written by rules from the map itself. |
| subdomains_checked | array | – | The sending subdomains mapped. |
| unknowns | array | yes | Senders no service in the vendor data matches. |
No examples provided.
sendermap_vendor Show a vendor's patterns and setup ~163
Returns one vendor's block from Sendermap's vendor data as JSON: its category, aliases, every pattern Sendermap recognises it by (SPF includes, MX hosts, DKIM selectors and CNAMEs, bounce and tracking hosts, tokens, networks and the rest), each with the live record that proves it, its documented setup and its sending address. Use it to see why a map credited a service, or which records a vendor's setup asks for. name is the vendor's name or one of its aliases, matched exactly once case, spaces and punctuation are dropped. It looks nothing up for any domain and says nothing about sending volume or who uses the vendor.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A vendor's name or alias, such as Office 365. |
No output schema declared.
No examples provided.
How do I install the Sendermap MCP server?
Sendermap runs locally as a PyPI package, launched with uvx sendermap. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · sendermap
claude mcp add marmot7775-sendermap -- uvx sendermap
What is the Sendermap MCP server?
Sendermap is an MCP server listed in the public MCP registry as io.github.marmot7775/sendermap. Maps every service that sends email as a domain, with the public record behind each one. This page covers its PyPI package (sendermap).
Is the Sendermap MCP server safe to use?
Sendermap scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sendermap MCP server expose?
Sendermap exposes 2 tools: sendermap_map, sendermap_vendor. Their descriptions and schemas cost roughly 465 tokens of context every time the server is loaded.
Is the Sendermap MCP server still maintained?
Sendermap is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Sendermap MCP server under?
Sendermap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.