Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

co.pixelcove/citation-tracker

REMOTE · CITATION-TRACKER.PIXELCOVE.CO · SCANNED SEP 20

Checks whether AI search engines cite your target domains for a prompt. $0.75/call via MCP.

+3 this week 75 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1069 tokens (~152/item across 7 items; 7 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 Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety50
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "citation_tracker_check" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • Manipulation not yet verified: only 7 of 8 captured unit(s) of tool text has been judged so far, so we will not certify text no model has read as clean.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the co.pixelcove/citation-tracker MCP server?

co.pixelcove/citation-tracker is a hosted endpoint at https://citation-tracker.pixelcove.co/mcp, 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 · citation-tracker.pixelcove.co

# add to Claude Code
claude mcp add --transport http co-pixelcove-citation-tracker 'https://citation-tracker.pixelcove.co/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "co-pixelcove-citation-tracker": {
      "url": "https://citation-tracker.pixelcove.co/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "co-pixelcove-citation-tracker": {
      "type": "http",
      "url": "https://citation-tracker.pixelcove.co/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.co-pixelcove-citation-tracker]
url = "https://citation-tracker.pixelcove.co/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-pixelcove-citation-tracker": {
      "type": "remote",
      "url": "https://citation-tracker.pixelcove.co/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add co-pixelcove-citation-tracker --url 'https://citation-tracker.pixelcove.co/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  co-pixelcove-citation-tracker:
    url: "https://citation-tracker.pixelcove.co/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "co-pixelcove-citation-tracker": {
      "Transport": "http",
      "Url": "https://citation-tracker.pixelcove.co/mcp"
    }
  }
}
# add to Vellum
assistant mcp add co-pixelcove-citation-tracker -t streamable-http -u 'https://citation-tracker.pixelcove.co/mcp'
// mcp.json
{
  "mcpServers": {
    "co-pixelcove-citation-tracker": {
      "type": "http",
      "url": "https://citation-tracker.pixelcove.co/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 20 Sept 2026 · Probed https://citation-tracker.pixelcove.co/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=citation-tracker.pixelcove.co CN=YR2,O=Let's Encrypt,C=US 26 Aug 2026 24 Nov 2026 RSA 2048 SHA256-RSA 553b420cd3fa1a94a10cb5a9b0b45ffb986
SANs: citation-tracker.pixelcove.co
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of citation-tracker.pixelcove.co. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
pixelcove.co. 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
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://citation-tracker.pixelcove.co/mcp Verified 200
http (plaintext) http://citation-tracker.pixelcove.co/mcp HTTPS enforced 308 https://citation-tracker.pixelcove.co/mcp
MCP tools · 7 exposed · ~1,017 tokens

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 →

Tool Tokens
citation_tracker_check ~174

Sends one prompt to 1 to 4 search assistants (Perplexity, OpenAI, Anthropic, Gemini) and reports whether each cites your target domains: cited status, citation count, cited domains, model, and a structured error per engine. Started concurrently; a failed engine returns `cited: null` and does not block the others (PD7). Paid, $0.75/call; read-only and safe to retry.

NameTypeReqDescription
enginesarrayyes1 to 4 distinct engines to check, from perplexity, openai, anthropic, gemini.
promptstringyesThe prompt to send to the search assistant(s), verbatim. 1 to 4000 characters.
targetsarrayyes1 to 10 target domains to check for a citation.

No output schema declared.

No examples provided.

citation_tracker_check_perplexity ~117

Sends one prompt to Perplexity (sonar) and reports whether it cites your target domains, with citation count and cited domains. Free: one call per caller and 100 calls total per UTC day; both limits fail closed. A real live evaluation before you pay for citation_tracker_check.

NameTypeReqDescription
promptstringyesThe prompt to send to the search assistant(s), verbatim. 1 to 4000 characters.
targetsarrayyes1 to 10 target domains to check for a citation.

No output schema declared.

No examples provided.

citation_tracker_monitor_30 ~214

Buys a monitor: 30 recurring runs of citation_tracker_check for one prompt and 1 to 10 target domains, daily or weekly. The first run happens now and is returned. Later runs are read with citation_tracker_monitor_status using the returned monitor_id (the only credential; it is not recoverable). Each run flags which target domains changed since the last run. Paid once, $18 for the term ($0.6/check); no refund of unused runs; cancel any time with citation_tracker_monitor_cancel. Retains the prompt, domains and results until 30 days after the last run or until cancelled.

NameTypeReqDescription
cadencestringyesHow often to re-run the check.
enginesarrayyes1 to 4 search assistants to run on every check.
promptstringyesThe prompt to send to the search assistant(s), verbatim. 1 to 4000 characters.
targetsarrayyes1 to 10 target domains to check for a citation.

No output schema declared.

No examples provided.

citation_tracker_monitor_7 ~216

Buys a monitor: 7 recurring runs of citation_tracker_check for one prompt and 1 to 10 target domains, daily or weekly. The first run happens now and is returned. Later runs are read with citation_tracker_monitor_status using the returned monitor_id (the only credential; it is not recoverable). Each run flags which target domains changed since the last run. Paid once, $4.2 for the term ($0.6/check); no refund of unused runs; cancel any time with citation_tracker_monitor_cancel. Retains the prompt, domains and results until 30 days after the last run or until cancelled.

NameTypeReqDescription
cadencestringyesHow often to re-run the check.
enginesarrayyes1 to 4 search assistants to run on every check.
promptstringyesThe prompt to send to the search assistant(s), verbatim. 1 to 4000 characters.
targetsarrayyes1 to 10 target domains to check for a citation.

No output schema declared.

No examples provided.

citation_tracker_monitor_cancel ~66

Stops a monitor and deletes its prompt, domains and results. Unused runs are not refunded. Free. Needs the monitor_id.

NameTypeReqDescription
monitor_idstringyesThe monitor id returned by citation_tracker_monitor_7 or _30. It is the only credential; keep it.

No output schema declared.

No examples provided.

citation_tracker_monitor_status ~86

Reads a monitor: remaining runs, next run time, and every run so far (most recent first) with the same per-engine rows as citation_tracker_check plus changed_since_last per target domain. Free. Needs the monitor_id.

NameTypeReqDescription
monitor_idstringyesThe monitor id returned by citation_tracker_monitor_7 or _30. It is the only credential; keep it.

No output schema declared.

No examples provided.

citation_tracker_shortlist_gate ~144

Checks whether ChatGPT would search the web for one prompt and whether its first search query names any of your supplied brand or product terms (whole-word match). Use it to gate a prompt before spending on citation_tracker_check. Paid, $0.20/call; read-only and safe to retry.

NameTypeReqDescription
brand_termsarrayyes1 to 20 brand terms to look for in the first search query.
product_termsarray0 to 50 product terms to look for in the first search query.
promptstringyesThe prompt to send to the search assistant(s), verbatim. 1 to 4000 characters.

No output schema declared.

No examples provided.

Common questions

What is the co.pixelcove/citation-tracker MCP server?

co.pixelcove/citation-tracker is an MCP server listed in the public MCP registry as co.pixelcove/citation-tracker. Checks whether AI search engines cite your target domains for a prompt. $0.75/call via MCP. This page covers its hosted endpoint (https://citation-tracker.pixelcove.co/mcp).

Is the co.pixelcove/citation-tracker MCP server safe to use?

co.pixelcove/citation-tracker scores 75 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 co.pixelcove/citation-tracker MCP server expose?

co.pixelcove/citation-tracker exposes 7 tools: citation_tracker_check, citation_tracker_check_perplexity, citation_tracker_shortlist_gate, citation_tracker_monitor_7, citation_tracker_monitor_30, and 2 more. Their descriptions and schemas cost roughly 1,017 tokens of context every time the server is loaded.

Does the co.pixelcove/citation-tracker MCP server require authentication?

No. We connected to co.pixelcove/citation-tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the co.pixelcove/citation-tracker MCP server still maintained?

co.pixelcove/citation-tracker is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.