Werify

app.werifyPublished by werify.appOfficial publisherv1.0.0Updated Oct 30, 2026

Your WhatsApp history in Claude and ChatGPT: search years of chats, voice notes transcribed.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that brings your WhatsApp chat history into Claude and ChatGPT, with search across years of chats and transcribed voice notes.

What you can do
  • Search your WhatsApp chat history across years of conversations.
  • Retrieve voice notes with their transcriptions.
  • Bring WhatsApp message context into Claude and ChatGPT sessions.
  • No tool list is published, so the exact operations are not documented.
When to use it
Useful when you want an assistant to recall or search what was said in your WhatsApp conversations, for example to find an old message, a shared detail, or the content of a voice note.
Requirements
A remote MCP endpoint at werify.app using streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared. A WhatsApp account whose history is connected to the service is implied.
Before you install
Connecting your WhatsApp history gives the service and the assistant access to private conversations, including transcribed voice notes. Access is granted through OAuth, so review the scopes and permissions requested. Consider whether chat data is sent to third parties and how it is stored.

Installation

In SourceWeft

  1. Open Werify in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.werify%2Fwerify/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "werify": {
      "type": "http",
      "url": "https://werify.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 30, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.