Organiq
MCP server · organiqgeo.com · found in a public list · checked since 2026-10-31
Live, handshake completed · latest check
Analyses Search Console and GA4 data: cannibalisation, query shapes, decay and AI traffic.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in SEO data: keywords, rankings and backlinks: Keyword volumes, search rankings, backlinks, domain authority, indexing and Search Console data.
https://organiqgeo.com/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Details
Tools listed by the server
analyze_cannibalizationanalyze_query_shapesanalyze_sampling_impactbreakdown_by_pathcheck_connectiondetect_anomaliesdetect_change_pointsfind_decaying_contentfind_page_poaching_opportunitiesforecast_trafficgenerate_seo_reportget_ai_trafficget_annotationsget_bing_performanceget_branded_performanceget_breakdownget_capabilitiesget_core_web_vitalsget_ctr_benchmarkget_ctr_curveget_genai_impressionsget_indexing_trackerget_longtail_clustersget_page_performanceget_position_distributionget_query_performanceget_query_shape_trendget_ranking_changesget_site_summaryget_timeseriesget_weekly_digestlist_ga4_propertieslist_sitemapslist_siteslist_url_inspectionsquery_countriesquery_devicesquery_top_pagesquery_top_queriesscore_opportunities+4
- Tools
- 44
- This list since
- 2026-10-31
- First listed to us
- 2026-10-31
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- promptstools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
get_capabilities languageget_ctr_benchmark position impressionscheck_connectionlist_sites includeHiddenget_site_summary site* days startDate endDate compare searchType country device brand pageContains queryquery_top_queries site* days startDate endDate compare searchType country device brand pageContains query limit sort minImpressionsquery_top_pages site* days startDate endDate compare searchType country device brand pageContains query limit sort minImpressionsquery_countries site* days startDate endDate compare searchType country device brand pageContains query limit sort minImpressionsquery_devices site* days startDate endDate compare searchType country device brand pageContains query limit sort minImpressionsget_timeseries site* days startDate endDate searchType country device brand pageContains query granularityget_breakdown site* days startDate endDate searchType country device brand pageContains queryget_annotations site* days startDate endDate
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Web access and automation / Website analysis / SEO data (primary); Web access and automation / Website analysis / Website traffic analytics. Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-31. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:MIA |
Live, handshake completed HTTP 200 | 424 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_2fb02e8e21bdd388