Ext Ops Panel
Open dashboard
Comparison

UXUS Agent Services: wallet lookup, entity labels, caller ID vs bridge-watch on-chain intelligence

UXUS Agent Services: wallet lookup, entity labels, caller ID is an MCP server published by Dcroyalty. Marketplaces we read that list it: 1 (Official MCP Registry). bridge-watch on-chain intelligence is an MCP server published by agentsapi.top. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceUXUS Agent Services: wallet lookup, entity labels, caller IDbridge-watch on-chain intelligence
Official MCP Registry Listed
Version: 1.4.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.3.1
Downloads/month (npm): 416
Downloads/week (npm): 416
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

UXUS Agent Services: wallet lookup, entity labels, caller ID vs bridge-watch on-chain intelligence
FactUXUS Agent Services: wallet lookup, entity labels, caller IDbridge-watch on-chain intelligence
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-10-16Not published
Where it runs (differs)Remote server (uxus.finance/api/mcp)Remote server (agentsapi.top/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/dcroyalty/cryptorisk-apigithub.com/lakesky/bridge-watch-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
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

UXUS Agent Services: wallet lookup, entity labels, caller ID

In its own words, on Official MCP Registry:

Free wallet lookup, ENS, labels, caller ID. Paid x402: search, scrape, XRP yield and lending grades

bridge-watch on-chain intelligence

In its own words, on Official MCP Registry:

Base on-chain address labels (eth-labels 104k category tags), tx explainer, clusters, CCTP USDC.

How to run each

UXUS Agent Services: wallet lookup, entity labels, caller ID As a remote MCP server

Claude Code
claude mcp add --transport http uxus https://uxus.finance/api/mcp

bridge-watch on-chain intelligence As a remote MCP server

Claude Code
claude mcp add --transport http bridge-watch https://agentsapi.top/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 the marketplaces of bridge-watch on-chain intelligence nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of UXUS Agent Services: wallet lookup, entity labels, caller ID publish no settings it asks for, so we do not compare settings.

What it can do: UXUS Agent Services: wallet lookup, entity labels, caller ID · What it can do: bridge-watch on-chain intelligence · 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