Ext Ops Panel
Open dashboard
Comparison

agentkey vs io.github.seanthings/hermes-real-estate-data

agentkey is a plugin bundle for AI coding tools published by Chainbase Labs. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.seanthings/hermes-real-estate-data is an MCP server published by seanthings. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplaceagentkeyio.github.seanthings/hermes-real-estate-data
Community marketplace chainbase-labs/agentkey Listed
Version: 1.14.0
Forks (GitHub): 68
Stars (GitHub): 663
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
No figure published
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

agentkey vs io.github.seanthings/hermes-real-estate-data
Factagentkeyio.github.seanthings/hermes-real-estate-data
Marketplaces that list it11
Stars (GitHub) (differs)663No figure on GitHub
Forks (GitHub) (differs)68No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.agentkey.app/v1/mcp)Remote server (hermes-storefront.onrender.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/chainbase-labs/agentkeyNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)not checked yetAnswered with HTTP 404 (4 days ago)

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

agentkey

In its own words, on Community GitHub marketplaces:

AgentKey — one-stop live data marketplace for your agent: web search, web scraping, social media, finance, crypto, e-commerce, business data, weather/maps, and travel through a single MCP server. No API keys to manage, auto failover across providers, free to start.

io.github.seanthings/hermes-real-estate-data

In its own words, on Official MCP Registry:

Typed US real-estate feeds: deals, signals, leads. Empty is explained, never pay for a blank.

How to run each

agentkey As a Claude Code plugin

Claude Code
/plugin marketplace add chainbase-labs/agentkey
/plugin install agentkey@agentkey

io.github.seanthings/hermes-real-estate-data As a remote MCP server

Claude Code
claude mcp add --transport http hermes-real-estate-data https://hermes-storefront.onrender.com/mcp

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

Only io.github.seanthings/hermes-real-estate-data has a remote endpoint we 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: agentkey · What it can do: io.github.seanthings/hermes-real-estate-data · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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