RRepoGEO

REPOGEO REPORT · LITE

weiesky/cc-viewer

Default branch main · commit dbf8de5c · scanned 6/14/2026, 11:11:46 AM

GitHub: 985 stars · 118 forks

AI VISIBILITY SCORE
35 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface weiesky/cc-viewer, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Update README's H1 and opening paragraph for clarity

    Why:

    CURRENT
    # CC-Viewer

Based on Claude Code, a Vibe Coding tool that distills and accumulates real development experience:
    COPY-PASTE FIX
    # CC-Viewer: Real-time API Monitoring for AI Coding Assistants

CC-Viewer is a request monitoring system specifically designed for AI coding assistants like Claude Code. It captures and visualizes all API requests and responses in real time, helping developers monitor their context for reviewing and debugging during Vibe Coding.
  • hightopics#2
    Add relevant topics to improve categorization

    Why:

    COPY-PASTE FIX
    ai-coding-assistant, claude-code, api-monitoring, debugging-tool, real-time-monitoring, llm-development, vibe-coding, privacy-tool, multi-model
  • mediumreadme#3
    Add a 'Key Differentiators' section to highlight unique value

    Why:

    COPY-PASTE FIX
    ## Key Differentiators

Unlike general network proxies, CC-Viewer is purpose-built for AI coding assistants. It enables local monitoring to protect your project code privacy, offers comprehensive API logging and analysis for debugging, and supports hot-swapping between various third-party LLM models like Deepseek, GLM, and Kimi.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface weiesky/cc-viewer
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Proxyman
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Proxyman · recommended 1×
  2. Charles Proxy · recommended 1×
  3. Fiddler Everywhere · recommended 1×
  4. mitmproxy · recommended 1×
  5. Wireshark · recommended 1×
  • CATEGORY QUERY
    How can I monitor and debug my AI coding assistant's API requests locally for privacy?
    you: not recommended
    AI recommended (in order):
    1. Proxyman
    2. Charles Proxy
    3. Fiddler Everywhere
    4. mitmproxy
    5. Wireshark
    6. Postman

    AI recommended 6 alternatives but never named weiesky/cc-viewer. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Tools to enhance AI coding assistants with comprehensive API logging, analysis, and multi-model compatibility?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LiteLLM
    3. Helicone
    4. OpenTelemetry
    5. Weights & Biases
    6. Portkey.ai

    AI recommended 6 alternatives but never named weiesky/cc-viewer. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of weiesky/cc-viewer?
    pass
    AI named weiesky/cc-viewer explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts weiesky/cc-viewer in production, what risks or prerequisites should they evaluate first?
    pass
    AI named weiesky/cc-viewer explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo weiesky/cc-viewer solve, and who is the primary audience?
    pass
    AI named weiesky/cc-viewer explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of weiesky/cc-viewer. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/weiesky/cc-viewer.svg)](https://repogeo.com/en/r/weiesky/cc-viewer)
HTML
<a href="https://repogeo.com/en/r/weiesky/cc-viewer"><img src="https://repogeo.com/badge/weiesky/cc-viewer.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

weiesky/cc-viewer — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite