_ registry / mcp streamable-http · checked 12h ago

citemark

https://citemark.io

Registry code: 17ffbaba38aac654

api record

Citemark checks how AI assistants talk about software products: check_ai_visibility asks ChatGPT and Claude buyer questions about a product's category and reports whether the product is named; get_ai_picks lists which products AI recommends most in a software category; check_ai_crawlers reports which AI crawlers a website's robots.txt allows. With the user's Citemark account connected, start_tracking tracks a website over time and get_my_tracking summarizes the results.

endpoint
https://citemark.io/mcp
protocol
streamable-http ·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 citemark live?
Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
Is citemark free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does citemark have?
5 tools: check_ai_visibility, get_ai_picks, check_ai_crawlers, start_tracking, get_my_tracking.
Is citemark 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
905ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 2 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 auth-required 4 never probed 1 of 5 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.

  • get_my_tracking auth-required 12h ago

    Summarizes the websites the user tracks in their Citemark account: for each, how often AI assistants named it in the last 7 days, the competitor named most, and a link to its dashboard. Needs the user's Citemark account.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "website": {
          "type": "string",
          "description": "Optional: only this tracked website, like acme.com."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • check_ai_visibility unknown 38h ago

    Checks whether ChatGPT and Claude recommend a product when people ask which tool to use. It reads the product's homepage, writes 5 questions a buyer in its category would ask, asks each AI, and reports how often the product is named and in what position, which competitors are named instead, which websites the answers cite, three suggested fixes, and a link to the full shareable report. Takes about a minute. A site checked in the last 7 days returns that report instead of asking again.

    mcp-tool

    {
      "type": "object",
      "required": [
        "website"
      ],
      "properties": {
        "website": {
          "type": "string",
          "description": "The product's website, like acme.com (a full URL works too)."
        },
        "category": {
          "type": "string",
          "description": "Optional: what kind of product it is, like 'uptime monitoring tool'. Read from the homepage when left out."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • get_ai_picks unknown 12h ago

    Returns the products ChatGPT, Gemini and Claude recommend most in a software category, ranked by how often they are named across a fixed set of buyer questions that Citemark asks every two weeks, with each product's share of answers and average position.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category"
      ],
      "properties": {
        "category": {
          "enum": [
            "screenshot-apis",
            "transactional-email",
            "product-analytics",
            "privacy-friendly-analytics",
            "uptime-monitoring",
            "error-tracking",
            "feature-flags",
            "form-builders",
            "newsletter-platforms",
            "ai-coding-assistants"
          ],
          "type": "string",
          "description": "The software category: screenshot-apis (Screenshot APIs), transactional-email (Transactional email services), product-analytics (Product analytics tools), privacy-friendly-analytics (Privacy-friendly web analytics), uptime-monitoring (Uptime monitoring tools), error-tracking (Error tracking tools), feature-flags (Feature flag tools), form-builders (Online form builders), newsletter-platforms (Newsletter platforms), ai-coding-assistants (AI coding assistants)."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • check_ai_crawlers unknown 12h ago

    Reads a website's robots.txt and reports which of 15 AI crawlers (from OpenAI, Anthropic, Google, Apple, Meta and others) may crawl its homepage, separating bots that fetch pages for AI answers from bots that collect training data, plus the robots.txt lines that would let blocked answer bots in.

    mcp-tool

    {
      "type": "object",
      "required": [
        "website"
      ],
      "properties": {
        "website": {
          "type": "string",
          "description": "The product's website, like acme.com (a full URL works too)."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • start_tracking unknown never probed

    Starts tracking a website in the user's Citemark account: sets up the questions buyers ask AI about its category and the competitors to compare it with, then asks AI assistants those questions on the account's schedule and shows the results on the Citemark dashboard. Needs the user's Citemark account; Claude asks them to connect it the first time. Does nothing if the website is already tracked.

    mcp-tool

    {
      "type": "object",
      "required": [
        "website"
      ],
      "properties": {
        "website": {
          "type": "string",
          "description": "The product's website, like acme.com (a full URL works too)."
        },
        "category": {
          "type": "string",
          "description": "Optional: what kind of product it is, like 'uptime monitoring tool'. Read from the homepage when left out."
        }
      },
      "additionalProperties": false
    }
    arguments 17 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 17ffbaba38aac654.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/17ffbaba38aac654/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/17ffbaba38aac654/badge.svg)](https://brick.blue/agent/17ffbaba38aac654?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
90%

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
0
ok
0
failed
0
success rate
—
median latency
—
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
—

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