Skip to content

MCP servers › co.civai.nova › mcp-apple_developer

MCP server · registry snapshot 2026-11-02 · last tested 2026-11-02

co.civai.nova/mcp-apple_developer

Apple Developer MCP by Nova (CIVAI) — the publisher's title

by nova.civai.co · domain (the registry's namespace rule)Website ↗

Ship a new iOS app from chat. AI runs App Store Connect, builds, release, and submission through Ap… — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-02version 1.0.0streamable HTTP55 tools

Summary

co.civai.nova/mcp-apple_developer is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain nova.civai.co. On 2026-11-02 ProtocolProbe connected to it in read-only mode and read its inventory: 55 tools, 3 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
55
Last tested
2026-11-02

Tool list size

13,724 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (55 tools). Counted with Anthropic's token counter on 2026-11-02, from the tool list we read on 2026-11-02. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-02 (nova.civai.co), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 23 tools whose name or declaration suggests they change data (create_bundle_id, delete_bundle_id, create_asc_api_key, create_app_bundle, create_app and 18 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-02.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-02
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-11-02 (registry, as of the 2026-11-02 snapshot)
First listed version
2026-11-02 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-02
Package and repository
checked 2026-11-02
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-01, listed on 2026-11-02 with version 1.0.0 (published 2026-11-02).

Source: the official MCP Registry list on 2026-11-01 and on 2026-11-02.

What it is

What does this server offer?

Observed inventory
55tools
3resources
0prompts

None of its 55 tools are described as changing anything. For 55 the reading was uncertain, so no mark is shown.

  • “After operator completes Apple IDMSA in a browser, verify Developer portal session (checkPermissions).”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • session_statuson 13 other servers

    “ASC session check”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • list_bundle_ids

    “List bundle IDs registered on developer.apple.com for the current team.”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • create_bundle_id

    “Register a new bundle ID on developer.apple.com (requires Developer Identifiers session from start_browser_auth).”

    5 inputs, 2 required
    • bundle_idstringrequired
    • bundle_display_namestring
    • bundle_platformstring
    • developer_team_idstringrequired“Apple Developer Team ID (teamId query parameter).”
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • delete_bundle_id

    “Remove a bundle ID from developer.apple.com (requires Developer Identifiers session from start_browser_auth).”

    4 inputs, 1 required
    • bundle_idstring“Reverse-DNS id to remove (resolved via ascBundleIds if record id omitted).”
    • developer_bundle_record_idstring“Developer portal bundleIds record id (from Identifiers edit URL).”
    • developer_team_idstringrequired“Apple Developer Team ID (teamId).”
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • list_asc_api_keys

    “List App Store Connect API team keys and the team issuer id (for EAS / CI).”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • create_asc_api_key

    “Create an App Store Connect API team key.”

    4 inputs, 1 required
    • api_key_nicknamestringrequired
    • api_key_rolestring
    • download_p8boolean“Fetch private key immediately after create (only chance Apple offers)”
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • download_asc_api_key

    “Download the one-time .p8 private key for an existing API key when canDownload is still true.”

    2 inputs, 1 required
    • api_key_idstringrequired
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • revoke_asc_api_key

    “Permanently revoke an App Store Connect API team key (cannot be undone).”

    3 inputs, 2 required
    • api_key_idstringrequired
    • confirm_revoke_api_keybooleanrequired“Must be true to proceed”
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • get_bundle_id

    “Get details for one existing bundle ID by its ASC resource id.”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • “List apps visible to the current App Store Connect session.”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • list_app_bundles

    “List ASC app bundles (iris GET /appBundles).”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
Show 43 more tools
  • create_app_bundle

    “Create ASC app bundle (may 403 if tenant allows GET only).”

    3 inputs
    • bundle_namestring“Display name for the app bundle.”
    • primary_app_idstring“ASC apps id for the first app in the bundle.”
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • “Create App Store Connect app”

    6 inputs, 3 required
    • bundle_idstringrequired
    • app_namestringrequired
    • skustringrequired
    • primary_localestring
    • version_stringstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • “Get one app's details (name, bundle id, SKU) by asc_app_id.”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • “Update an existing app's name, primary locale, or bundle id (PATCH apps).”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • probe_update_version_localization

    “PATCH app store version localization promotional text (requires asc_app_id / localization_id on tenant).”

    3 inputs
    • promotional_textstring
    • localization_idstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • update_version_localization

    “Update the current app store version's description, keywords, promotional text, what's new, support URL, or marketing URL for one localization (PATCH app store version localization).”

    8 inputs
    • localization_idstring
    • descriptionstring
    • keywordsstring
    • promotional_textstring
    • whats_newstring
    • support_urlstring
    • marketing_urlstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • get_testflight_public_link

    “Create or reuse an external TestFlight group, attach a processed build, enable the public join link, and return https://testflight.apple.com/join/… Requires asc_session_cookie (session_status OK).”

    16 inputs, 1 required
    • asc_app_idstringrequired
    • build_idstring
    • build_numberstring
    • build_selectionstring
    • beta_group_namestring
    • skip_beta_reviewstring
    • beta_app_descriptionstring
    • beta_what_to_teststring
    • beta_feedback_emailstring
    • beta_privacy_policy_urlstring
    • beta_marketing_urlstring
    • beta_contact_first_namestring
    • beta_contact_last_namestring
    • beta_contact_phonestring
    • beta_contact_emailstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • submit_testflight_beta_review

    “Submit a processed build for TestFlight external Beta App Review (iris betaAppReviewSubmissions).”

    15 inputs, 1 required
    • asc_app_idstringrequired
    • build_idstring
    • build_numberstring
    • build_selectionstring
    • beta_group_namestring
    • beta_app_descriptionstring
    • beta_what_to_teststring
    • beta_feedback_emailstring
    • beta_privacy_policy_urlstring
    • beta_marketing_urlstring
    • beta_contact_first_namestring
    • beta_contact_last_namestring
    • beta_contact_phonestring
    • beta_contact_emailstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • “List ASC builds for asc_app_id (newest first).”

    2 inputs
    • asc_app_idstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • submit_build_for_review

    “Operator uploaded a new build: attach latest, build_number (ASC build version), or build_id to the current store version; optionally submit for review when confirm_submit_for_review=true.”

    9 inputs
    • asc_app_idstring
    • app_store_version_idstring
    • build_idstring
    • build_numberstring“e.g.”
    • build_selectionstring
    • attach_onlystring“true = attach only, do not submit”
    • confirm_submit_for_reviewstring“true = after attach, create review submission and PATCH submitted=true”
    • uses_non_exempt_encryptionstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • upload_buildon 1 other server

    “Upload a .ipa to App Store Connect via Transporter on the replay host.”

    3 inputs
    • ipa_urlstring“https URL to download signed .ipa before Transporter upload”
    • ipa_pathstring“Legacy path on replay host or https URL”
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • set_version_build

    “Set which build is attached to an app store version without also running export-compliance or wait-for-processing steps.”

    3 inputs
    • app_store_version_idstring
    • build_idstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • get_review_submission

    “Get the status and attached items of one review submission by review_submission_id.”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • create_review_submission

    “Create a new, empty review submission (READY_FOR_REVIEW) for an app so a version/build can be attached before submit.”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • attach_review_item

    “Attach an app store version or build item to an existing review submission by review_submission_id.”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • submit_build_and_press_submit

    “Upload done: attach latest/build number/build_id to current version, then press Submit for Review in ASC via API.”

    7 inputs
    • asc_app_idstring
    • app_store_version_idstring
    • build_idstring
    • build_numberstring
    • build_selectionstring
    • uses_non_exempt_encryptionstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • press_submit_for_review

    “Build already on version: create review submission and PATCH submitted=true.”

    4 inputs, 1 required
    • asc_app_idstring
    • app_store_version_idstring
    • confirm_submit_for_reviewstringrequired
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • submit_for_reviewon 2 other servers

    “Press Submit for Review, restricted to apps on the probe/disposable allowlist (checked server-side) and gated behind confirm_probe_submit=true.”

    4 inputs, 1 required
    • asc_app_idstring
    • app_store_version_idstring
    • confirm_submit_for_reviewstringrequired
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • list_review_messages

    “Resolution Center threads and App Review messages for asc_app_id.”

    3 inputs, 1 required
    • asc_app_idstringrequired
    • resolution_center_thread_idstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • distribute_build_to_testflight

    “Add a VALID build to TestFlight internal or external beta group.”

    17 inputs, 1 required
    • asc_app_idstringrequired
    • build_idstring
    • build_numberstring
    • build_selectionstring
    • testing_scopestring
    • tester_emailsstring“Comma-separated team emails to add to internal group”
    • beta_group_namestring
    • skip_beta_reviewstring
    • beta_app_descriptionstring
    • beta_what_to_teststring
    • beta_feedback_emailstring
    • beta_privacy_policy_urlstring
    • beta_contact_first_namestring
    • beta_contact_last_namestring
    • beta_contact_phonestring
    • beta_contact_emailstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • invite_testflight_testers

    “Add testers to a TestFlight beta group by email.”

    6 inputs, 1 required
    • asc_app_idstring
    • tester_emailsstringrequired“Comma-separated emails”
    • testing_scopestring
    • beta_group_idstring
    • beta_group_namestring“Default Internal Testing or Public Link Testers by scope”
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • list_asc_team_members

    “List active App Store Connect team members and pending email invitations, returning only each person's identifier (email/username) and roles.”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • invite_asc_team_member

    “Invite a user to your App Store Connect team (email invitation, 3-day expiry).”

    8 inputs, 4 required
    • invite_emailstringrequired
    • invite_first_namestringrequired
    • invite_last_namestringrequired
    • asc_rolesstring“Comma-separated roles, e.g.”
    • limit_visible_appsstring
    • visible_app_idsstring
    • confirm_invite_team_memberstringrequired
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • list_app_media_sets

    “List existing screenshot and app preview sets for an app store version localization (read-only).”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • “Get one build's processing state and metadata by build_id.”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • get_review_path

    “Get the Resolution Center and App Review URLs for an app, for messages Apple has not exposed via list_review_messages.”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • get_app_store_version

    “GET iOS appStoreVersions for asc_app_id”

    2 inputs
    • asc_app_idstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • update_app_info_localization

    “Update the localized app name, subtitle, and privacy policy URL for one locale (PATCH app info localization).”

    5 inputs
    • app_info_localization_idstring
    • app_namestring
    • subtitlestring
    • privacy_policy_urlstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • upload_screenshot

    “Upload one App Store screenshot into a single carousel slot via the screenshot bytes (screenshot_image_base64) or a URL to fetch them from (screenshot_image_url).”

    6 inputs
    • localization_idstring
    • screenshot_image_base64string“PNG/JPEG base64 or data: URI (MCP preferred)”
    • screenshot_image_urlstring“https URL to master image”
    • screenshot_file_pathstring“Legacy: https URL or path on SecOps replay host”
    • screenshot_display_typestring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • wait_build_processed

    “Poll until build processing VALID”

    2 inputs
    • build_idstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • set_export_compliance

    “PATCH build export encryption flag”

    3 inputs
    • build_idstring
    • uses_non_exempt_encryptionstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • attach_build_and_compliance

    “After Expo/CI has uploaded the .ipa to ASC: list builds for asc_app_id, wait until processing is VALID, attach build_id to app_store_version_id, set export compliance (uses_non_exempt_encryption usua…”

    5 inputs
    • asc_app_idstring
    • app_store_version_idstring
    • build_idstring“Optional; latest build from list_builds when omitted.”
    • uses_non_exempt_encryptionstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • update_app_review_information

    “Create or update App Store review contact and demo sign-in for the current version (iris appStoreReviewDetail).”

    10 inputs, 5 required
    • asc_app_idstring
    • review_contact_emailstringrequired
    • review_contact_first_namestringrequired
    • review_contact_last_namestringrequired
    • review_contact_phonestringrequired
    • demo_account_namestring“Required when the app has sign-in (default).”
    • demo_account_passwordstring“Demo password for App Review.”
    • review_notesstringrequired
    • requires_demo_accountboolean“Default true.”
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • set_age_rating

    “Set the app's age rating questionnaire answers (content descriptors) required before submit.”

    1 input
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • set_app_store_metadata

    “Set primary App Store category, version copyright, and third-party content rights declaration.”

    4 inputs
    • primary_categorystring
    • copyrightstring
    • content_rights_declarationstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • set_app_privacy

    “Set App Privacy data-collection declarations (iris appDataUsages): pass app_privacy_profile=contact or analytics for the built-in presets, or app_privacy_profile=custom with an inline declarations JS…”

    5 inputs
    • app_privacy_profilestring
    • publish_app_privacystring
    • replace_app_privacystring
    • app_privacy_declarations_jsonstring“Required when app_privacy_profile=custom.”
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • delete_orphan_review_submissions

    “Delete empty READY_FOR_REVIEW review submission drafts (zero items) for an app.”

    4 inputs, 1 required
    • asc_app_idstringrequired
    • review_submission_idstring“Optional — delete one open orphan draft by id”
    • dry_runstring“List would_delete only; no DELETE when true”
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • get_pre_submit_statuson 1 other server

    “Read-only checklist before Submit for Review (build, privacy, category, copyright).”

    2 inputs
    • asc_app_idstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • set_pricing_and_availability

    “Set or read USA base price tier (0 free, 1+ paid).”

    4 inputs
    • price_tierstring
    • price_base_territorystring
    • pricing_modestring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • delete_screenshots

    “Delete screenshots for targeted iPhone display types (e.g.”

    5 inputs, 1 required
    • localization_idstring
    • screenshot_display_typesstringrequired“Comma-separated types, e.g.”
    • screenshot_idstring“Optional — delete one screenshot when it belongs to a targeted size”
    • dry_runstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • upload_screenshots

    “Upload one App Store screenshot for a single iPhone display size from a master image that this tool auto-resizes.”

    6 inputs
    • screenshot_image_base64string
    • screenshot_image_urlstring
    • screenshot_file_pathstring
    • screenshot_display_typesstring“Single type per call, e.g.”
    • screenshot_display_typestring“Alias when passing one size via screenshot_display_type.”
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • get_account_compliance_status

    “Business portal links for Agreements/Tax/Banking plus price schedule hints (contracts are human-signed).”

    2 inputs
    • asc_app_idstring
    • notification_messagestring“Short user-facing sentence for this action if the follow-up reply fails.”
  • start_browser_authon 3 other servers

    “Open App Store Connect sign-in only when needed.”

    1 input
    • force_reconnectboolean“DESTRUCTIVE: delete the saved session cookie for this tenant, then open the viewer for a fresh sign-in.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-02.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
39% of 218
Tools with a description
100% of 55
Typical description length
160 characters

The tool set

Counted from the listing

Tools
55
Size of the list
about 8,901 tokens for an agent to load (characters ÷ 4)
Naming
54 of 55 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 55 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-02 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://nova.civai.co/mcp/agents/mcp-apple_developer
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "mcp-apple_developer": {
      "url": "https://nova.civai.co/mcp/agents/mcp-apple_developer"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "mcp-apple_developer": {
      "type": "http",
      "url": "https://nova.civai.co/mcp/agents/mcp-apple_developer"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"mcp-apple_developer","type":"http","url":"https://nova.civai.co/mcp/agents/mcp-apple_developer"}'
Claude Code
claude mcp add --transport http mcp-apple_developer https://nova.civai.co/mcp/agents/mcp-apple_developer
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "mcp-apple_developer": {
      "type": "streamableHttp",
      "url": "https://nova.civai.co/mcp/agents/mcp-apple_developer",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "mcp-apple_developer": {
      "httpUrl": "https://nova.civai.co/mcp/agents/mcp-apple_developer"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.mcp-apple_developer]
url = "https://nova.civai.co/mcp/agents/mcp-apple_developer"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "mcp-apple_developer": {
      "url": "https://nova.civai.co/mcp/agents/mcp-apple_developer"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://nova.civai.co/mcp/agents/mcp-apple_developer --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint nova.civai.co/mcp/agents/mcp-apple_developerSession openedmatchesour test · 2026-11-02
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-02

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-02. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about co.civai.nova/mcp-apple_developer

Answered from the data above

Who publishes co.civai.nova/mcp-apple_developer?

The registry ties the namespace co.civai.nova to the domain nova.civai.co; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does co.civai.nova/mcp-apple_developer need an API key or sign-in?

It opened a session without any credential on 2026-11-02. The registry entry declares no required credential; no declaration is not a guarantee.

Has co.civai.nova/mcp-apple_developer been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-02
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-02, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 650 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 55 tools, 3 resources, 0 prompts.
  4. 5,612 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-11-02; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-02
MCP capability
experimental, resources, tools
our test · 2026-11-02
Transport
streamable HTTP
registry · 2026-11-02
Required credentials
none declared
registry · 2026-11-02 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-02
Lifecycle status
registry · 2026-11-02
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-02

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “co.civai.nova/mcp-apple_developer: MCP server record.” Data checked 2026-11-02. https://protocolprobe.com/mcp/servers/co.civai.nova/mcp-apple_developer

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/co.civai.nova/mcp-apple_developer)](https://protocolprobe.com/mcp/servers/co.civai.nova/mcp-apple_developer)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology