_ registry / mcp http-sse · checked 1h ago

Q9ive Ölçüm

https://mcp.q9ive.io

Registry code: d147fecb9c04797a

api record

Q9ive Ölçüm, e-ticaret sitelerinin reklam ölçümünü kontrol eder ve yapıştırılan reklam raporlarını teşhis eder. Araçlar yalnızca okur; hiçbir şeyi değiştirmez ve raporları saklamaz. Q9ive Measure checks e-commerce sites' ad measurement and diagnoses pasted ad reports. Tools are read-only; nothing is changed and reports are not stored.

endpoint
https://mcp.q9ive.io/olcum
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Q9ive Ölçüm live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Q9ive Ölçüm free to use?
Yes — the hub reached it with no key and no payment.
What tools does Q9ive Ölçüm have?
2 tools: check_site_measurement, diagnose_ad_report.
Is Q9ive Ölçüm safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
196ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_site_measurement unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "check_site_measurementArguments",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Url"
        },
        "country": {
          "type": "string",
          "title": "Country",
          "default": ""
        },
        "language": {
          "type": "string",
          "title": "Language",
          "default": "tr"
        }
      }
    }
    arguments 23 lines
  • diagnose_ad_report unknown 1h ago

    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. 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.

    mcp-tool

    {
      "type": "object",
      "title": "diagnose_ad_reportArguments",
      "required": [
        "report_text"
      ],
      "properties": {
        "language": {
          "type": "string",
          "title": "Language",
          "default": "tr"
        },
        "platform": {
          "type": "string",
          "title": "Platform",
          "default": ""
        },
        "report_text": {
          "type": "string",
          "title": "Report Text"
        }
      }
    }
    arguments 23 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d147fecb9c04797a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d147fecb9c04797a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d147fecb9c04797a/badge.svg)](https://brick.blue/agent/d147fecb9c04797a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
5,377ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.