io.github.richelo/isitdisposable-mcp
NPM · ISITDISPOSABLE-MCP · SCANNED OCT 1
An MCP server that lets AI agents check whether an email address or domain is disposable.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 56 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 907 tokens (~302/item across 3 items; 3 tools + 0 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.richelo/isitdisposable-mcp server?
io.github.richelo/isitdisposable-mcp runs locally as an npm package, launched with npx -y isitdisposable-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · isitdisposable-mcp
claude mcp add richelo-isitdisposable-mcp -- npx -y isitdisposable-mcp
{
"mcpServers": {
"richelo-isitdisposable-mcp": {
"command": "npx",
"args": [
"-y",
"isitdisposable-mcp"
]
}
}
} {
"servers": {
"richelo-isitdisposable-mcp": {
"command": "npx",
"args": [
"-y",
"isitdisposable-mcp"
]
}
}
} codex mcp add richelo-isitdisposable-mcp -- npx -y isitdisposable-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"richelo-isitdisposable-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"isitdisposable-mcp"
],
"enabled": true
}
}
} openclaw mcp add richelo-isitdisposable-mcp --command npx --arg -y --arg isitdisposable-mcp
mcp_servers:
richelo-isitdisposable-mcp:
command: "npx"
args: ["-y", "isitdisposable-mcp"] {
"McpServers": {
"richelo-isitdisposable-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"isitdisposable-mcp"
]
}
}
} assistant mcp add richelo-isitdisposable-mcp -t stdio -c npx -a -y isitdisposable-mcp
{
"mcpServers": {
"richelo-isitdisposable-mcp": {
"command": "npx",
"args": [
"-y",
"isitdisposable-mcp"
]
}
}
} 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.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Sept 26 −3
- Stability: pass → 0.80 functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 1 Oct 2026 · Analysed npm/isitdisposable-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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 →
check_batch Check a batch of emails and domains for disposable ~343
Checks up to 100 email addresses or domains at once in a single call, which is far more efficient than calling the single-item tools in a loop. Provide a mixed list in `items`: entries containing an @ sign are sent as email addresses, and all other entries are sent as bare domains. A disposable address is a throwaway or temporary inbox (for example from a burner mail service) that someone uses to receive a single signup message and evade normal registration requirements, rather than a real, ongoing mailbox. In the response, `disposable` is the core true or false verdict. `action` is the recommended handling: `allow`, `warn`, or `block`, based on the caller's own account policy. Extra opt in signals may also be present: `mx_valid` (whether the domain's mail servers accept mail at all), `relay` (a forwarding or catch all style address rather than a dedicated inbox), `public_domain` (a well known free provider such as Gmail or Outlook), and `did_you_mean` (a likely intended domain when the one given looks like a typo). This tool always fails open: if a network problem, timeout, rate limit, or server error prevents a real check, the call still succeeds and returns `checked` false with `action` allow, plus a `note` explaining the check could not be completed. Treat that outcome as inconclusive, never as evidence the address is safe.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 1 to 100 entries, each either a full email address or a bare domain. Entries containing an @ sign are checked as email addresses; all other entries are checked as bare domains. |
No output schema declared.
No examples provided.
check_domain Check domain for disposable ~294
Checks a single bare domain (no local part, for example when only a company's domain is known and not a specific address) to see whether it is disposable. A disposable address is a throwaway or temporary inbox (for example from a burner mail service) that someone uses to receive a single signup message and evade normal registration requirements, rather than a real, ongoing mailbox. In the response, `disposable` is the core true or false verdict. `action` is the recommended handling: `allow`, `warn`, or `block`, based on the caller's own account policy. Extra opt in signals may also be present: `mx_valid` (whether the domain's mail servers accept mail at all), `relay` (a forwarding or catch all style address rather than a dedicated inbox), `public_domain` (a well known free provider such as Gmail or Outlook), and `did_you_mean` (a likely intended domain when the one given looks like a typo). This tool always fails open: if a network problem, timeout, rate limit, or server error prevents a real check, the call still succeeds and returns `checked` false with `action` allow, plus a `note` explaining the check could not be completed. Treat that outcome as inconclusive, never as evidence the address is safe.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A bare domain with no local part and no @ sign, for example example.com. |
No output schema declared.
No examples provided.
check_email Check email for disposable ~270
Checks a single email address to see whether it is disposable. A disposable address is a throwaway or temporary inbox (for example from a burner mail service) that someone uses to receive a single signup message and evade normal registration requirements, rather than a real, ongoing mailbox. In the response, `disposable` is the core true or false verdict. `action` is the recommended handling: `allow`, `warn`, or `block`, based on the caller's own account policy. Extra opt in signals may also be present: `mx_valid` (whether the domain's mail servers accept mail at all), `relay` (a forwarding or catch all style address rather than a dedicated inbox), `public_domain` (a well known free provider such as Gmail or Outlook), and `did_you_mean` (a likely intended domain when the one given looks like a typo). This tool always fails open: if a network problem, timeout, rate limit, or server error prevents a real check, the call still succeeds and returns `checked` false with `action` allow, plus a `note` explaining the check could not be completed. Treat that outcome as inconclusive, never as evidence the address is safe.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The full email address to check, for example someone@example.com. |
No output schema declared.
No examples provided.
What is the io.github.richelo/isitdisposable-mcp server?
io.github.richelo/isitdisposable-mcp is listed in the public MCP registry as io.github.richelo/isitdisposable-mcp. An MCP server that lets AI agents check whether an email address or domain is disposable. This page covers its npm package (isitdisposable-mcp).
Is the io.github.richelo/isitdisposable-mcp server safe to use?
io.github.richelo/isitdisposable-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. It declares no install or post-install scripts. 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 io.github.richelo/isitdisposable-mcp server expose?
io.github.richelo/isitdisposable-mcp exposes 3 tools: check_email, check_domain, check_batch. Their descriptions and schemas cost roughly 907 tokens of context every time the server is loaded.
Is the io.github.richelo/isitdisposable-mcp server still maintained?
io.github.richelo/isitdisposable-mcp is still listed as active in the MCP registry. We last reached this channel on 1 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 io.github.richelo/isitdisposable-mcp server under?
io.github.richelo/isitdisposable-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.