Home / MCP registry index / in.upgrowth/growth-toolkit

upGrowth Growth Toolkit

in.upgrowth/growth-toolkit in the official MCP registry. Endpoint https://upgrowth.in/connected-app/mcp. Source: github.com/upGrowth-in/upgrowth-growth-toolkit.

The registry describes it as: 29 free read-only growth tools: CAC, ROAS, PPC, schema, meta tags, robots.txt and AI crawler checks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http growth-toolkit https://upgrowth.in/connected-app/mcp

{
  "mcpServers": {
    "growth-toolkit": {
      "url": "https://upgrowth.in/connected-app/mcp"
    }
  }
}

code --add-mcp '{"name":"growth-toolkit","type":"http","url":"https://upgrowth.in/connected-app/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

unit_economics growth_rate roas_check ad_budget_planner find_growth_moves max_affordable_cac period_change seo_roi ai_crawler_access_check mdr_charges robots_txt_generator schema_generator content_seo_check meta_tags_builder youtube_earnings instagram_earnings engagement_rate website_ad_revenue ytd_growth ppc_forecast customer_lifetime_value ecommerce_metrics growth_projection acos_check share_of_voice break_even campaign_roi attrition_rate book_strategy_call

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): 8dfad3969bf318a3. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/in-upgrowth-growth-toolkit/badge.svg)](https://lazaretto.dev/mcp-registry/in-upgrowth-growth-toolkit)

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

Web scraping MCP servers