Native mobile build plan — Atom
Server Details
Native mobile build plan: declared native-mobile build-plan record checked per call.
- Status
- Healthy
- Uptime
- 39.1% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- nrupala/atom-services
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. Its purpose (submitting/auditing a native mobile build-plan record and returning a deterministic verdict) is stated explicitly, including what it does not do (no building, no store submission).
The single name uses clear snake_case with a noun-phrase describing the domain object, which is readable and predictable. With only one tool there is no cross-tool pattern to validate, so it cannot demonstrate strong consistency across a set.
A one-tool surface is thin: the domain covers six sections of build-plan auditing, yet there is no way to list, retrieve, or revise previously submitted records. The lone tool is dense and well-scoped internally, but the set is borderline under-provisioned.
Submission plus verdict is covered, but there are notable gaps: no read/list of existing build plans, no update/revision path for a plan already submitted, and no schema-discovery tool describing required evidence per section. Agents can work around this by embedding everything in one submission, but dead ends exist.
Available Tools
1 toolnative_mobile_build_planNative mobile build planARead-onlyIdempotentInspect
Submits a native mobile build-plan record (device constraints and platform citizenship, offline-first and sync, builds and signing, testing and accessibility, release/store and privacy, red lines) and returns a deterministic NATIVE_MOBILE_BUILD_PLAN_READY / NATIVE_MOBILE_BUILD_PLAN_NOT_READY / INSUFFICIENT_EVIDENCE verdict across six sections, including computed per-permission feature-coverage checks, with per-check evidence. Audits the declared build-plan record; it builds no app and submits nothing to any store.
Inputs: app, builds, offline, privacy, +6 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Tech stack decision memo: declared stack decision memo record checked per call.
MCP server design & review: declared MCP server record checked per call.
ML project framing review: declared framing record checked per call.
Poc design kill criteria verdict: declared POC design record checked per call.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceLets coding agents statically scan Swift, Kotlin/Java, Dart, React Native and manifest files for crash-prone operators, main-thread deadlocks, missing accessibility labels, insecure token storage, cleartext traffic and vague permission strings, and cross-check platform APIs against Info.plist, PrivacyInfo.xcprivacy and AndroidManifest permission/exported settings. It also runs syntax or full build verification, returning FAIL on error-level findings so agents must fix issues before claiming work is done.51 npmMIT
- AlicenseCqualityCmaintenanceEnables AI-assisted mobile development workflows with guarded build, Appium testing, security scanning, verification, and evidence-based fix-retest loops on Android and iOS.8212MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to publish hierarchical project plans and task status changes to a mobile app in real time, letting developers monitor progress and blockers without checking their computer.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to check a dedicated Mac's readiness, inspect recent iOS/Flutter/Xcode builds and artifacts, and optionally dispatch allowlisted build workflows without exposing a shell or signing credentials.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.