io.q9ive/olcum
REMOTE · MCP.Q9IVE.IO
Checks e-commerce ad measurement (pixels, GTM, GA4, consent, UTM) and diagnoses exported ad reports.
Available components
Last scanned (2 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1696 tokens (~424/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +4
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: Q9ive Ölçüm → Q9ive security
- Tool “diagnose_ad_report” rewrote its description, which is the text the model reads security
- Schema quality: 276 → 424 ▼ functional
- First check of Schema quality: 100 functional
- New prompt “ad_report_diagnosis” functional
- New prompt “ai_traffic_funnel” functional
- New prompt “ai_visibility” functional
- New prompt “site_measurement” functional
- New tool “analyze_ai_traffic” functional
- New tool “check_ai_visibility” functional
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.q9ive.io/olcum
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.q9ive.io | CN=YE1,O=Let's Encrypt,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 56071cb1ef11095b8a814cc77507710c483 |
| SANs: mcp.q9ive.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.q9ive.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| q9ive.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.q9ive.io/olcum | Verified | 200 | |
| http (plaintext) | http://mcp.q9ive.io/olcum | HTTPS enforced | 301 | https://mcp.q9ive.io/olcum |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_ai_traffic Yapay zeka trafiği analizi / AI traffic analysis ~433
Kullanıcı bir analitik ya da trafik raporu paylaşıp yapay zekadan (ChatGPT, Perplexity, Gemini…) siteye ne kadar trafik geldiğini ya da bu ziyaretçilerin satın alıp almadığını sorduğunda kullanılır. Analitik aracından (GA4, Yandex Metrica, Matomo, Adobe ya da mağaza paneli) dışa aktarılan trafik kaynağı ya da kanal raporundan, sitenin yapay zeka asistanlarından (ChatGPT, Perplexity, Gemini, Copilot, Claude ve diğerleri) ne kadar trafik aldığını, hangi asistandan geldiğini, bu ziyaretlerin etkileşim ve dönüşüm oranını, gelirini ve sepete ekleme, ödeme ve satın alma hunisindeki en büyük kaybı sitenin geneliyle karşılaştırır. Raporu dışa aktarıldığı haliyle, ham CSV metni olarak report_text alanına verin. Giriş gerektirmez; rapor saklanmaz (format desteğini geliştirmek için yalnızca tanınmayan raporların sütun başlıkları kaydedilebilir). Use when the user shares an analytics or traffic report and asks how much traffic comes from AI (ChatGPT, Perplexity, Gemini…) or whether those visitors buy. From a traffic source or channel report exported from an analytics tool (GA4, Yandex Metrica, Matomo, Adobe or a store panel), shows how much traffic the site gets from AI assistants (ChatGPT, Perplexity, Gemini, Copilot, Claude and others), which assistant it comes from, and the engagement rate, conversion rate, revenue and add-to-cart, checkout and purchase funnel (with the biggest drop-off) of those visits compared with the site overall. Pass the report exactly as exported, as raw CSV text, in report_text. No sign-in; the report is not stored (only column headers of unrecognized reports may be logged to improve format support).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| report_text | string | yes | – |
No output schema declared.
No examples provided.
check_ai_visibility AI görünürlüğü kontrolü / AI visibility check ~266
Bir e-ticaret sitesinin yapay zeka asistanlarında (ChatGPT, Claude, Perplexity, Gemini, Copilot) bulunmaya ve ölçülmeye hazır olup olmadığını kontrol eder: robots.txt'de AI arama ve eğitim tarayıcılarına izin, ürün sayfasında yapılandırılmış ürün verisi (ad, görsel, fiyat, stok, marka, ürün kodu, yorum puanı), llms.txt ve site haritası, ChatGPT'den gelen ziyaretlerin işaretlerinin yönlendirmede korunması. Giriş gerektirmez; yalnızca herkese açık sayfaları ve robots.txt'yi okur. Checks whether an e-commerce site is ready to be found and measured in AI assistants (ChatGPT, Claude, Perplexity, Gemini, Copilot): AI search and training crawlers allowed in robots.txt, structured product data on a product page (name, image, price, stock, brand, product code, rating), llms.txt and sitemap, and whether ChatGPT visit markers survive redirects. No sign-in; reads only public pages and robots.txt.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| language | string | – | – |
| product_url | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
check_site_measurement Site ölçüm kontrolü / Site measurement check ~217
Bir e-ticaret sitesinin reklam ölçümünü kontrol eder: Meta Pixel, Google Ads, TikTok Pixel, ChatGPT Ads ve LinkedIn etiketleri, Google Tag Manager ve GA4, çerez onay aracı ve Google Consent Mode, çift yüklenen etiketler ve yönlendirmelerde UTM, gclid, fbclid, ttclid ve oppref işaretlerinin korunması. Giriş gerektirmez; yalnızca herkese açık ana sayfayı okur ve robots.txt kurallarına uyar. Checks an e-commerce site's ad measurement: Meta Pixel, Google Ads, TikTok Pixel, ChatGPT Ads and LinkedIn tags, GTM and GA4, consent tool and Google Consent Mode, duplicate tags, and whether redirects keep UTM, gclid, fbclid, ttclid and oppref. No sign-in; reads only the public home page and respects robots.txt.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| language | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
diagnose_ad_report Reklam raporu teşhisi / Ad report diagnosis ~354
Kullanıcı reklam panelinden aldığı bir kampanya raporunu paylaşıp kampanyalarının performansını, satış getirmeyen harcamayı ya da ölçüm hatalarını sorduğunda kullanılır. Meta Ads, Google Ads, TikTok Ads ya da ChatGPT Ads panelinden dışa aktarılan kampanya raporunu teşhis eder: satış ya da dönüşüm getirmeyen harcamayı, ilk bakılması gereken kampanyayı ve nedenini, günlük kırılım varsa son 7 günün gidişatını gösterir. Raporu dışa aktarıldığı haliyle, ham CSV metni olarak report_text alanına verin; tabloya çevirmeyin ve sütun çıkarmayın. Giriş gerektirmez; rapor saklanmaz, yalnızca bu istek için işlenir (format desteğini geliştirmek için yalnızca tanınmayan raporların sütun başlıkları kaydedilebilir). Use when the user shares a campaign report from an ad panel and asks about campaign performance, spend without sales or measurement errors. Diagnoses a campaign report exported from Meta Ads, Google Ads, TikTok Ads or ChatGPT Ads: spend without sales or conversions, the campaign to look at first and why, and the last 7 days' trend when a daily breakdown is included. Pass the report exactly as exported, as raw CSV text, in report_text; don't convert it to a table or drop columns. No sign-in; the report is not stored (only column headers of unrecognized reports may be logged to improve format support).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| platform | string | – | – |
| report_text | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.q9ive/olcum MCP server?
io.q9ive/olcum is a hosted endpoint at https://mcp.q9ive.io/olcum, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.q9ive.io
claude mcp add --transport http io-q9ive-olcum 'https://mcp.q9ive.io/olcum'
What is the io.q9ive/olcum MCP server?
io.q9ive/olcum is an MCP server listed in the public MCP registry as io.q9ive/olcum. Checks e-commerce ad measurement (pixels, GTM, GA4, consent, UTM) and diagnoses exported ad reports. This page covers its hosted endpoint (https://mcp.q9ive.io/olcum).
Is the io.q9ive/olcum MCP server safe to use?
io.q9ive/olcum scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.q9ive/olcum MCP server expose?
io.q9ive/olcum exposes 4 tools: check_site_measurement, diagnose_ad_report, check_ai_visibility, analyze_ai_traffic. Their descriptions and schemas cost roughly 1,270 tokens of context every time the server is loaded.
Does the io.q9ive/olcum MCP server require authentication?
No. We connected to io.q9ive/olcum without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.q9ive/olcum MCP server still maintained?
io.q9ive/olcum is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.