ContactZapp MCP server
app.contactz/contactzappcontactz.appstreamable-httpv1.0.6Scanned
Keeps your contacts in sync across Google, Microsoft, Apple and CardDAV, and cleans up duplicates.
7 tools: 1 can delete or cancel things, 2 change things and 4 only read.
- Reads private data · 3
- Reads text others write · 2
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ContactZapp MCP server can do
The ContactZapp MCP server is published by contactz.app, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (1 tool: contact_change) and create or change data (2 tools: contact_create and sync_start). 4 tools only read.
3 tools read private data (api_key_check, contact_find and contact_read); 2 tools bring in text other people can write (api_key_check and contact_find); 1 tool can send data out of your system (contact_create). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 1.0.6.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Deletes or cancels 1Claude Code: deny
contact_changeChanges a contact, as editing it in ContactZapp does.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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 or the connected app that made it. A contact waiting in Review duplicates cannot be changed until the review is decided: 409, `contact_pending_review`. Send an `Idempotency-Key` header to make a retry safe.
Annotations the server declares
- destructiveHint: true
- readOnlyHint: false
Changes things 2Claude Code: ask
contact_createAdds a contact.Can send data outNo findings
Why it is in this group
- The name "contact_create" says "create": a word for a change.
What it can reach
- outboundThe input takes a destination (input.body.phones): what the tool writes goes there.
- outboundThe input takes a URL (input.body.urls): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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: the first one the user linked that keeps an address book and is not paused. The next sync copies it to the user's other two-way accounts, never to a read-only one. A create is never refused for the plan's contact limit. Over the limit, the contact is created frozen and `contact.frozen` is true. ContactZapp keeps a frozen contact but does not sync it until the user upgrades or frees a place. Send an `Idempotency-Key` header to make a retry safe.
Annotations the server declares
- destructiveHint: false
- readOnlyHint: false
sync_startStarts a sync, the same as Sync now in ContactZapp.No findings
Why it is in this group
- The name "sync_start" says "sync": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- readOnlyHint: false
Only reads 4Show 4 read-only tools
api_key_checkReturns the user the request acts for, the user's plan, the user's sign-in email and the scopes of the API key or connected app that made it.Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "return" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Returns the user the request acts for, the user's plan, the user's sign-in email and the scopes of the API key or connected app that made it. Any live key or access token can call it, so call it to test one.
Annotations the server declares
- destructiveHint: false
- readOnlyHint: true
contact_findFinds the user's contacts by email address, phone number or text.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "contact_find" says "find": a word for reading.
What it can reach
- private-dataThe name "contact_find" says "find" and "contact": it reads contacts.
- private-dataThe description's first sentence says "find" and "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "find" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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 contacts are never returned. For the next page, send the `nextCursor` you got as `cursor`, with the same filter. The last page has no `nextCursor`.
Annotations the server declares
- destructiveHint: false
- readOnlyHint: true
contact_readReturns one contact.Reads private dataNo findings
Why it is in this group
- The name "contact_read" says "read": a word for reading.
What it can reach
- private-dataThe name "contact_read" says "read" and "contact": it reads contacts.
- private-dataThe description's first sentence says "return" and "contact": it reads contacts.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- readOnlyHint: true
event_listLists the events of one type, newest first.No findings
Why it is in this group
- The name "event_list" says "list": a word for reading.
Description, as the server wrote it 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 them. - `match.needs_review` lists each contact flagged as a possible duplicate and not yet merged. Its `id` changes when the flag is raised again. Each item carries what an automation needs, with no second call: - the contact's fields, or null once the contact is deleted or merged - for a merge, the ids of the contacts it absorbed - for an account, the account and why it needs attention
Annotations the server declares
- destructiveHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__contactzapp__contact_create"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://app.contactz.app/.well-known/oauth-protected-resource/api/v1/mcp
- Authorization servers
- https://app.contactz.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://app.contactz.app/api/v1/mcp: tools/list returned 7 tools to an anonymous client, including contact_change (destructive), contact_create (write), sync_start (write)
Posture changes
- Nov 11, 2026
- RFC 9728 protected resource metadata: none to https://app.contactz.app/.well-known/oauth-protected-resource/api/v1/mcp
- Authorization servers: none to https://app.contactz.app
- Dynamic client registration: not observed to no
- Client ID metadata documents: not observed to yes
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:api_key_checkOnly readsdescription
PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://app.contactz.app/.well-known/oauth-protected-resource/api/v1/mcp; Authorization servers: none -> https://app.contactz.app; Dynamic client registration: not observ…View diff
- RFC 9728 protected resource metadata: none to https://app.contactz.app/.well-known/oauth-protected-resource/api/v1/mcp
- Authorization servers: none to https://app.contactz.app
- Dynamic client registration: not observed to no
- Client ID metadata documents: not observed to yes
Tools2 changed.~2 changedView diff
- Changed:api_key_checkOnly readsdescription
- Changed:contact_changeDeletes or cancelsdescription
Tools7 added, 10 removed.+7 added−10 removedView diff
- Added:api_key_checkOnly reads
- Added:contact_changeDeletes or cancels
- Added:contact_createChanges things
- Added:contact_findOnly reads
- Added:contact_readOnly reads
- Added:event_listOnly reads
- Added:sync_startChanges things
- Removed:createV1Contact
- Removed:createV1Webhook
- Removed:getV1Contact
- Removed:getV1Me
- Removed:listV1Accounts
- Removed:listV1Contacts
- Removed:listV1TriggerEvents
- Removed:listV1Webhooks
- Removed:postV1Sync
- Removed:updateV1Contact
Install
Pinned to version 1.0.6. Values in angle brackets are yours to fill in.
claude mcp add --transport http contactzapp https://app.contactz.app/api/v1/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http contactzapp https://app.contactz.app/api/v1/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__contactzapp__api_key_check",
"mcp__contactzapp__contact_find",
"mcp__contactzapp__contact_read",
"mcp__contactzapp__event_list"
],
"ask": [
"mcp__contactzapp__contact_create",
"mcp__contactzapp__sync_start"
],
"deny": [
"mcp__contactzapp__contact_change"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as contactzapp. Review it before you use it.
Capability tags behind 4 rules
- mcp__contactzapp__api_key_check private-data, untrusted-input
- mcp__contactzapp__contact_find private-data, untrusted-input
- mcp__contactzapp__contact_create outbound
- mcp__contactzapp__contact_read private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.contactz/contactzapp/verify?hash=78250b477f7432d725c01b1bb8f3727b4b3abede29b1ba1378693b53507b2918" | jq -e '.changed == false'Pinned hash 78250b477f74, from Nov 11, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.contactz/contactzapp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.contactz/contactzapp)Source: MCP Registry · repository. Synced Nov 11, 2026, 11:17 UTC.
ContactZapp MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ContactZapp MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ContactZapp MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: contact_change.
Can the ContactZapp MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ContactZapp MCP server have?
- 7 tools: 1 destructive, 2 write, 4 read. contact_change, contact_create, sync_start, api_key_check, contact_find, contact_read and event_list.
Does the ContactZapp MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ContactZapp MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): contact_create.
Has the ContactZapp MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.