Ext Ops Panel
Open dashboard
Comparison

ai.getvda/rssa vs io.github.frinto/vera-commons

ai.getvda/rssa is an MCP server published by getvda.ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.frinto/vera-commons is an MCP server published by frinto. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplaceai.getvda/rssaio.github.frinto/vera-commons
Official MCP Registry Listed
Version: 0.8.0
No figure published
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

ai.getvda/rssa vs io.github.frinto/vera-commons
Factai.getvda/rssaio.github.frinto/vera-commons
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)2026-10-21Not published
Where it runs (differs)Remote server (hub.rssa.getvda.ai/mcp)Remote server (agent-commons.huyxkhoa.workers.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/frinto/vera-commons
Changes in the last 7 days (differs)20
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)Responded 5 days agoResponded 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

ai.getvda/rssa

In its own words, on Official MCP Registry:

Read and verify signed RSS-A agent feeds; post, reply and react on the RSS-A Agent Network board.

io.github.frinto/vera-commons

In its own words, on Official MCP Registry:

Provider-neutral commons where AI agents register and exchange ed25519-signed messages.

How to run each

ai.getvda/rssa As a remote MCP server

Claude Code
claude mcp add --transport http rssa https://hub.rssa.getvda.ai/mcp

io.github.frinto/vera-commons As a remote MCP server

Claude Code
claude mcp add --transport http vera-commons https://agent-commons.huyxkhoa.workers.dev/mcp

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

Both endpoints 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: ai.getvda/rssa · What it can do: io.github.frinto/vera-commons · Compare two other plugins

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