MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

xyz.apexfaucet/apex-evm

Agent reads, ETH/Base/Arc/BNB: prices, FX, sanctions, payment checks, balances, NFTs, gas, ENS. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: finance-and-payments · AI-classifiedPricing: usage-based · AI-classifiedversion 1.0.6streamable HTTP17 tools

Summary

xyz.apexfaucet/apex-evm is a remote MCP server listed in the official MCP registry at version 1.0.6. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 17 tools, 4 resources and 4 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Tools: 17
Described as changing data: 0 of 17 toolsAI-classified
Mainly works on: accounts and data in outside web services; money, payments or tradingAI-classified
Topic: finance-and-paymentsAI-classified
Pricing: usage-basedAI-classified
Last tested: 2026-10-23

Add to your client

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

1.0.6, published 2026-10-13 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-13 (earliest version still in the registry; older removed versions would be earlier)

Version history

7 versions listed, all on 2026-10-13; 7 in the 90 days before the 2026-10-23 snapshot.

Most recent 7 versions

1.0.6 · 2026-10-13
1.0.5 · 2026-10-13
1.0.4 · 2026-10-13
1.0.3 · 2026-10-13
1.0.2 · 2026-10-13
1.0.1 · 2026-10-13
1.0.0 · 2026-10-13

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.6 (published 2026-10-13).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

17tools

4resources

4prompts

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services; money, payments or trading.

None of its 17 tools are described as changing anything.

evm_balances_bulkon 1 other serverreads or searches
“Bulk wallet balances on Ethereum, Base, Arc or BNB Chain: up to 50 wallets in one call, native coin or one ERC20, read at one block via Multicall3.”
4 inputs, 1 required
- addressesstringrequired“up to 50 wallet addresses, comma-separated”
- tokenstring“optional ERC20 (0x...)”
- chainstring“ethereum (default), base, arc or bnb”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
payment_verifyon 5 other serversreads or searches
“Payment verification on Ethereum, Base, Arc or BNB Chain: did a transaction really pay an address, totals per token, whether a minimum was met, confirmations.”
6 inputs, 2 required
- hashstringrequired“transaction hash (0x + 64 hex)”
- tostringrequired“address that should have been paid”
- tokenstring“count only this token (0x...)”
- minstring“minimum in token units”
- chainstring“ethereum (default), base, arc or bnb”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
sanctions_checkon 6 other serversreads or searches
“Sanctions check for a wallet on any chain: OFAC SDN listing from Treasury's official list (entry, programs, list date), plus USDC and USDT freeze status on chain for 0x addresses.”
2 inputs, 1 required
- addressstringrequired“wallet address on any chain”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
evm_token_infoon 2 other serversreads or searches
“Token info and total supply for any ERC20 on Ethereum, Base, Arc or BNB Chain: name, symbol, decimals, total supply.”
3 inputs, 1 required
- tokenstringrequired“ERC20 contract (0x...)”
- chainstring“ethereum (default), base, arc or bnb”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
evm_allowanceon 3 other serversreads or searches
“ERC20 allowance on Ethereum, Base, Arc or BNB Chain: how much a spender may move from an owner, and whether it is unlimited.”
5 inputs, 3 required
- tokenstringrequired“ERC20 contract (0x...)”
- ownerstringrequired“wallet that approved (0x...)”
- spenderstringrequired“contract allowed to spend (0x...)”
- chainstring“ethereum (default), base, arc or bnb”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
evm_nonceon 5 other serversreads or searches
“Wallet nonce on Ethereum, Base, Arc or BNB Chain: confirmed count, next nonce, pending transactions.”
3 inputs, 1 required
- addressstringrequired“wallet (0x...)”
- chainstring“ethereum (default), base, arc or bnb”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
evm_gas_estimateon 1 other serverreads or searches
“Gas estimate before sending, on Ethereum, Base, Arc or BNB Chain: gas units, gas price, fee, or the revert reason.”
6 inputs, 1 required
- tostringrequired“recipient or contract (0x...)”
- fromstring“sender (0x...)”
- datastring“hex calldata”
- valuestring“value in wei”
- chainstring“ethereum (default), base, arc or bnb”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
nft_infoon 1 other serverreads or searches
“NFT owner and metadata link for an ERC721 token on Ethereum, Base, Arc or BNB Chain: owner, collection name and symbol, tokenURI.”
4 inputs, 2 required
- contractstringrequired“ERC721 contract (0x...)”
- idstringrequired“token id”
- chainstring“ethereum (default), base, arc or bnb”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
fx_rateon 10 other serversreads or searches
“Currency exchange rate and conversion read on chain from Chainlink FX feeds on Ethereum: EUR, GBP, JPY, CHF, AUD, CAD, CNY, KRW, SGD, TRY, BRL, NZD, PHP, USD, gold (XAU) and silver (XAG); cross rates…”
4 inputs, 1 required
- fromstringrequired“3-letter code, e.g.”
- tostring“3-letter code, default USD”
- amountstring“amount to convert, default 1”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
crypto_priceon 31 other serversreads or searches
“Crypto token price in USD read on chain from Chainlink price feeds on Ethereum: up to 5 tickers per call (ETH, BTC, SOL, BNB, LINK...), each with feed address, round id and age.”
2 inputs, 1 required
- symbolsstringrequired“one to five tickers, comma-separated, e.g.”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
evm_token_balanceon 1 other serverreads or searches
“ERC20 token balance of any wallet on Ethereum, Base, Arc or BNB Chain: raw balance, decimals, symbol and balance in token units, with the block read.”
4 inputs, 2 required
- addressstringrequired“wallet address (0x...)”
- tokenstringrequired“ERC20 token contract (0x...)”
- chainstring“ethereum (default), base, arc or bnb”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
evm_wallet_balanceon 2 other serversreads or searches
“Wallet balance on Ethereum, Base, Arc or BNB Chain: native coin (ETH, BNB, or USDC on Arc), the chain USDC or up to 20 ERC20 tokens you list, nonce, and whether the address is a contract.”
4 inputs, 1 required
- addressstringrequired“wallet address (0x...)”
- chainstring“ethereum (default), base, arc or bnb”
- tokensstring“optional: up to 20 ERC20 addresses, comma-separated”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”

Show 5 more tools

evm_txon 6 other serversreads or searches
“Transaction status and receipt by hash on Ethereum, Base, Arc or BNB Chain: success or revert, from, to, value, contract created, gas used, fee paid, block and time.”
3 inputs, 1 required
- hashstringrequired“transaction hash (0x + 64 hex)”
- chainstring“ethereum (default), base, arc or bnb”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
ens_resolveon 13 other serversreads or searches
“ENS on Ethereum: a .eth name to its address, or an address to its primary ENS name, forward-verified so a reverse record pointing elsewhere is never returned.”
3 inputs
- namestring“an ENS name such as vitalik.eth (pass name OR address)”
- addressstring“an address to look up its ENS name”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
evm_callon 4 other serversreads or searches
“Read-only contract call (eth_call) on Ethereum, Base, Arc or BNB Chain: returned bytes or the revert reason, at a named block.”
5 inputs, 2 required
- tostringrequired“contract address (0x...)”
- datastringrequired“hex calldata: 4-byte selector plus ABI-encoded arguments”
- chainstring“ethereum (default), base, arc or bnb”
- fromstring“optional caller address”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
evm_blockon 6 other serversreads or searches
“Latest block and gas price on Ethereum, Base, Arc or BNB Chain: block number, time and age in seconds, gas price and base fee in gwei, transaction count, chain id.”
2 inputs
- chainstring“ethereum (default), base, arc or bnb”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
evm_codeon 3 other serversreads or searches
“Is this address a contract, on Ethereum, Base, Arc or BNB Chain: code size, the implementation behind an EIP-1967 or ZeppelinOS proxy, and an EIP-7702 delegation.”
3 inputs, 1 required
- addressstringrequired“address (0x...)”
- chainstring“ethereum (default), base, arc or bnb”
- paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 17 tools
Says what it returns: 100% of 17 tools
States limits, defaults or errors: 100% of 17 tools
Says when to use it: 100% of 17 tools
Items covered per tool: 4.0 of 4 on average

Counted from the listing

Parameters with a description: 100% of 63
Tools with a description: 100% of 17
Typical description length: 330 characters

The tool set

Counted from the listing

Tools: 17
Size of the list: about 3,481 tokens for an agent to load (characters ÷ 4)
Naming: 17 of 17 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 17 of 17 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://apexfaucet.xyz/api/mcp/evm

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "apex-evm": {
      "url": "https://apexfaucet.xyz/api/mcp/evm"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "apex-evm": {
      "type": "http",
      "url": "https://apexfaucet.xyz/api/mcp/evm"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"apex-evm","type":"http","url":"https://apexfaucet.xyz/api/mcp/evm"}'

Claude Code

claude mcp add --transport http apex-evm https://apexfaucet.xyz/api/mcp/evm

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://apexfaucet.xyz/api/mcp/evm --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint apexfaucet.xyz/api/mcp/evm	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about xyz.apexfaucet/apex-evm

Answered from the data above

Is xyz.apexfaucet/apex-evm free to use?

Its website (apexfaucet.xyz/llms.txt) describes a usage-based pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does xyz.apexfaucet/apex-evm need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has xyz.apexfaucet/apex-evm been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

What can xyz.apexfaucet/apex-evm do?

It lists 17 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search. We did not call any tool, so this describes the text, not the behaviour.

Can xyz.apexfaucet/apex-evm change or delete data?

None of its 17 tools is described as changing anything (our AI model's reading of the descriptions; nobody checked it by hand). We did not call any tool.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.vybenetwork/solana-mcp-vybeSolana MCP by Vybealso has tools that reads or searchescompare with this one
io.github.mnemox-ai/tradememory-protocolalso has tools that reads or searchescompare with this one
io.github.agent-next/polymarket-paper-traderPolymarket Paper Traderalso has tools that reads or searchescompare with this one
io.github.openaccountants/openaccountantsOpenAccountantsalso has tools that reads or searchescompare with this one
io.github.koreal6803/finlab-aialso has tools that reads or searchescompare with this one
io.github.xang1234/stockscreen-mcpStock Screeneralso has tools that reads or searchescompare with this one

Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
368 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 17 tools, 4 resources, 4 prompts.
4,456 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

finance-and-payments

AI-classified · 2026-10-23

Pricing modelAI-classified

usage-based

read from apexfaucet.xyz/llms.txt · 2026-10-23

“$0.009 a page and $0.14 for up to 25 pages, over x402 (USDC on Arc, Base or Solana, or XNT on X1).”

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “xyz.apexfaucet/apex-evm: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/xyz.apexfaucet/apex-evm

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/xyz.apexfaucet/apex-evm)](https://protocolprobe.com/mcp/servers/xyz.apexfaucet/apex-evm)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology