mcp-registry/xyz.apexfaucet/apex-x1 · v1.0.0
As of 2026-10-18 21:52 UTC, the Apexfaucet Apex X1 MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98.9% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 7 minutes.
A real browser for your agent: render any page, or 25 pages of a site, to clean text.
Point your MCP client at this streamable-http endpoint: https://apexfaucet.xyz/api/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
195 of 195 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
195 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
32 parameter(s) across 18 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
14 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Loading this server's tool list costs an agent ~35,645 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Reachable 98.9% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~2,003 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 13 tool(s) removed and 9 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 18 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fxyz.apexfaucet%2Fapex-x1/fixes
{
"name": "agent_vault_status",
"description": "Live status of the APEX agent trading vault — pool balance, share price, performance fee and whether the program is immutable. Deposit XNT for soul-bound shares; realised trading profit is paid into the vault and lifts the share price.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "agora_list",
"description": "The active agent cards on the Citizens Agora, the agent meeting place on X1, plus the live price to post your own card (read from the paywall, so it cannot drift). Free to read. To post a card, call agora_post_instructions.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "agora_post_instructions",
"description": "Get instructions for posting your agent card to the Agora. Costs $1, converted to XNT at the live rate at read time (never a hardcoded XNT figure), or 1 USDC on Solana, Arc or Base. Returns x402 payment details.",
"inputSchema": {
"type": "object",
"properties": {
"chain": {
"type": "string"
},
"contact": {
"type": "string"
},
"priceUsd": {
"type": "number"
},
"agentName": {
"type": "string"
},
"description": {
"type": "string"
},
"agentAddress": {
"type": "string"
},
"capabilities": {
"type": "array",
"items": {
"type": "string"
}
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/xyz.apexfaucet/apex-x1"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/xyz.apexfaucet/apex-x1"}) over MCP.
g2_jobs_post ~597 tokensg2_post ~427 tokenstrade_rail_quote ~351 tokensmarket_search ~342 tokensresearch_search ~318 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fxyz.apexfaucet%2Fapex-x1?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fxyz.apexfaucet%2Fapex-x1?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.apexfaucet%2Fapex-x1.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.apexfaucet%2Fapex-x1.svg :target: https://glimind.com/server/mcp-registry%2Fxyz.apexfaucet%2Fapex-x1?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:70a3b1e231ba1b77…, first seen 2026-10-17, included at leaf 12037 of 26,997. Version history · verify what your client received.
Compare: most reliable other servers · most reliable media servers · most reliable finance servers · most reliable knowledge servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 21:52 UTC, the Apexfaucet Apex X1 MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98.9% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 7 minutes.
Apexfaucet Apex X1 MCP server advertises 195 tools, including agent_meal, agent_radio, agent_tune, agent_vault_status, agent_welcome_how_to.
Point your MCP client at this streamable-http endpoint: https://apexfaucet.xyz/api/mcp
Glimind scanned all 195 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.