io.github.hoainho/podium-mcp
NPM · PODIUM-MCP · SCANNED SEP 20
Mobile E2E MCP (51 tools): iOS + Android, native UI + canvas/WebGL, no-vision, RN debug
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 → Why this is hard to score →
Supply Chain Security98
- 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
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 68 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7562 tokens (~148/item across 51 items; 51 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "app_terminate" implies "terminate" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 51 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
How do I install the io.github.hoainho/podium-mcp server?
io.github.hoainho/podium-mcp runs locally as an npm package, launched with npx -y podium-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 · podium-mcp
claude mcp add hoainho-podium-mcp -- npx -y podium-mcp
{
"mcpServers": {
"hoainho-podium-mcp": {
"command": "npx",
"args": [
"-y",
"podium-mcp"
]
}
}
} {
"servers": {
"hoainho-podium-mcp": {
"command": "npx",
"args": [
"-y",
"podium-mcp"
]
}
}
} codex mcp add hoainho-podium-mcp -- npx -y podium-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hoainho-podium-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"podium-mcp"
],
"enabled": true
}
}
} openclaw mcp add hoainho-podium-mcp --command npx --arg -y --arg podium-mcp
mcp_servers:
hoainho-podium-mcp:
command: "npx"
args: ["-y", "podium-mcp"] {
"McpServers": {
"hoainho-podium-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"podium-mcp"
]
}
}
} assistant mcp add hoainho-podium-mcp -t stdio -c npx -a -y podium-mcp
{
"mcpServers": {
"hoainho-podium-mcp": {
"command": "npx",
"args": [
"-y",
"podium-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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/podium-mcp@0.4.0
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 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 →
webview_network ~447
Captures HTTP traffic made INSIDE a WebView (fetch + XMLHttpRequest) and exports it as JSON or a redacted HAR 1.2 log. This is the network-debugging path for WebView-based apps — RN shells that host their UI in a WKWebView, where the API calls run in the web layer so metro_network (CDP Network domain) captures nothing. It injects a fetch/XHR recorder into the page, captures for durationMs while you drive the app, then returns request/response metadata (url, method, status, headers, timing). Only requests made AFTER capture starts are recorded. format:'har' emits a valid HAR 1.2 log (HAR-lite — no response bodies) openable in Chrome DevTools → Import HAR; pass saveTo to write the .har file. Sensitive headers (authorization/cookie/…) and request bodies are REDACTED by default — set redact:false to keep them (don't commit unredacted HAR: it leaks tokens). Requires the app's WKWebView to be inspectable (isInspectable=true) — on by default in debug/staging builds, frequently disabled in production App Store builds.
| Name | Type | Req | Description |
|---|---|---|---|
| durationMs | integer | – | How long to capture (ms) while you drive the app (default 5000) |
| format | string | – | Output format: 'json' (default, structured entries) or 'har' (HAR 1.2 log). |
| includeResources | boolean | – | Also include the browser's retroactive Performance Resource Timing list — EVERY request the document made since navigation, including ones that fired before capture started (URL + timing + size, but… |
| redact | boolean | – | Mask sensitive headers (authorization/cookie/…) and request bodies. Default true. |
| saveTo | string | – | Optional file path to write the output (a .har file when format:'har'). |
| udid | string | yes | Simulator / device UDID |
| webviewId | string | – | Target WebView id. Omit to auto-select the first visible WebView. |
No output schema declared.
No examples provided.
What is the io.github.hoainho/podium-mcp server?
io.github.hoainho/podium-mcp is listed in the public MCP registry as io.github.hoainho/podium-mcp. Mobile E2E MCP (51 tools): iOS + Android, native UI + canvas/WebGL, no-vision, RN debug. This page covers its npm package (podium-mcp).
Is the io.github.hoainho/podium-mcp server safe to use?
io.github.hoainho/podium-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.hoainho/podium-mcp server expose?
io.github.hoainho/podium-mcp exposes 51 tools: podium_health, device_list, device_boot, app_install, app_launch, and 46 more. Their descriptions and schemas cost roughly 7,562 tokens of context every time the server is loaded.
Is the io.github.hoainho/podium-mcp server still maintained?
io.github.hoainho/podium-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.hoainho/podium-mcp server under?
io.github.hoainho/podium-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.