io.github.TecniForgeMaryam/androidapi-mcp
NPM · ANDROIDAPI-MCP · SCANNED AUG 3
Send SMS & WhatsApp, verify OTPs, manage contacts, and control Android devices via AndroidAPI.net.
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 Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- 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 & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2653 tokens (~51/item across 52 items; 52 tools + 0 resources), lean.Pass
- 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 Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% of tool parameters carry a description.Partial
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 · androidapi-mcp
claude mcp add tecniforgemaryam-androidapi-mcp -- npx -y androidapi-mcp
codex mcp add tecniforgemaryam-androidapi-mcp -- npx -y androidapi-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tecniforgemaryam-androidapi-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"androidapi-mcp"
],
"enabled": true
}
}
} openclaw mcp add tecniforgemaryam-androidapi-mcp --command npx --arg -y --arg androidapi-mcp
mcp_servers:
tecniforgemaryam-androidapi-mcp:
command: "npx"
args: ["-y", "androidapi-mcp"] {
"mcpServers": {
"tecniforgemaryam-androidapi-mcp": {
"command": "npx",
"args": [
"-y",
"androidapi-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.
- 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 +45
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- License: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 −24
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 38
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
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.
androidapi_validate_whatsapp_phone ~54
Check whether a phone number is registered on WhatsApp.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number in E.164 format. |
| unique | string | yes | WhatsApp account unique ID to use for the check. |
No output schema declared.
No examples provided.
androidapi_verify_otp ~45
Verify an OTP that was entered by the user. Returns success if the OTP is valid and not expired.
| Name | Type | Req | Description |
|---|---|---|---|
| otp | string | yes | OTP code entered by the user. |
No output schema declared.
No examples provided.