Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
ContactZapp is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
Keeps your contacts in sync across Google, Microsoft, Apple and CardDAV, and cleans up duplicates.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http contactzapp-mcp https://app.contactz.app/api/v1/mcp --header 'Authorization: Bearer ${API_KEY}'
# 2 — ask your agent for something these tools do
# api_key_check, contact_find, contact_create and 4 more
It needs API_KEY (Your ContactZapp API key. Make one in Settings › Advanced. Start the value with Bearer): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.
ContactZapp costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
COAll 1 server
contactz1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads API_KEY (Your ContactZapp API key. Make one in Settings › Advanced. Start the value with Bearer) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx API_KEY … and open a new terminal (Windows).
claude mcp add --scope user --transport http contactzapp-mcp https://app.contactz.app/api/v1/mcp --header 'Authorization: Bearer ${API_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: Authorization header — Your ContactZapp API key. Make one in Settings › Advanced. Start the value with Bearer.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Returns the user the key acts for, the user's plan and the key's scopes. Any live key can call it, so call it to test a key.
No parameter schema on file.
Finds the user's contacts by email address, phone number or text. Give at most one of email, phone and query: - email finds the contacts with that address. Case does not matter. - phone finds the contacts with that number, however it is formatted. - query searches the way the Contacts screen's search does. - With none of them, every contact is listed, newest first. Deleted and merged
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cursor | string | no | The previous page's nextCursor. |
| string | no | — | |
| limit | integer | no | Page size; 50 when omitted. |
| phone | string | no | — |
| query | string | no | — |
Adds a contact. If the user already has this person, the values may go to that contact instead: - If the user's Auto-Merge level covers the match, the values are added to the existing contact: 200, merged. - Otherwise a new contact is created: 201, created. If it may be a duplicate, it also waits in Review duplicates: 201, needs_review. ContactZapp saves the contact in one two-way account:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| Idempotency-Key | string | no | Any string of 1 to 255 bytes you choose for this write, such as a UUID. Repeat the request with the same key and body within 24 hours, and you get the first result back and nothing is written twice. T |
| body | object | yes | The body of a contact create or update: the contact fields a read shows that a write can change, under the same names and in the same shapes, and nothing else. A field the body carries that is not on |
Returns one contact. id is the contact's id or its publicId, such as CS-0042. A deleted or merged contact is a 404, and so is another user's contact.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
Changes a contact, as editing it in ContactZapp does. Only the fields you send change. A field you leave out keeps its value. The change goes to every two-way account the contact is in, never to a read-only one. History records it as the user's change and names the API key. A contact waiting in Review duplicates cannot be changed until the review is decided: 409, contact_pending_review. Send a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| Idempotency-Key | string | no | Any string of 1 to 255 bytes you choose for this write, such as a UUID. Repeat the request with the same key and body within 24 hours, and you get the first result back and nothing is written twice. T |
| body | object | yes | The body of a contact create or update: the contact fields a read shows that a write can change, under the same names and in the same shapes, and nothing else. A field the body carries that is not on |
| id | string | yes | The contact's id or its publicId (CS-0042). |
Starts a sync, the same as Sync now in ContactZapp. History shows it as a manual run. The answer is 202 with the sync's state, queued or running. If a sync is already going, you get that one back and no second one starts.
No parameter schema on file.
Lists the events of one type, newest first. Zapier, Make and n8n poll this to start an automation. Each item's id never changes. Poll again and the items you already have come back with the same ids, with new ones on top. Skip the ids you have seen. - contact.created, contact.updated, contacts.merged and account.needs_attention come from History, and are kept as long as History keeps t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cursor | string | no | The previous page's nextCursor, to read further back. |
| event | string | yes | The events the API reports, as polling triggers. - contact.created: a contact was added. - contact.updated: a contact was changed. - contacts.merged: contacts were merged into one. - `match.nee |
| limit | integer | no | Page size; 50 when omitted. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ContactZapp or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.5 · scanned 6 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest673b21e6fbc66bfa881b708b060efd6f4eb821f6d9b91ff1a40d09cb277b15ac
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| api_key_check | no tags | |
| contact_find | no tags | |
| contact_create | state-write | state-write: declares readOnlyHint: false |
| contact_read | no tags | |
| contact_change | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| sync_start | state-write | state-write: declares readOnlyHint: false |
| event_list | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest673b21e6fbc66bfa
Scanned2026-11-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.5.
1.0.5
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish ContactZapp can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.