Home / MCP registry index / co.civai.nova/mcp-android_developer
Android Developer MCP by Nova (CIVAI)
co.civai.nova/mcp-android_developer in the official MCP registry.
Endpoint https://nova.civai.co/mcp/agents/mcp-android_developer.
The registry describes it as: Ship a new Android app from chat. AI runs Google Play Console listings, screenshots, releases, uplo…
We read its 38 tools on 2026-11-02. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http mcp-android-developer https://nova.civai.co/mcp/agents/mcp-android_developer{
"mcpServers": {
"mcp-android-developer": {
"url": "https://nova.civai.co/mcp/agents/mcp-android_developer"
}
}
}code --add-mcp '{"name":"mcp-android-developer","type":"http","url":"https://nova.civai.co/mcp/agents/mcp-android_developer"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
list_tracks get_track create_release upload_bundle check_package_name_availability create_app list_apps list_accounts update_store_listing update_store_listing_screenshots get_release start_rollout update_ads_declaration update_sign_in_details update_target_audience_content update_policy_declaration update_content_rating update_privacy_policy update_data_safety update_none_option_declaration upload_screenshot_asset promote_release get_pre_submit_status upload_store_listing_graphic enroll_play_app_signing get_user_permissions grant_app_permission attach_artifact_to_release refresh_browser_session update_track_countries get_app_submission_state send_app_for_review update_store_settings get_setup_state declare_asset_ai_state setup_closed_testing submit_prod_access_application start_browser_auth
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-02):
8872aac55e300ac0. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/co-civai-nova-mcp-android-developer)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.