Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

xyz.fluxiq/agent

REMOTE · FLUXIQ.XYZ · SCANNED SEP 20

Non-custodial Ethereum swaps and managed liquidity. You sign every tx; FluxIQ holds no funds.

Available components

0 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 999 tokens (~111/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "quote_lp_withdraw" implies "withdraw" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the xyz.fluxiq/agent MCP server?

xyz.fluxiq/agent is a hosted endpoint at https://fluxiq.xyz/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · fluxiq.xyz

# add to Claude Code
claude mcp add --transport http xyz-fluxiq-agent 'https://fluxiq.xyz/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "xyz-fluxiq-agent": {
      "url": "https://fluxiq.xyz/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "xyz-fluxiq-agent": {
      "type": "http",
      "url": "https://fluxiq.xyz/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.xyz-fluxiq-agent]
url = "https://fluxiq.xyz/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-fluxiq-agent": {
      "type": "remote",
      "url": "https://fluxiq.xyz/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add xyz-fluxiq-agent --url 'https://fluxiq.xyz/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  xyz-fluxiq-agent:
    url: "https://fluxiq.xyz/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "xyz-fluxiq-agent": {
      "Transport": "http",
      "Url": "https://fluxiq.xyz/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add xyz-fluxiq-agent -t streamable-http -u 'https://fluxiq.xyz/api/mcp'
// mcp.json
{
  "mcpServers": {
    "xyz-fluxiq-agent": {
      "type": "http",
      "url": "https://fluxiq.xyz/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://fluxiq.xyz/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fluxiq.xyz CN=YR1,O=Let's Encrypt,C=US 6 Aug 2026 4 Nov 2026 RSA 2048 SHA256-RSA 5bbbb4bfe2de93fc219c5aa7572e296e96c
SANs: fluxiq.xyz
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of fluxiq.xyz. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
fluxiq.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://fluxiq.xyz/api/mcp Verified 200
http (plaintext) http://fluxiq.xyz/api/mcp HTTPS enforced 308 https://fluxiq.xyz/api/mcp
MCP tools · 9 exposed · ~999 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
build_lp_deposit ~156

Build a NON-CUSTODIAL any-token LP deposit plan (approve → Permit2 sign → router.depositAnyToken) for the caller to sign + broadcast. No broadcast.

NameTypeReqDescription
amountInstringyesAmount in base units (integer string, e.g. USDC 6dp).
chainIdintegeryesEVM chain id (mainnet = 1 in v1).
inputTokenstringyesAny held token to deposit.
recipientstringyesRecipient / payer address (the wallet that signs + receives).
slippageBpsintegerOptional slippage budget in basis points (0–10000).
vaultstringyesKnown any-token LP vault address.

No output schema declared.

No examples provided.

build_lp_withdraw ~149

Build a NON-CUSTODIAL any-token LP withdraw plan (approve shares → Permit2 sign → router.withdrawAnyToken) for the caller to sign + broadcast. No broadcast.

NameTypeReqDescription
chainIdintegeryesEVM chain id (mainnet = 1 in v1).
outputTokenstringyesToken to receive on withdraw.
recipientstringyesRecipient / payer address (the wallet that signs + receives).
sharesstringyesVault shares to burn (base-unit integer string).
slippageBpsintegerOptional slippage budget in basis points (0–10000).
vaultstringyesKnown any-token LP vault address.

No output schema declared.

No examples provided.

build_swap ~155

Build a NON-CUSTODIAL ERC20 swap plan (approve → Permit2 sign → router.swap) for the caller to sign + broadcast. No broadcast.

NameTypeReqDescription
amountInstringyesAmount in base units (integer string, e.g. USDC 6dp).
chainIdintegeryesEVM chain id (mainnet = 1 in v1).
recipientstringyesRecipient / payer address (the wallet that signs + receives).
slippageBpsintegerOptional slippage budget in basis points (0–10000).
tokenInstringyesERC20 input token (native ETH is not supported).
tokenOutstringyesERC20 output token.

No output schema declared.

No examples provided.

list_tokens ~48

List the public swap token allow-list (address/symbol/name/decimals). Public market data only — no user-private reads.

NameTypeReqDescription
chainIdintegerDefaults to mainnet (1).

No output schema declared.

No examples provided.

list_vaults ~48

List the public any-token LP vaults (addresses + token pair). Public market data only — no user-private reads.

NameTypeReqDescription
chainIdintegerDefaults to mainnet (1).

No output schema declared.

No examples provided.

ping ~14

Health check — returns 'pong'.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

quote_lp_deposit ~146

Read-only any-token LP deposit preview: estimated shares, guaranteed minShares, fee, and refund bps. No broadcast.

NameTypeReqDescription
amountInstringyesAmount in base units (integer string, e.g. USDC 6dp).
chainIdintegeryesEVM chain id (mainnet = 1 in v1).
inputTokenstringyesAny held token to deposit.
recipientstringyesRecipient / payer address (the wallet that signs + receives).
slippageBpsintegerOptional slippage budget in basis points (0–10000).
vaultstringyesKnown any-token LP vault address.

No output schema declared.

No examples provided.

quote_lp_withdraw ~134

Read-only any-token LP withdraw preview: estimated and guaranteed token-out for burning vault shares. No broadcast.

NameTypeReqDescription
chainIdintegeryesEVM chain id (mainnet = 1 in v1).
outputTokenstringyesToken to receive on withdraw.
recipientstringyesRecipient / payer address (the wallet that signs + receives).
sharesstringyesVault shares to burn (base-unit integer string).
slippageBpsintegerOptional slippage budget in basis points (0–10000).
vaultstringyesKnown any-token LP vault address.

No output schema declared.

No examples provided.

quote_swap ~149

Read-only ERC20 swap quote: expected out, guaranteed minOut, fee, and a high-level route summary. No broadcast.

NameTypeReqDescription
amountInstringyesAmount in base units (integer string, e.g. USDC 6dp).
chainIdintegeryesEVM chain id (mainnet = 1 in v1).
recipientstringyesRecipient / payer address (the wallet that signs + receives).
slippageBpsintegerOptional slippage budget in basis points (0–10000).
tokenInstringyesERC20 input token (native ETH is not supported).
tokenOutstringyesERC20 output token.

No output schema declared.

No examples provided.

Common questions

What is the xyz.fluxiq/agent MCP server?

xyz.fluxiq/agent is an MCP server listed in the public MCP registry as xyz.fluxiq/agent. Non-custodial Ethereum swaps and managed liquidity. You sign every tx; FluxIQ holds no funds. This page covers its hosted endpoint (https://fluxiq.xyz/api/mcp).

Is the xyz.fluxiq/agent MCP server safe to use?

xyz.fluxiq/agent scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the xyz.fluxiq/agent MCP server expose?

xyz.fluxiq/agent exposes 9 tools: ping, quote_swap, build_swap, quote_lp_deposit, build_lp_deposit, and 4 more. Their descriptions and schemas cost roughly 999 tokens of context every time the server is loaded.

Does the xyz.fluxiq/agent MCP server require authentication?

No. We connected to xyz.fluxiq/agent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the xyz.fluxiq/agent MCP server still maintained?

xyz.fluxiq/agent is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.