Ext Ops Panel
Open dashboard
Comparison

BittleBits GEO Assistant vs Citedy SEO Agent

BittleBits GEO Assistant is an MCP server published by bittlebits.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Citedy SEO Agent is an MCP server published by nttylock. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceBittleBits GEO AssistantCitedy SEO Agent
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.2.0
Forks (GitHub): 7
Stars (GitHub): 20
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

BittleBits GEO Assistant vs Citedy SEO Agent
FactBittleBits GEO AssistantCitedy SEO Agent
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)20 (better)
Forks (GitHub) (differs)0 (worse)7 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (bittlebits.ai/mcp)Remote server (mcp.citedy.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/bittlebitsai/bittlebits-plugingithub.com/citedy/citedy-seo-agent
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: no HTTP response at the last check 43 h agoStatus out of date: last check 46 h ago returned HTTP 200

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

BittleBits GEO Assistant

In its own words, on Official MCP Registry:

GEO scores and content-rewrite suggestions for any web page, as MCP tools.

Citedy SEO Agent

In its own words, on Official MCP Registry:

AI marketing: SEO articles, trend scouting, competitor analysis, social media, lead magnets

How to run each

BittleBits GEO Assistant As a remote MCP server

Claude Code
claude mcp add --transport http bittlebits https://bittlebits.ai/mcp

Citedy SEO Agent As a remote MCP server

Claude Code
claude mcp add --transport http citedy-seo-agent https://mcp.citedy.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of Citedy SEO Agent responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: BittleBits GEO Assistant · What it can do: Citedy SEO Agent · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built