io.github.richelo/isitdisposable-mcp
NPM · ISITDISPOSABLE-MCP · SCANNED AUG 7
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 →
Supply Chain Security96
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 94 of 98 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 94 of 98 dependencies we could resolve, so this covers what we could see, not the whole tree. 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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- 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 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · isitdisposable-mcp
claude mcp add richelo-isitdisposable-mcp -- npx -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": {
"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.
- 6 Aug 26 +38
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Dependency health: unverified → partial ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- 5 Aug 26 28
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 7 Aug 2026 · Analysed npm/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Deprecated | 4 |
| Stale | 29 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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 [email protected]. |
No output schema declared.
No examples provided.