io.github.abryfs/willitsend
NPM · WILLITSEND · SCANNED AUG 3
Deterministic pre-send lint for SMS/iMessage: silent carrier filtering and segment blowups.
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 Security83
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects @hono/node-server 1.19.17, reached via @modelcontextprotocol/sdk > @hono/node-server. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), 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 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 823 tokens (~823/item across 1 items; 1 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 Management27
- Stability observed for 8 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · willitsend
claude mcp add abryfs-willitsend -- npx -y willitsend
codex mcp add abryfs-willitsend -- npx -y willitsend
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"abryfs-willitsend": {
"type": "local",
"command": [
"npx",
"-y",
"willitsend"
],
"enabled": true
}
}
} openclaw mcp add abryfs-willitsend --command npx --arg -y --arg willitsend
mcp_servers:
abryfs-willitsend:
command: "npx"
args: ["-y", "willitsend"] {
"mcpServers": {
"abryfs-willitsend": {
"command": "npx",
"args": [
"-y",
"willitsend"
]
}
}
} 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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +47
- GHSA-frvp-7c67-39w9 affects this package: medium ▼ security
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
- 1 Aug 26 −6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 29 Jul 26 +17
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −17
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 41
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-frvp-7c67-39w9 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
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.
preflight_message Preflight a message before sending ~823
Analyzes (lints) a draft SMS/iMessage BEFORE you send it — it sends nothing itself, makes no delivery attempt, and has no side effects. Call this first, before send_message or any other messaging tool, on every outbound draft. Returns: a verdict (pass, warn, block, or needs_context — block-severity issues that depend on context you didn't provide, like whether this is the first message to this contact); a list of findings, each with a severity, a stable rule id, a plain-language explanation, an optional concrete fix, and a citation URL (AgentPhone docs, CTIA, or Twilio guidelines) backing the rule; and a send trace with the destination classification, the assumed delivery channel (imessage/sms/mms/unknown), SMS segment math (encoding, segment count), and — given a 10DLC campaign_type — a daily-quota illustration. Use it to catch carrier-filtering risks (missing opt-out language, missing brand identification, missing opt-in wording on first messages), invalid iMessage send_style values, oversized media carousels, and GSM-7/UCS-2 segment blowups from stray unicode before spending a real send. Every finding's fix field is directly actionable: apply it to the draft verbatim (e.g. append the exact quoted sentence), then call preflight_message again — loop until the verdict is pass. Never treat needs_context as permission to send; supply the missing context and re-check.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The exact message text to preflight. Pass an empty string for a media-only send. This text is used only for local analysis — the tool never stores or forwards it anywhere. |
| brand_name | string | — | Sender brand or company name that should be identifiable in a first message. Without it the brand-identification check degrades to advisory only. |
| campaign_type | string | — | 10DLC campaign tier, if known, to attach a static daily-send-cap illustration to the trace. |
| destination_capabilities | object | — | Known delivery capabilities for the destination, if you already looked them up. Passing this explicitly always takes precedence over — and skips — this server's own optional lookup. |
| destination_line_type | string | — | Destination phone line type, if known from an external lookup. Never guess this from the number itself — VoIP lines often have unreliable iMessage/SMS delivery. |
| is_first_message_to_contact | boolean | — | Whether this is the first outbound message ever sent to this contact. Set true or false when you know it — first messages carry stricter compliance rules (opt-out language, brand identification, opt-… |
| media_urls | array | — | Media attachment URLs. 2-20 entries triggers an iMessage carousel; check the returned findings for carousel-size warnings on other channels. |
| recipients | array | — | 2+ destinations to create a new iMessage group (iMessage only, never delivers as SMS). Do not combine with to_number. |
| reply_to_message_id | string | — | iMessage-only threaded reply target message id. |
| response_format | string | — | Output size. "detailed" (default): full messages, fixes, and citation URLs. "concise": one line per finding (severity, rule, fix), ~10x fewer tokens — same engine, same verdict, everything needed to… |
| send_style | string | — | iMessage-only visual send effect (e.g. "confetti", "slam"). Silently dropped outside iMessage — flagged unless the channel is confirmed iMessage. |
| to_number | string | — | Single destination: E.164 phone number (e.g. +15551234567), email (iMessage only), a 5-6 digit short code, or a grp_ group id. Omit when using `recipients` for a multi-recipient group. |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | — |
| trace | object | yes | — |
| verdict | string | yes | — |
No examples provided.