@aernoud/contactsmcp

MCPcommunity

v0.4.0Aernoud DekkerMITUpdated 4mo agonpm GitHub

MCP server for macOS Contacts.app — contact management via AppleScript

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

37Downloads/wk

4mo agoLast update

Package

AuthorAernoud Dekker

LicenseMIT

Version0.4.0

Sourcenpm+mcp-registry

npm@aernoud/contactsmcp

GitHubaernouddekker/macos-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface15 tools · 4 privileged

Security scan✓ Cleanv0.4.0 · 1mo agoHow well does this scan work?

EvalsNone

IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · 4 privileged

Statically extracted from the published packagev0.4.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

search-contactsSearch contacts in macOS Contacts.app by name, email, or phone number

Search contacts in macOS Contacts.app by name, email, or phone number

No input schema was published for this tool.

read-contactGet full details of a contact by their Contacts.app ID

Get full details of a contact by their Contacts.app ID

No input schema was published for this tool.

create-contactCreate a new contact in macOS Contacts.app

Create a new contact in macOS Contacts.app

No input schema was published for this tool.

update-contactUpdate fields on an existing contact in macOS Contacts.app

Update fields on an existing contact in macOS Contacts.app

No input schema was published for this tool.

list-groupsList all contact groups in macOS Contacts.app with member counts

List all contact groups in macOS Contacts.app with member counts

No input schema was published for this tool.

add-to-groupAdd a contact to a group in macOS Contacts.app

Add a contact to a group in macOS Contacts.app

No input schema was published for this tool.

remove-from-groupprivilegedRemove a contact from a group in macOS Contacts.app

Remove a contact from a group in macOS Contacts.app

No input schema was published for this tool.

delete-contactprivilegedDelete a contact from macOS Contacts.app

Delete a contact from macOS Contacts.app

No input schema was published for this tool.

create-groupCreate a new contact group in macOS Contacts.app

Create a new contact group in macOS Contacts.app

No input schema was published for this tool.

delete-groupprivilegedDelete a contact group from macOS Contacts.app

Delete a contact group from macOS Contacts.app

No input schema was published for this tool.

rename-groupprivilegedRename a contact group in macOS Contacts.app

Rename a contact group in macOS Contacts.app

No input schema was published for this tool.

list-group-membersList all contacts in a group in macOS Contacts.app

List all contacts in a group in macOS Contacts.app

No input schema was published for this tool.

get-my-cardGet the user's own contact card from macOS Contacts.app

Get the user's own contact card from macOS Contacts.app

No input schema was published for this tool.

get-vcardGet the vCard 3.0 text for a contact by their Contacts.app ID

Get the vCard 3.0 text for a contact by their Contacts.app ID

No input schema was published for this tool.

search-by-modification-dateFind contacts modified after a given date in macOS Contacts.app

Find contacts modified after a given date in macOS Contacts.app

No input schema was published for this tool.

15 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for macOS Contacts.app — contact management via AppleScript

Keywords

mcpmcp-servercontactsaddress-bookmacosapplescriptclaude

Alternatives

Comparing tool surfaces…

Tools exposed

15 tools · 4 privileged · observed 2026-08-31 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

search-contacts
read-contact
create-contact
update-contact
list-groups
add-to-group
remove-from-grouppriv
delete-contactpriv
create-group
delete-grouppriv
rename-grouppriv
list-group-members
get-my-card
get-vcard
search-by-modification-date

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-31 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod3.25.76
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.6
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.5.4
- cors2.8.6+1 not drawn1 dependency
  - object-assign4.1.1
- hono4.13.5
- jose6.2.10
- express5.2.1+27 not drawn1 dependency
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 49
below the depth cap: 5

wrappy 1 — required by once@1.4.0package cap reached
http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.