# io.github.abryfs/willitsend (npm · willitsend)

Deterministic pre-send lint for SMS/iMessage: silent carrier filtering and segment blowups.

- Trust score: 65/100 (medium)
- Change this week: +24
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `willitsend`: 65/100 (this document), [markdown](https://verifymcp.io/servers/abryfs-willitsend/willitsend.md), [page](https://verifymcp.io/servers/abryfs-willitsend/willitsend)

## Channel facts

- Registry: `npm`
- Package: `willitsend`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - 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.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 17 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add abryfs-willitsend -- npx -y willitsend
```

### Codex

```bash
codex mcp add abryfs-willitsend -- npx -y willitsend
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "abryfs-willitsend": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "willitsend"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add abryfs-willitsend --command npx --arg -y --arg willitsend
```

### Hermes

```yaml
mcp_servers:
  abryfs-willitsend:
    command: "npx"
    args: ["-y", "willitsend"]
```

### Other

```json
{
  "mcpServers": {
    "abryfs-willitsend": {
      "command": "npx",
      "args": [
        "-y",
        "willitsend"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 65, +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.

### 2026-08-02 (score 64, +47)

- [security regression] GHSA-frvp-7c67-39w9 affects this package: medium
- [security regression] Provenance: unverified → fail
- [security regression] Known CVEs: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Dependency health: unverified → partial
- [functional] Licence: MIT

### 2026-08-01 (score 17, −6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 23, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-29 (score 41, +17)

- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 24, −17)

- [functional regression] Security disclosure: unverified → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 41)

First indexed and scored.

## MCP tools (1)

### `preflight_message` (~823 tokens)

Preflight a message before sending

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.

Input parameters:

- `body` (string, required): 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.

Output parameters:

- `findings` (array)
- `trace` (object)
- `verdict` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/abryfs-willitsend/willitsend#diagnostics

## Score history

- 2026-08-03: 65
- 2026-08-02: 64
- 2026-08-01: 17
- 2026-07-31: 23
- 2026-07-29: 41
- 2026-07-28: 24
- 2026-07-27: 41

## Links

- npm package: https://www.npmjs.com/package/willitsend
- Socket report: https://socket.dev/npm/package/willitsend
- Repository: https://github.com/abryfs/willitsend
- Changelog RSS feed: https://verifymcp.io/servers/abryfs-willitsend/willitsend/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/abryfs-willitsend/willitsend/changelog.json
- HTML version of this page: https://verifymcp.io/servers/abryfs-willitsend/willitsend