RRepoGEO

REPOGEO REPORT · LITE

Dicklesworthstone/mcp_agent_mail

Default branch main · commit 0fd616a0 · scanned 5/18/2026, 1:41:48 AM

GitHub: 1,948 stars · 203 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
28 /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
2 / 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 Dicklesworthstone/mcp_agent_mail, 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
    Reposition the README's opening to clarify 'FastMCP' and target audience

    Why:

    CURRENT
    A mail-like coordination layer for coding agents, exposed as an HTTP-only FastMCP server.
    COPY-PASTE FIX
    A mail-like coordination layer specifically for *AI coding agents*, exposed as an HTTP-only FastMCP server (a lightweight, agent-focused protocol, *not* Minecraft Protocol).
  • mediumhomepage#2
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    Add a relevant URL for the project's homepage (e.g., a GitHub Pages site, documentation, or project landing page).
  • mediumlicense#3
    Clarify the existing license in the README

    Why:

    COPY-PASTE FIX
    Add a section or sentence in the README stating: 'This project is released under the terms specified in the [LICENSE](LICENSE) file, which outlines the specific conditions for use and distribution.'

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 Dicklesworthstone/mcp_agent_mail
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Apache Kafka
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Apache Kafka · recommended 2×
  2. RabbitMQ · recommended 2×
  3. PostgreSQL · recommended 2×
  4. Git · recommended 1×
  5. Git LFS · recommended 1×
  • CATEGORY QUERY
    How can multiple AI agents coordinate work and avoid conflicts on shared files?
    you: not recommended
    AI recommended (in order):
    1. Git
    2. Git LFS
    3. GitPython
    4. DVC
    5. S3
    6. Google Cloud Storage
    7. Azure Blob Storage
    8. MLflow
    9. Apache Kafka
    10. RabbitMQ
    11. AWS SQS
    12. confluent-kafka-python
    13. Redis
    14. Memcached
    15. redis-py
    16. Kubernetes
    17. PostgreSQL
    18. MongoDB
    19. psycopg2
    20. pymongo

    AI recommended 20 alternatives but never named Dicklesworthstone/mcp_agent_mail. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a communication layer for AI agents with identity, inbox, and message search.
    you: not recommended
    AI recommended (in order):
    1. XMPP
    2. sleekxmpp
    3. smack
    4. Prosody
    5. ejabberd
    6. Apache Kafka
    7. RabbitMQ
    8. Elasticsearch
    9. Matrix
    10. Synapse
    11. Dendrite
    12. Redis Pub/Sub
    13. RedisJSON
    14. RediSearch
    15. gRPC
    16. PostgreSQL

    AI recommended 16 alternatives but never named Dicklesworthstone/mcp_agent_mail. 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 Dicklesworthstone/mcp_agent_mail?
    pass
    AI named Dicklesworthstone/mcp_agent_mail explicitly

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

  • If a team adopts Dicklesworthstone/mcp_agent_mail in production, what risks or prerequisites should they evaluate first?
    pass
    AI did not name Dicklesworthstone/mcp_agent_mail — likely talking about a different project

    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 Dicklesworthstone/mcp_agent_mail solve, and who is the primary audience?
    pass
    AI named Dicklesworthstone/mcp_agent_mail 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 Dicklesworthstone/mcp_agent_mail. 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/Dicklesworthstone/mcp_agent_mail.svg)](https://repogeo.com/en/r/Dicklesworthstone/mcp_agent_mail)
HTML
<a href="https://repogeo.com/en/r/Dicklesworthstone/mcp_agent_mail"><img src="https://repogeo.com/badge/Dicklesworthstone/mcp_agent_mail.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

Dicklesworthstone/mcp_agent_mail — 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