Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Apple Contacts

PYPI · APPLE-CONTACTS-MCP · 2 COMPONENTS

Inspect and search Apple Contacts on macOS, and resolve a contact into a message-ready recipient.

0 this week 90 Trust /100

Last scanned (2 hours ago)

Scores higher than 93% of PyPI servers

Category Communication

Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to JonathanRReed/Apple-MCPs). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
  • 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 645 tokens (~37/item across 17 items; 16 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety88
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "contacts_suggest_merge_candidates" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +39
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → 0.90 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Schema quality: unverified → 50 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 14 Oct 26 0
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Schema quality: unverified → 50 ▲ functional
    • Stability: unverified → 0.87 ▲ functional
    • Package version: 1.1.1 → 1.1.2 functional
    • Package version: 1.0.5 → 1.1.1 functional
  • 13 Oct 26 0
    • Package version: 1.1.0 → 1.1.1 functional
    • Package version: 1.0.5 → 1.1.0 functional
  • 12 Oct 26 −40
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 50 → unverified ▼ functional
    • Package version: 1.0.5 → 1.1.0 functional
  • 4 Oct 26 0
    • Stability: 0.97 → pass security
  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Oct 26 −1
    • Stability: pass → 0.93 functional
Diagnostics

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 17 Oct 2026 · Analysed pypi/apple-contacts-mcp@1.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo JonathanRReed/Apple-MCPs
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/JonathanRReed/Apple-MCPs/.github/workflows/release.yml@refs/tags/v1.1.2
Rekor log index 3252400682
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:8d71bf257953a92d74f15e66625ab4e83c160b32c8e02a15f732451e0e56377a

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~588 tokens

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 →

Tool Tokens
contacts_create_contact ~73

Create a new contact in Apple Contacts with a first name (required) and optional last name, organization, and note.

NameTypeReqDescription
emails–––
first_namestringyes–
last_namestring––
notestring––
organizationstring––
phones–––
NameTypeReqDescription
result–yes–

No examples provided.

contacts_delete_contact ~32

Permanently delete a contact by contact_id. Requires full_access safety mode.

NameTypeReqDescription
contact_idstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

contacts_find_duplicates ~28

Find likely duplicate Apple Contacts records using names, nicknames, phone numbers, and email addresses.

Input schema present but exposes no named parameters.

NameTypeReqDescription
result–yes–

No examples provided.

contacts_get_contact ~29

Fetch full details for an Apple Contacts record by contact_id.

NameTypeReqDescription
contact_idstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

contacts_get_prompt ~33

Fallback prompt rendering tool for tool-only MCP clients.

NameTypeReqDescription
arguments_json–––
namestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

contacts_health ~16

Report the active Apple Contacts MCP configuration.

Input schema present but exposes no named parameters.

NameTypeReqDescription
capabilitiesarrayyes–
contacts_accessiblebooleanyes–
okboolean––
permission_error–––
permission_error_code–––
permission_statusstring––
permission_suggestion–––
safety_modestringyes–
server_namestringyes–
transportstring––
versionstringyes–

No examples provided.

contacts_list_contacts ~28

List Apple Contacts entries.

NameTypeReqDescription
limitinteger––
offsetinteger––
NameTypeReqDescription
result–yes–

No examples provided.

contacts_list_prompts ~21

Fallback prompt discovery tool for tool-only MCP clients.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

contacts_permission_guide ~21

Explain how to grant Apple Contacts permission on macOS.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

contacts_recheck_permissions ~31

Recheck Contacts access after the user changes macOS permissions, and notify the client that Contacts resources changed.

Input schema present but exposes no named parameters.

NameTypeReqDescription
capabilitiesarrayyes–
contacts_accessiblebooleanyes–
okboolean––
permission_error–––
permission_error_code–––
permission_statusstring––
permission_suggestion–––
safety_modestringyes–
server_namestringyes–
transportstring––
versionstringyes–

No examples provided.

contacts_resolve_message_recipient ~39

Resolve a contact into a message-ready phone number or email address.

NameTypeReqDescription
channelstring––
querystringyes–
NameTypeReqDescription
result–yes–

No examples provided.

contacts_search_contacts ~36

Search Apple Contacts by name, phone number, or email address.

NameTypeReqDescription
limitinteger––
querystringyes–
NameTypeReqDescription
result–yes–

No examples provided.

contacts_suggest_merge_candidates ~30

Return likely duplicate Apple Contacts groups that are strong candidates for cleanup review.

NameTypeReqDescription
query–––
NameTypeReqDescription
result–yes–

No examples provided.

contacts_update_contact ~73

Update an existing contact's information. Only the fields you provide will be changed.

NameTypeReqDescription
contact_idstringyes–
emails–––
first_namestring––
last_namestring––
notestring––
organizationstring––
phones–––
NameTypeReqDescription
result–yes–

No examples provided.

get_tool_info ~48

Load the full schema, examples, and metadata for one tool from this server.

NameTypeReqDescription
include_examplesboolean––
include_schemaboolean––
namestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

search_tools ~50

Search this server's tool catalog by keyword, alias, or domain tag.

NameTypeReqDescription
domain_tags–––
limitinteger––
modestring––
querystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Apple Contacts MCP server?

Apple Contacts runs locally as a PyPI package, launched with uvx apple-contacts-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · apple-contacts-mcp

# add to Claude Code
claude mcp add jonathanrreed-apple-contacts-mcp -- uvx apple-contacts-mcp
Common questions

What is the Apple Contacts MCP server?

Apple Contacts is an MCP server listed in the public MCP registry as io.github.JonathanRReed/apple-contacts-mcp. Inspect and search Apple Contacts on macOS, and resolve a contact into a message-ready recipient. This page covers its PyPI package (apple-contacts-mcp).

Is the Apple Contacts MCP server safe to use?

Apple Contacts scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. Its build provenance is signed and verified. 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 Apple Contacts MCP server expose?

Apple Contacts exposes 16 tools: contacts_health, contacts_permission_guide, contacts_recheck_permissions, contacts_list_contacts, contacts_search_contacts, and 11 more. Their descriptions and schemas cost roughly 588 tokens of context every time the server is loaded.

Is the Apple Contacts MCP server still maintained?

Apple Contacts is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Apple Contacts MCP server under?

Apple Contacts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.