Home / MCP registry index / com.organiqgeo/organiq

Organiq

com.organiqgeo/organiq in the official MCP registry. Endpoint https://organiqgeo.com/mcp. Source: github.com/organiqgeo/organiq-plugin.

The registry describes it as: Search Console and GA4 analysis (read-only Google): queries, decay, cannibalization, AI traffic.

We read its 44 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

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 organiq https://organiqgeo.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "organiq": {
      "url": "https://organiqgeo.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"organiq","type":"http","url":"https://organiqgeo.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.

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.

Install lazaretto-guard

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

Tools it advertises

get_capabilities get_ctr_benchmark check_connection list_sites get_site_summary query_top_queries query_top_pages query_countries query_devices get_timeseries get_breakdown get_annotations get_ai_traffic get_ctr_curve find_decaying_content analyze_cannibalization score_opportunities find_page_poaching_opportunities get_ranking_changes get_position_distribution get_branded_performance breakdown_by_path get_query_performance get_page_performance get_longtail_clusters analyze_sampling_impact analyze_query_shapes get_query_shape_trend detect_anomalies detect_change_points forecast_traffic get_core_web_vitals get_indexing_tracker list_url_inspections list_sitemaps get_bing_performance get_genai_impressions generate_seo_report get_weekly_digest list_ga4_properties set_ga4_property set_bing_site set_bing_key set_branded_terms

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-10-31): cb5c56731c8659aa. 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:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-organiqgeo-organiq/badge.svg)](https://lazaretto.dev/mcp-registry/com-organiqgeo-organiq)

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.