Skip to content

Mini XUI Proxy Trials MCP server

shop.leefbiant123.vps/mini-xuivps.leefbiant123.shopstreamable-httpv1.0.0Scanned

Free short-lived VLESS Reality and Hysteria 2 proxy credentials for compatible clients.

4 tools: 1 change things and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Mini XUI Proxy Trials MCP server can do

The Mini XUI Proxy Trials MCP server is published by vps.leefbiant123.shop, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: create_trial), but cannot delete data. 3 tools only read.

1 tool reads private data (get_trial_connection).

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

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.0.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.

4 tools

Changes things 1Claude Code: ask
  • create_trialReserve a free 1 GiB, 30-minute proxy trial using an inbound from get_service_info.No findings

    Why it is in this group

    • The name "create_trial" says "create": a word for a change.
    Description, as the server wrote it
    Reserve a free 1 GiB, 30-minute proxy trial using an inbound from get_service_info. Returns an ID and secret access_token. This has side effects, consumes a slot, and is not idempotent. If ready is false, poll get_trial_status. Never publish or log the token.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • readOnlyHint: false
Only reads 3Show 3 read-only tools
  • get_service_infoDiscover available VLESS Reality and Hysteria 2 proxy trial inbounds, quota, duration and available capacity.No findings

    Why it is in this group

    • The name "get_service_info" says "get": a word for reading.
    Description, as the server wrote it
    Discover available VLESS Reality and Hysteria 2 proxy trial inbounds, quota, duration and available capacity. Free; no authentication.

    Annotations the server declares

    • idempotentHint: false
    • readOnlyHint: true
  • get_trial_connectionReturn a secret VLESS or Hysteria 2 connection link for an active trial.Reads private dataNo findings

    Why it is in this group

    • The name "get_trial_connection" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "secret": it reads secrets.
    Description, as the server wrote it
    Return a secret VLESS or Hysteria 2 connection link for an active trial. Requires its ID and access_token. Never publish or log the returned link.

    Annotations the server declares

    • idempotentHint: false
    • readOnlyHint: true
  • get_trial_statusGet a trial's expiry, approximate usage and active state.No findings

    Why it is in this group

    • The name "get_trial_status" says "get": a word for reading.
    Description, as the server wrote it
    Get a trial's expiry, approximate usage and active state. Requires the ID and secret access_token from create_trial. Keep both private.

    Annotations the server declares

    • idempotentHint: false
    • readOnlyHint: true

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 untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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.

Tools listed without sign-in

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

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://vps.leefbiant123.shop/mcp: tools/list returned 4 tools to an anonymous client, including create_trial (write)

    What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http mini-xui https://vps.leefbiant123.shop/mcp
claude mcp add --transport http mini-xui https://vps.leefbiant123.shop/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__mini-xui__get_service_info",
      "mcp__mini-xui__get_trial_connection",
      "mcp__mini-xui__get_trial_status"
    ],
    "ask": [
      "mcp__mini-xui__create_trial"
    ],
    "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 mini-xui. Review it before you use it.

Capability tags behind 1 rule
  • mcp__mini-xui__get_trial_connection private-data

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/shop.leefbiant123.vps/mini-xui/verify?hash=ee6c55a2380309dcbc62cba5dfc77e35c506d37a003cad363e07122bceeb6fd4" | jq -e '.changed == false'

Pinned hash ee6c55a23803, from Nov 19, 2026, 16:18 UTC.

Watch

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

https://radar.anlyon.com/servers/shop.leefbiant123.vps/mini-xui/changes.xml

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

Badge

Anlyon Radar badge for shop.leefbiant123.vps/mini-xui
[![Anlyon Radar](https://radar.anlyon.com/badge/shop.leefbiant123.vps/mini-xui.svg)](https://radar.anlyon.com/servers/shop.leefbiant123.vps/mini-xui)

Source: MCP Registry. Synced Nov 19, 2026, 16:18 UTC.

Mini XUI Proxy Trials MCP server: questions and answers

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

Is the Mini XUI Proxy Trials MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 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 Mini XUI Proxy Trials MCP server delete data?

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

Can the Mini XUI Proxy Trials 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 Mini XUI Proxy Trials MCP server have?

4 tools: 1 write, 3 read. create_trial, get_service_info, get_trial_connection and get_trial_status.

Does the Mini XUI Proxy Trials MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Mini XUI Proxy Trials MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Mini XUI Proxy Trials MCP server changed its tools?

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