phone-sms
PYPI · PHONE-SMS
Read and send SMS through your own Android phone over KDE Connect on your LAN. No cloud relay.
Available components
Last scanned (20 hours ago)
Scores higher than 88% of PyPI 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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to h-3303/phone-sms). View diagnostics → Pass
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 252 tokens (~63/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +5
- Stability: unverified → 0.40 ▲ functional
- 13 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Oct 26 63
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 16 Oct 2026 · Analysed pypi/phone-sms@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | h-3303/phone-sms |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/h-3303/phone-sms/.github/workflows/publish.yml@refs/tags/v0.1.0 |
| Rekor log index | 3061641685 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:f7294d15bb7088f18cf638b1fad189b3de4fa9660a38e5bfeb920dda8469eed0 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | uv_build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| 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 →
find_contact ~25
Look up phone contacts by name or number fragment.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_threads ~68
List SMS conversations, newest first, with the latest message of each. Each line starts with the thread id, which read_thread takes. contact: optional name or number fragment to filter on.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | – |
| limit | integer | – | – |
| unread_only | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
read_thread ~38
Read the most recent `count` messages of one conversation, oldest first.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| thread_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
send_sms ~69
Send an SMS (several numbers = group message) from the user's phone and number. ONLY call after the user has explicitly approved this exact recipient list and text. `to` takes phone numbers; resolve names with find_contact first.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
| to | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the phone-sms MCP server?
phone-sms runs locally as a PyPI package, launched with uvx phone-sms. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · phone-sms
claude mcp add h-3303-phone-sms -- uvx phone-sms
What is the phone-sms MCP server?
phone-sms is an MCP server listed in the public MCP registry as io.github.h-3303/phone-sms. Read and send SMS through your own Android phone over KDE Connect on your LAN. No cloud relay. This page covers its PyPI package (phone-sms).
Is the phone-sms MCP server safe to use?
phone-sms scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. Its build provenance is signed and verified. 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 phone-sms MCP server expose?
phone-sms exposes 4 tools: list_threads, read_thread, find_contact, send_sms. Their descriptions and schemas cost roughly 200 tokens of context every time the server is loaded.
Is the phone-sms MCP server still maintained?
phone-sms is still listed as active in the MCP registry. We last reached this channel on 16 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 phone-sms MCP server under?
phone-sms declares the GPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.