Home / MCP registry index / io.github.mridang/chowdown

chowdown

io.github.mridang/chowdown in the official MCP registry. Endpoint https://chowdown.apps.mrida.ng/mcp. Source: github.com/mridang/chowdown.

The registry describes it as: Your recipes as plain files in your own Google Drive, searchable by your AI assistant.

On 2026-10-31 this server asked for credentials before it would list its tools, so we could not read them. Nothing was checked: this is not a clean result.

Connect it

The endpoint is live and asks for credentials before it lists its tools. Add it to your client:

Claude Code
claude mcp add --transport http chowdown https://chowdown.apps.mrida.ng/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "chowdown": {
      "url": "https://chowdown.apps.mrida.ng/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"chowdown","type":"http","url":"https://chowdown.apps.mrida.ng/mcp"}'

Most clients open the server's sign-in page the first time they connect. If it wants an API key instead, the server's own docs say where to put it.

Check its tools after you sign in

We could not read this server's tools without an account, so nothing above says they are clean. Once you are signed in, your agent can pass the tool list it received to the check_mcp_tools tool on our MCP server, which runs the same tool-poisoning rules. A free developer key covers 10 checks a day, and your agent can get one in the same session with get_free_key. No account or card.

Add Lazaretto to Claude Code
claude mcp add --transport http lazaretto https://lazaretto.dev/mcp

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-mridang-chowdown/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mridang-chowdown)

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

Google_docs
io.github.pipeworx-io/google_docs
48 tools, nothing matched
2026-10-27
Google_drive
io.github.pipeworx-io/google_drive
47 tools, nothing matched
2026-10-27
Google Docs Agent by Nova (CIVAI)
co.civai.nova/google-docs-agent
8 tools, nothing matched
2026-10-22
Developer Tools
goog.workspace-developer/developer-tools
2 tools, nothing matched
2026-10-28
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