Ext Ops Panel
Open dashboard
Comparison

Verimand MCP Authority Server vs ViralQuery

Verimand MCP Authority Server is an MCP server published by verimand.dev. Marketplaces we read that list it: 1 (Official MCP Registry). ViralQuery is an MCP server published by tfcbot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
MarketplaceVerimand MCP Authority ServerViralQuery
Official MCP Registry Listed
Version: 0.1.0
Downloads/month (npm): 328
Downloads/week (npm): 21
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.2.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

Verimand MCP Authority Server vs ViralQuery
FactVerimand MCP Authority ServerViralQuery
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@verimand/mcp-authority-server)Remote server (viralquery.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/verimand/mcp-authority-servergithub.com/tfcbot/viralquery-skills
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 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

Verimand MCP Authority Server

In its own words, on Official MCP Registry:

Agent-native access to verifiable VAGP authority.

ViralQuery

In its own words, on Official MCP Registry:

Protected research briefs, bounded scrolls, and private video feeds for agents.

How to run each

Verimand MCP Authority Server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcp-authority-server -- npx -y @verimand/mcp-authority-server

ViralQuery As a remote MCP server

Claude Code
claude mcp add --transport http viralquery https://viralquery.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 ViralQuery 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: Verimand MCP Authority Server · What it can do: ViralQuery · 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