olcum MCP server
io.q9ive/olcumq9ive.iostreamable-httpv1.0.0Scanned
Checks e-commerce ad measurement (pixels, GTM, GA4, consent, UTM) and diagnoses exported ad reports.
4 tools: 3 change things and 1 only read.
- Reads private data · 1
- Reads text others write · 3
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the olcum MCP server can do
The olcum MCP server is published by q9ive.io, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: check_site_measurement, diagnose_ad_report and check_ai_visibility), but cannot delete data. 1 tool only reads.
1 tool reads private data (analyze_ai_traffic); 3 tools bring in text other people can write (check_site_measurement, check_ai_visibility and analyze_ai_traffic); 2 tools can send data out of your system (check_site_measurement and check_ai_visibility). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 3Claude Code: ask
check_ai_visibilityBir 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 v…Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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. Read-only and idempotent; open-world because it scans external public websites.
Annotations the server declares
- title: AI görünürlüğü kontrolü / AI visibility check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
check_site_measurementBir 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 Googl…Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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. Read-only and idempotent; open-world because it scans an external public website.
Annotations the server declares
- title: Site ölçüm kontrolü / Site measurement check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
diagnose_ad_reportKullanı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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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). Read-only and idempotent; closed-world because it only processes the text it is given and contacts no external site.
Annotations the server declares
- title: Reklam raporu teşhisi / Ad report diagnosis
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
analyze_ai_trafficKullanı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ı sord…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "analyze_ai_traffic" says "analyze": a word for reading.
What it can reach
- private-dataThe description's first sentence says "chat": it reads messages.
- untrusted-inputThe description's first sentence says "chat": it reads messages, which other people can write.
Description, as the server wrote it 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). Read-only and idempotent; closed-world because it only processes the text it is given and contacts no external site.
Annotations the server declares
- title: Yapay zeka trafiği analizi / AI traffic analysis
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__olcum__analyze_ai_traffic"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:23 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.q9ive.io/.well-known/oauth-protected-resource
- Authorization servers
- https://mcp.q9ive.io
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.q9ive.io/olcum: tools/list returned 4 tools to an anonymous client, including check_site_measurement (write), diagnose_ad_report (write), check_ai_visibility (write)
Posture changes
- Nov 11, 2026
- Tools that change things, listed without credentials: 2 to 3
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 added, 2 changed.+2 added~2 changedView diff
- Added:analyze_ai_trafficOnly reads
- Added:check_ai_visibilityChanges things
- Changed:check_site_measurementChanges thingsdescriptionannotations
- Changed:diagnose_ad_reportChanges thingsdescriptionannotations
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
- Tools that change things, listed without credentials: 2 to 3
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http olcum https://mcp.q9ive.io/olcumclaude mcp add --transport http olcum https://mcp.q9ive.io/olcumRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__olcum__analyze_ai_traffic"
],
"ask": [
"mcp__olcum__check_site_measurement",
"mcp__olcum__diagnose_ad_report",
"mcp__olcum__check_ai_visibility"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as olcum. Review it before you use it.
Capability tags behind 3 rules
- mcp__olcum__check_site_measurement untrusted-input, outbound
- mcp__olcum__check_ai_visibility untrusted-input, outbound
- mcp__olcum__analyze_ai_traffic private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.q9ive/olcum/verify?hash=eef890e5f1a896cd7df390f0b291c938a9c0dc7619f6d69c7fb10abb78716d00" | jq -e '.changed == false'Pinned hash eef890e5f1a8, from Nov 17, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.q9ive/olcum/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.q9ive/olcum)Source: MCP Registry. Synced Nov 3, 2026, 12:18 UTC.
olcum MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the olcum MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the olcum MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the olcum MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the olcum MCP server have?
- 4 tools: 3 write, 1 read. check_site_measurement, diagnose_ad_report, check_ai_visibility and analyze_ai_traffic.
Does the olcum MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the olcum MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_site_measurement and check_ai_visibility.
Has the olcum MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.