Home / MCP registry index / io.github.leanrads/leanriq

LeanrIQ

io.github.leanrads/leanriq in the official MCP registry. Endpoint https://iq.leanrads.com/mcp. Source: github.com/leanrads/LeanrIQ.

The registry describes it as: Creative-intelligence MCP for campaign strategy, ad builds, QA, and reporting.

We read its 136 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

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

Claude Code

claude mcp add --transport http leanriq https://iq.leanrads.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "leanriq": {
      "url": "https://iq.leanrads.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"leanriq","type":"http","url":"https://iq.leanrads.com/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. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

get_current_user list_accessible_seats get_current_seat get_permissions get_capabilities get_leanriq_capabilities get_media_buy_delivery list_advertisers get_advertiser create_advertiser update_advertiser archive_advertiser get_brand_profile refresh_brand_profile get_brand_visuals refresh_brand_visuals list_competitors run_competitor_intelligence get_competitor_intelligence list_competitor_evidence run_creative_intelligence get_creative_intelligence_run get_creative_intelligence create_creative_intelligence_plan get_world_activation_evidence get_world_research_profile get_world_research_summary get_world_research_events get_world_research_event get_world_research_mentions get_world_research_insights get_world_research_proposal get_world_research_decision get_world_research_question build_world_research_profile record_world_research_feedback run_world_intelligence get_world_intelligence list_world_signals list_world_opportunities get_world_opportunity get_vertical_intelligence list_campaigns get_campaign create_campaign update_campaign archive_campaign select_world_opportunity_for_campaign create_creative_brief create_production_plan build_videoad qa_creative run_creative_chain launch_creative_campaign promote_creative_workspace list_creatives get_creative build_ad build_dooh build_campaign_creative_set and 76 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

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

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.