Zyphe
com.zyphePublished by zyphe.comOfficial publisherv1.14.1Updated Oct 24, 2026
Run KYB and AML case reviews and configure Zyphe verification flows, forms and API keys.
Overview
Zyphe's remote MCP server lets an assistant run KYB and AML case reviews and configure Zyphe verification flows, forms and API keys.
- What you can do
- Run KYB and AML case reviews through the Zyphe platform, with the assistant handling review work on connected cases. Configure verification flows and forms used in Zyphe onboarding and compliance checks. Manage API keys and bot access for the organization's Zyphe account. Access is authenticated with a bot token issued from the Zyphe dashboard or created through the bots API.
- When to use it
- Useful when a team already uses Zyphe for business verification or anti-money-laundering checks and wants an assistant to work with cases, flows and forms directly instead of switching to the dashboard. Less relevant if you do not have a Zyphe organization account.
- Requirements
- A remote MCP endpoint at api.zyphe.com over streamable HTTP, with OAuth authentication. An Authorization header carrying a Zyphe bot token is required; the token is issued from the Bots page of the Zyphe dashboard or created through the organizations bots API. A Zyphe organization account is implied.
Installation
In SourceWeft
- Open Zyphe in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/com.zyphe%2Fzyphe-mcp/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"zyphe": {
"type": "http",
"url": "https://api.zyphe.com/mcp"
}
}
}Tools
0Version history
1- v1.14.1LatestSep 16, 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.