Ir para o conteúdo
Logo de Organiq

Servidor MCP de Organiq

Quais servidores MCP são de Organiq, do registro oficial e encontrados perguntando ao próprio domínio, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.

lido em 2026-10-30

← Voltar para Organiq

De quem é o servidor
  • Nome no registrocom.organiqgeo/organiqverificado no registro MCP

O nome no registro fica sob organiqgeo.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

Quando perguntamosverificado em 2026-10-30
  • Estadorespondeverificado em 2026-10-30
  • Ferramentas44
  • O servidor se chamaorganiq
  • Versão do servidor0.3.0
  • Versão do protocolo2025-06-18

Em 2026-10-30 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 254 ms.

Um agente deve conectá-loAinda não está claro
  • As ferramentas fazem todos os casos de uso verificados: ask Claude about Search Console clicks and impressions; review CTR curves and content decay across properties; check sessions arriving from AI assistants in GA4.
  • Verificado em 6 dos 7 dias necessários para julgar a confiabilidade.

Depois de conectar

  • Para "review CTR curves and content decay across properties", a primeira chamada provável é list_sites.
  • Para "check sessions arriving from AI assistants in GA4", a primeira chamada provável é get_ai_traffic.
  • set_ga4_property, set_bing_site, set_bing_key, set_branded_terms alteram dados sem login: qualquer pessoa com o endereço pode chamá-las.
  • As definições ocupam cerca de 29093 tokens de contexto: ative só as ferramentas de que a tarefa precisa.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

Medido todo diaverificações diárias: 6, a primeira em 2026-10-30
  • Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 6 até agora
  • O que um agente consegue fazer com ele3 de 3 casos de uso
  • Uso1 estrelas no GitHub
  • Respondeumedindo6 das 7 verificações diárias necessárias para mostrar a porcentagem
  • Mediana da primeira resposta655 ms
  • Espaço no contexto do agente≈ 29.093 tokensas definições de todas as ferramentas (47), que o agente carrega a cada turno
  • Definições das ferramentasA · 100 de 100
  • Resultados tipados0 de 47 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez
  • Parâmetros sem descrição: em 1 de 47

O que um agente consegue fazer com ele

  • consegue · ask Claude about Search Console clicks and impressions
  • consegue · review CTR curves and content decay across properties
  • consegue · check sessions arriving from AI assistants in GA4

Cada caso de uso do produto foi perguntado ao Jev junto com a lista de ferramentas deste servidor: um agente consegue fazer isso com essas ferramentas?

Vale conferir

  • Ferramentas que alteram dados, em um servidor que responde sem login: set_ga4_property, set_bing_site, set_bing_key, set_branded_terms

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

Ferramentas que oferece44 ferramentas · lido em 2026-10-30
  • get_capabilities

    Returns a factual overview of this connector: what data it holds (Google Search Console synced daily into Organiq, plus GA4 referral sessions from AI assistants), the list of tools with when to use each, units, default periods, how to…

  • get_ctr_benchmark

    Returns the generic organic click-through-rate curve by Google position (1–20, fraction 0–1) used by score_opportunities and find_page_poaching_opportunities as the fallback when a property lacks its own volume, optionally interpolated…

  • check_connection

    Reports whether this request is authenticated and, if so, which Organiq account it uses (name, plan, how it authenticated), how many Search Console properties are available with their data coverage, and what is missing (no account, no…

  • list_sites

    Lists the Search Console properties synced for the signed-in account: id, siteUrl (Search Console format), displayName, tags, branded_terms (used by the brand filter), whether GA4/Bing are mapped and the data coverage (dataFrom/dataTo…

  • get_site_summary

    Totals of clicks, impressions, CTR and average position for one property over the period, with the comparison period and the change (absolute, Pct as fraction, ctrPoints in percentage points, position difference where negative means…

  • query_top_queries

    Search queries of one property over the period, aggregated and sorted. Use for "what people search to find us", growth/decline lists and ranking changes. Each row has clicks, impressions, ctr, position for the period and, with a…

  • query_top_pages

    Pages (URLs) of one property over the period, aggregated and sorted. Use for best/worst pages and pages that gained or lost clicks. Each row has clicks, impressions, ctr, position for the period and, with a comparison…

  • query_countries

    Countries (ISO-3166-1 alpha-3, lowercase, e.g. bra) of one property over the period. Each row has clicks, impressions, ctr, position for the period and, with a comparison, prevClicks/prevImpressions/prevCtr/prevPosition plus…

  • query_devices

    Devices (MOBILE, DESKTOP, TABLET) of one property over the period. Each row has clicks, impressions, ctr, position for the period and, with a comparison, prevClicks/prevImpressions/prevCtr/prevPosition plus…

  • get_timeseries

    Clicks, impressions, CTR and position per day, week (Monday as key) or month (yyyy-mm) over the period, with filters. Use for trend, seasonality and to locate the date of a drop. Days without data are omitted. / Série temporal por dia…

  • get_breakdown

    Splits the period's traffic into branded/nonBranded (by the property's branded_terms) and into position bands (1-3, 4-10, 11-20, 21+) with impressions and clicks per band, plus queryCount. Position of each query = impression-weighted…

  • get_annotations

    Events annotated in the period for the property and globally: deploys, content changes, manual notes and Google algorithm updates (category "algo_update"). Use to correlate drops or gains with causes. Default: last 90 days. / Anotações e…

  • get_ai_traffic

    Referral sessions from AI assistants (chatgpt.com, perplexity.ai, gemini, copilot, claude…) according to GA4 (dimension ai_source): per source (sessions, activeUsers, engagedSessions, keyEvents) for the period and the comparison, totals…

  • get_ctr_curve

    The property's real CTR by position (bucket = round(position), 1–20, impression-weighted) compared with the generic benchmark (31.7% at position 1 … 18.6% at 3 … 2.0% at 10). deltaPoints in percentage points (negative = below expected…

  • find_decaying_content

    Pages (or queries) that lost clicks between a BASELINE and the RECENT period. Recent = days/startDate/endDate; baseline = compare (previous = window before, year = one year earlier) or explicit comparisonStartDate/comparisonEndDate (for…

  • analyze_cannibalization

    Queries where 2+ pages of the property compete for the same search in the period. Per cluster: totals, Shannon entropy of impressions across pages (bits; higher = more even split = worse; level high >= 1.5, medium >= 1.0), normalized…

  • score_opportunities

    Queries between minPosition and maxPosition whose CTR is below the expected CTR for their position. expectedCtr comes from the property's own curve (ctrSource "own", when the bucket has volume) or from the benchmark; ctrGap = expected −…

  • find_page_poaching_opportunities

    Queries just outside the top (default positions 4–20) with the estimated click gain if they reached the CTR of the target position (default 3 → 18.6% benchmark, or the property's own CTR at that position when it has volume: see…

  • get_ranking_changes

    Classifies each query (or page) of the property by what happened between the comparison period and the current one: new (appeared), lost (disappeared), improved (position better by >= minPositionChange), declined (worse) or stable. Rows…

  • get_position_distribution

    How the property's queries spread across position bands 1-3, 4-10, 11-20 and 21+ for each day (or week) of the period: number of queries, clicks, impressions and impression share per band. Each query's position for a day is its…

  • get_branded_performance

    Daily series of branded and non-branded traffic (clicks, impressions, ctr, position per group, plus brandedClickShare) with totals for the period and the comparison, using the property's branded_terms. brandedTermsConfigured=0 means no…

  • breakdown_by_path

    Groups the property's pages by host (subdomain) and by the first `depth` path segments (1–4), e.g. "example.com/blog/*": pages per group, clicks, impressions, ctr, position, clickShare, comparison (prevClicks, clicksChange…

  • get_query_performance

    Daily performance of ONE search query on the property (optionally on one page). Returns totals for the period and the comparison with change, the daily (or weekly) series and the top counterparts (pages ranking for the query). Exact match…

  • get_page_performance

    Daily performance of ONE page (URL) of the property. Returns totals for the period and the comparison with change, the daily (or weekly) series and the top counterparts (queries bringing the page traffic). Exact match (case-insensitive…

  • get_longtail_clusters

    Splits the period's queries into head, chunky middle and long tail by word count (preset balanced: 1–2 / 3–4 / 5+ words; strict: 1 / 2–3 / 4+; loose: 1–3 / 4–5 / 6+), with queries, clicks, impressions, ctr, position, shares and top…

  • analyze_sampling_impact

    How much of the property's traffic Search Console hides from the query/page rows because of anonymization: exact totals per day (no dimensions) minus the sum of the query × page rows = hidden clicks/impressions, with hiddenShare…

  • analyze_query_shapes

    Classifies the period's queries into shapes and aggregates each: branded, question, comparison, transactional, local, longtail (5+ words), head (<= 2 words), other, with queries, clicks, impressions, ctr, position, shares, comparison…

  • get_query_shape_trend

    Weekly share of impressions (or clicks) per query shape (branded, question, comparison, transactional, local, longtail, head, other) and of "AI-style" queries over the period (default 12 weeks), with sharePointsChange = last weeks minus…

  • detect_anomalies

    Flags days in the period whose clicks (or impressions, ctr, position) deviate from what the same weekday did in the previous baselineWeeks weeks (default 8): expected = median of those weekdays, scale = scaled MAD, zScore = (value −…

  • detect_change_points

    Finds the dates where the property's clicks (or impressions) moved to a new sustained level — a step up or down that holds for several weeks, as after a Google update, a migration or a content launch — using a robust CUSUM on the weekly…

  • forecast_traffic

    Projects the property's clicks (or impressions) for the next `horizon` weeks (default 12) or months (default 6) from the history in the period (default 364 days): aggregates the daily series, estimates a multiplicative seasonal index when…

  • get_core_web_vitals

    Field Core Web Vitals of the property's origin (or a URL) from the Chrome UX Report history, weekly, per form factor (PHONE, DESKTOP): latest p75 of LCP, INP, CLS, FCP, TTFB with rating (good / needs_improvement / poor by Google's…

  • get_indexing_tracker

    Indexing status of the property's inspected URLs (Search Console URL Inspection results stored by Organiq, plus the tracked_urls watch list): healthScore 0–100 (70 % indexed share + 30 % fresh-crawl share), indexed / not indexed counts…

  • list_url_inspections

    Latest stored URL Inspection result per URL of the property: verdict, coverageState, indexingState, robotsState, pageFetchState, Google vs user canonical, lastCrawlTime, crawledAs, mobileVerdict, checkedAt and whether the URL is on the…

  • list_sitemaps

    Sitemaps known to Search Console for the property: path, lastSubmitted, lastDownloaded, isPending, errors, warnings and contents per type (web, image, video, news: submitted URL counts). Search Console no longer reports indexed counts per…

  • get_bing_performance

    Organic performance on Bing (Bing Webmaster Tools, weekly data) for the property: view=traffic gives weekly clicks/impressions with totals and change vs the previous same-length window; view=queries or view=pages gives the top keys with…

  • get_genai_impressions

    Daily impressions of the property in Google's generative AI features (AI Overviews and AI Mode) from the Search Console "Generative AI features" report, imported into Organiq (this report is not in the Search Analytics API and has no…

  • generate_seo_report

    One compact report for a property over the period (default 28 days, 7–180) with the comparison period: headline KPIs with change and year-over-year, top movers (queries and pages up/down), daily anomalies and sustained level shifts…

  • get_weekly_digest

    Short weekly digest for a property: the last 7 synced days vs the 7 before (and year-over-year), top 3 queries/pages up and down, anomalies of the week, Google updates and annotations, quick wins, technical alerts (Core Web Vitals…

  • list_ga4_properties

    Lists the Google Analytics 4 properties the connected Google account can see (Analytics Admin API accountSummaries.list): id (numeric, the value set_ga4_property takes), displayName and the GA4 account name, sorted by account. Needs an…

  • set_ga4_property

    Links a Google Analytics 4 property to one Search Console property in Organiq (the same setting as the panel's "Integrações" block): ga4PropertyId is the numeric id from list_ga4_properties ("123456789" or "properties/123456789"); null…

  • set_bing_site

    Sets the site URL registered in Bing Webmaster Tools for one Search Console property in Organiq (same rule as the panel): https, no query/fragment, and on the property's own domain (an sc-domain property accepts the domain and its…

  • set_bing_key

    Stores the Bing Webmaster Tools API key of the Organiq account (one key per account; it serves every property with a Bing site set by set_bing_site). The key is generated by the user in Bing Webmaster Tools under Settings → API access…

  • set_branded_terms

    Replaces the branded terms of one Search Console property in Organiq (the list used by the brand filter, get_breakdown, get_branded_performance and the branded shape of analyze_query_shapes): brand and product names as people type them…

Como conectar

Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:

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

Adicionar

Claude Code, no terminal

claude mcp add --transport http organiqgeo https://organiqgeo.com/mcp

Adicionar ao CursorAdicionar ao VS Code

claude.ai, ChatGPT e outros clientes: adicione https://organiqgeo.com/mcp como conector personalizado nas configurações.

Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.