Homing Pigeon
NPM · HOMINGPIGEONDEV · 2 COMPONENTS
Homing Pigeon (homingpigeon.dev) sends text alerts from your code or agent to one phone: yours.
Available components
Last scanned (16 hours ago)
Scores higher than 43% of npm servers
Category Communication
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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 246 tokens (~82/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +1
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.1.1 → 0.1.2 functional
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 56
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 5 Nov 2026 · Analysed npm/homingpigeondev@0.1.2
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
send ~69
Send a text message to the account owner's verified phone. The recipient is fixed; `message` is the only required field.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Reuse this on a retry so it cannot double-text. |
| message | string | yes | The alert text, up to 480 characters. |
No output schema declared.
No examples provided.
status ~33
Report whether the phone is verified or paused, how many messages remain, and what happened to the last send. It sends nothing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify ~105
Verify the user's own US mobile number for Homing Pigeon (homingpigeon.dev). Call with phone to text them a six-digit code, then call again with phone and the code they read back. It cannot verify anyone else's number.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | The six-digit code the user received. Omit on the first call. |
| phone | string | yes | The user's own US mobile number. |
| project | string | – | Short name shown in front of each text. |
No output schema declared.
No examples provided.
How do I install the Homing Pigeon MCP server?
Homing Pigeon runs locally as an npm package, launched with npx -y homingpigeondev 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 · homingpigeondev
claude mcp add dev-homingpigeon-homingpigeondev -- npx -y homingpigeondev mcp
What is the Homing Pigeon MCP server?
Homing Pigeon is an MCP server listed in the public MCP registry as dev.homingpigeon/homingpigeondev. Homing Pigeon (homingpigeon.dev) sends text alerts from your code or agent to one phone: yours. This page covers its npm package (homingpigeondev).
Is the Homing Pigeon MCP server safe to use?
Homing Pigeon scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Homing Pigeon MCP server expose?
Homing Pigeon exposes 3 tools: verify, send, status. Their descriptions and schemas cost roughly 207 tokens of context every time the server is loaded.
Is the Homing Pigeon MCP server still maintained?
Homing Pigeon is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Homing Pigeon MCP server under?
Homing Pigeon declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Homing Pigeon MCP server?
VerifyMCP ran 16 checks on Homing Pigeon, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.