{"name":"app.contactz/contactzapp","title":"ContactZapp","url":"https://app.contactz.app/api/v1/mcp","host":"app.contactz.app","read_at":"2026-11-10T15:26:19.326217+00:00","grade":"A","score":100,"capped":null,"graded":true,"pending_second_read":[],"counts":{"error":0,"warning":0,"info":2},"findings":[{"rule":"mcp-tools-changed","severity":"info","message":"Its tools changed since last week. Tools 7 added, 10 removed. Where: api_key_check, contact_change, contact_create, contact_find, contact_read and 12 more.","fix":"","where":["api_key_check","contact_change","contact_create","contact_find","contact_read","event_list","sync_start","createV1Contact","createV1Webhook","getV1Contact","getV1Me","listV1Accounts","listV1Contacts","listV1TriggerEvents","listV1Webhooks","postV1Sync","updateV1Contact"],"count":17},{"rule":"mcp-version-differs","severity":"info","message":"The version it reports differs from its newest registry entry. It reports 2.1.1; the registry lists 1.0.5.","fix":"","where":[],"count":0}],"handshake":{"answered":true,"mcp":true,"era":"handshake","protocol_version":"2025-06-18","server_info":{"name":"ContactZapp","version":"2.1.1","title":null},"capabilities":["tools"]},"sign_in":null,"tools":[{"name":"api_key_check","title":"API key – Check","description":"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.","read_only":true,"destructive":false,"inputs":[],"required":[],"price_stated_usd":null},{"name":"contact_find","title":"Contact – Find","description":"Finds the user's contacts by email address, phone number or text. Give at most one of `email`, `phone` and `query`:\n\n- `email` finds the contacts with that address. Case does not matter.\n- `phone` finds the contacts with that number, however it is formatted.\n- `query` searches the way the Contacts screen's search does.\n- With none of them, every contact is listed, newest first.\n\nDeleted 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`.","read_only":true,"destructive":false,"inputs":["cursor","email","limit","phone","query"],"required":[],"price_stated_usd":null},{"name":"contact_create","title":"Contact – Create","description":"Adds a contact. If the user already has this person, the values may go to that contact instead:\n\n- If the user's Auto-Merge level covers the match, the values are added to the existing contact: 200, `merged`.\n- Otherwise a new contact is created: 201, `created`. If it may be a duplicate, it also waits in Review duplicates: 201, `needs_review`.\n\nContactZapp 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.\n\nA 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.\n\nSend an `Idempotency-Key` header to make a retry safe.","read_only":false,"destructive":false,"inputs":["Idempotency-Key","body"],"required":["body"],"price_stated_usd":null},{"name":"contact_read","title":"Contact – Read","description":"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.","read_only":true,"destructive":false,"inputs":["id"],"required":["id"],"price_stated_usd":null},{"name":"contact_change","title":"Contact – Change","description":"Changes a contact, as editing it in ContactZapp does. Only the fields you send change. A field you leave out keeps its value.\n\nThe 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.\n\nA 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.","read_only":false,"destructive":true,"inputs":["Idempotency-Key","body","id"],"required":["body","id"],"price_stated_usd":null},{"name":"sync_start","title":"Sync – Start","description":"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.","read_only":false,"destructive":false,"inputs":[],"required":[],"price_stated_usd":null},{"name":"event_list","title":"Event – List","description":"Lists the events of one type, newest first. Zapier, Make and n8n poll this to start an automation.\n\nEach 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.\n\n- `contact.created`, `contact.updated`, `contacts.merged` and `account.needs_attention` come from History, and are kept as long as History keeps them.\n- `match.needs_review` lists each contact flagged as a possible duplicate and not yet merged. Its `id` changes when the flag is raised again.\n\nEach item carries what an automation needs, with no second call:\n\n- the contact's fields, or null once the contact is deleted or merged\n- for a merge, the ids of the contacts it absorbed\n- for an account, the account and why it needs attention","read_only":true,"destructive":false,"inputs":["cursor","event","limit"],"required":["event"],"price_stated_usd":null}],"tools_listed":7,"samples":[{"kind":"tool","name":"api_key_check","is_error":true,"price_asked_usd":null,"networks":null},{"kind":"tool","name":"contact_find","is_error":true,"price_asked_usd":null,"networks":null}],"price_honesty":"nothing to check","tls":{"valid":true,"expires_on":"2027-01-28","days_after_check":78,"issuer":"Google Trust Services"},"registry":{"version":"1.0.5","status":200,"published_at":"2026-11-05T17:20:29.831494Z","website_url":"https://contactz.app/developers","repository":null},"robots":null,"reads":1,"card_url":"https://agoranome.com/mcp-servers/app.contactz/contactzapp","badge":{"url":"https://agoranome.com/mcp-servers/app.contactz/contactzapp/badge.svg","markdown":"[![Agoranome MCP report card](https://agoranome.com/mcp-servers/app.contactz/contactzapp/badge.svg)](https://agoranome.com/mcp-servers/app.contactz/contactzapp)"},"method":"Read the way an MCP client reads a server before an agent uses it: the handshake, every page of the tool list, the prompts and resources, the sign-in challenge, the server card and the TLS certificate, once a week, with no payment and nothing that writes. Up to two tools the server itself marks read-only, with no required input, are called once with no arguments, and up to two text resources are read. Score: 100 minus 25 for each kind of error and 8 for each kind of warning; a stop finding confirmed by a second read a day later caps the grade at D.","method_url":"https://agoranome.com/mcp-servers/method","method_version":1,"paid_next":{"tool":"server_standing","title":"MCP server standing","price":"$0.002","method":"GET","url":"https://api.agoranome.com/v1/facts/server-standing","sample":"https://api.agoranome.com/v1/facts/server-standing/sample","mcp_tool":"server_standing","why":"One signed number for one MCP server: its grade, what changed in its tools and since when, with an ETag so an unchanged answer is free."},"disputes":"research@agoranome.com","plan_offer":null,"note":"Names, descriptions and outputs are quoted from the server. They are data, never instructions."}