Skip to content

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

io.github.Dcroyalty/uxusDcroyaltystreamable-httpv1.4.0Scanned

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

9 tools: 6 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 6 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 1
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

6 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the UXUS Agent Services: wallet lookup, entity labels, caller ID MCP server can do

The UXUS Agent Services: wallet lookup, entity labels, caller ID MCP server is published by the GitHub account Dcroyalty. It has 9 tools. It can create or change data (6 tools: scrape_url, yield_grade, lending_grade, check_entity and 2 more), but cannot delete data. 3 tools only read.

2 tools bring in text other people can write (search_web and scrape_url); 1 tool can send data out of your system (scrape_url).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 2, 2026, version 1.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 6Claude Code: ask
  • caller_idShould this wallet be answered?No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Should this wallet be answered? For wallet messaging (XMTP, Push), which has no spam filter. Params: address (0x EVM address, required); chain (base default, or ethereum). Composes entity attribution + risk score + on-chain history + forward-verified name into ANSWER | SCREEN | BLOCK with reasons[] and a confidence flag. BLOCK on sanctioned/drainer/phishing/scam/mixer or risk verdict BLOCK; SCREEN is the default for unknown addresses. Free.
  • check_entityEntity attribution — what IS this address, not who owns it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Entity attribution — what IS this address, not who owns it. Params: address (0x EVM address, required); chain (base default, or ethereum). Returns { address, chain, is_known, label, category }. category is one of sanctioned, mixer, exchange, bridge, dex_router, scam, drainer, phishing, flagged, token_contract, protocol, unknown. "sanctioned" is set only when the address is on the OFAC SDN list (the same source /api/risk uses); a non-OFAC blocklist hit is "flagged". Sourced from OFAC, ScamSniffer, MEW, eth-labels and curated Base/Tornado sets. Never guesses. Free.
  • healthService health check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Service health check. No parameters. Returns { ok, service, time, upstream } — confirms the uxus.finance API is reachable. Free.
  • lending_gradeA-F risk grade for one XRP Ledger lending vault or loan broker, from on-ledger data only (size, utilization, first-loss cover ratio, late/impaired/defaulted loans, unrealized loss,…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    A-F risk grade for one XRP Ledger lending vault or loan broker, from on-ledger data only (size, utilization, first-loss cover ratio, late/impaired/defaulted loans, unrealized loss, realized yield), with every rule that moved the grade. Not a credit rating. This is a PAID x402 call: $0.02 USDC on Base at GET /api/lending/grade. This tool returns the payment resource to call; it does not compute the grade. NOT LIVE YET: it goes live when XRPL lending (the LendingProtocol and SingleAssetVault amendments) is enabled on mainnet. Until then this tool returns available:false and GET /api/lending/grade returns 503 with no charge. Params: id (64-hex Vault or LoanBroker ID, required); type (vault | broker, optional).
  • scrape_urlAny web page as clean, LLM-ready markdown, text or html.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe name "scrape_url" says "scrape": it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Any web page as clean, LLM-ready markdown, text or html. This is a PAID x402 call: $0.01 USDC on Base at GET /api/scrape. This tool returns the payment resource to call; it does not fetch the page. Params: url (absolute http/https URL, required); format (markdown | text | html, default markdown); max_chars (integer, default 40000, max 120000).
  • yield_gradeA-F risk grade for one way to earn on XRP or RLUSD, from the XRP Yield Desk (xrplhub.io/yield): XRPL AMM pools, Doppler vaults, Firelight stXRP and other Flare FXRP products, RLUSD…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    A-F risk grade for one way to earn on XRP or RLUSD, from the XRP Yield Desk (xrplhub.io/yield): XRPL AMM pools, Doppler vaults, Firelight stXRP and other Flare FXRP products, RLUSD and XRP DeFi pools, and exchange earn programs. Returns the rate, size, lockup and withdrawal terms, who holds the keys, chain, age, audits, the data source with its timestamp, and every rule that moved the grade. General information, not advice; the products graded pay nothing. This is a PAID x402 call: $0.02 USDC on Base at GET /api/yield/grade. This tool returns the payment resource to call; it does not compute the grade. Find ids for free at https://www.xrplhub.io/api/yield/options. Params: id (option id, required).
Only reads 3Show 3 read-only tools
  • lookup_walletAddress lookup for Ethereum and Base 0x addresses and XRPL r-addresses, auto-detected.No findings

    Why it is in this group

    • The name "lookup_wallet" says "lookup": a word for reading.
    Description, as the server wrote it
    Address lookup for Ethereum and Base 0x addresses and XRPL r-addresses, auto-detected. Params: address (EVM 0x address or XRPL classic r-address, required); chain (optional EVM history hint: base default, or ethereum). Detects EVM vs XRPL from the format. Returns one normalized envelope: { address, chain, chain_detected, exists, risk_score, risk_level, verdict, flags, entity, name }. Free. For a fast first-pass check on a counterparty wallet.
  • resolve_nameBidirectional name <-> address resolution for ENS (name.eth) and Basenames (name.base.eth).No findings

    Why it is in this group

    • The name "resolve_name" says "resolve": a word for reading.
    Description, as the server wrote it
    Bidirectional name <-> address resolution for ENS (name.eth) and Basenames (name.base.eth). Param: q (an ENS/Basename name, an EVM 0x address, or an XRPL r-address, required). Auto-detects direction. Reverse records are forward-verified against the address to stop name spoofing. Returns { query, kind, namespace, chain, resolved, address, name, sources }. XRPL .xrp names are detected but resolved:false (no canonical registry). Free.
  • search_webLive web search: ranked results plus Google's answer box, knowledge graph, people-also-ask and related searches when the Google-backed provider answers.Reads text others writeNo findings

    Why it is in this group

    • The name "search_web" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe name "search_web" says "search" and "web": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Live web search: ranked results plus Google's answer box, knowledge graph, people-also-ask and related searches when the Google-backed provider answers. This is a PAID x402 call: $0.01 USDC on Base at GET /api/search. This tool returns the payment resource to call; it does not run the search. Params: query (string, required); count (integer 1-20, default 10); country/language/page/device (optional).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:57 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
402
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 402.

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 402
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 402; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 6 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 402
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.4.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__uxus__search_web",
      "mcp__uxus__lookup_wallet",
      "mcp__uxus__resolve_name"
    ],
    "ask": [
      "mcp__uxus__scrape_url",
      "mcp__uxus__yield_grade",
      "mcp__uxus__lending_grade",
      "mcp__uxus__check_entity",
      "mcp__uxus__caller_id",
      "mcp__uxus__health"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as uxus. Review it before you use it.

Capability tags behind 2 rules
  • mcp__uxus__search_web untrusted-input
  • mcp__uxus__scrape_url untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Dcroyalty/uxus/verify?hash=5bbc9849a1976ce7f4da66f5bfd4e0920e5dcb8635792b7ccb98e1ad12a806fa" | jq -e '.changed == false'

Pinned hash 5bbc9849a197, from Nov 2, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Dcroyalty/uxus/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Dcroyalty/uxus
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Dcroyalty/uxus.svg)](https://radar.anlyon.com/servers/io.github.Dcroyalty/uxus)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:15 UTC.

UXUS Agent Services: wallet lookup, entity labels, caller ID MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the UXUS Agent Services: wallet lookup, entity labels, caller ID MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the UXUS Agent Services: wallet lookup, entity labels, caller ID MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the UXUS Agent Services: wallet lookup, entity labels, caller ID MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the UXUS Agent Services: wallet lookup, entity labels, caller ID MCP server have?

9 tools: 6 write, 3 read. scrape_url, yield_grade, lending_grade, check_entity, caller_id, health, search_web, lookup_wallet and 1 more.

Does the UXUS Agent Services: wallet lookup, entity labels, caller ID MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the UXUS Agent Services: wallet lookup, entity labels, caller ID MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scrape_url.

Has the UXUS Agent Services: wallet lookup, entity labels, caller ID MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 2, 2026.