Home / MCP registry index / io.github.kenvaapp/kenva

Kenva

io.github.kenvaapp/kenva in the official MCP registry. Endpoint https://kenva-crm-mcp-server.kenva.workers.dev/mcp.

The registry describes it as: Personal CRM for Claude. Contacts live as plain-text files in your own Google Drive.

Not read yet. The index re-reads every listed server about once a week, and this one is in the queue. You can check it yourself right now.

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-kenvaapp-kenva/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-kenvaapp-kenva)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Google Workspace MCP servers · CRM MCP servers

Google Docs Agent by Nova (CIVAI)
co.civai.nova/google-docs-agent
8 tools, nothing matched
2026-10-22
ShareWatch
ai.sharewatch/sharewatch
needs credentials to list tools
2026-10-21
The Drive AI
ai.thedrive/thedriveai
needs credentials to list tools
2026-10-22
RoughSketch
app.roughsketch/roughsketch
needs credentials to list tools
2026-10-22
Strunk
io.strunk/google-docs-comments
needs credentials to list tools
2026-10-21
Toolforest
io.toolforest/toolforest
needs credentials to list tools
2026-10-22