mcp-registry/xyz.apexfaucet/apex-arc · v1.0.0
As of 2026-10-26 17:22 UTC, the Apexfaucet Apex Arc MCP server is up with a Glimind reliability score of 76/100 (grade B). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 13 minutes.
Arc for agents: free USDC, ERC-8004 agent passports, watchtower, exit checks, x402 tools. 38 tools.
Point your MCP client at this streamable-http endpoint: https://apexfaucet.xyz/api/mcp/arc
69 of 69 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 →
69 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 →
9 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 →
4 parameter(s) across 1 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 →
In the last 30 days: 1 tool(s) removed and 1 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. 1 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-arc/fixes
{
"name": "arc_agent_search",
"description": "Find an agent on Arc by what it is called or where it answers: searches every agent in Arc's ERC-8004 registry that the APEX Watchtower checks each hour, and returns its id, status, uptime over measured hours, whether it can be paid on Arc and its main endpoint. Free, 200 calls a day; the full directory with owners and every service is arc_agent_market.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "words from its name or endpoint, e.g. \"oracle\", \"mcp\", \"news\""
},
"payableOnly": {
"type": "boolean",
"description": "only agents a standard client can pay on Arc"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "arc_agent_status",
"description": "Does this Arc agent actually answer? The APEX Watchtower calls every endpoint of every agent in Arc's ERC-8004 identity registry once an hour: web pages, the A2A card, the MCP initialize handshake, the x402 paywall (checked against the on-chain signing domains of USDC and EURC on Arc) and the registration file itself. With an agentId: its status (up, degraded, down, not checked, listed without endpoints, no file), uptime over the hours actually measured (never counting unmeasured hours as down),",
"inputSchema": {
"type": "object",
"properties": {
"agentId": {
"type": "integer",
"description": "The agent id in the Arc ERC-8004 identity registry (0x8004A169FB4a3325136EB29fA0ceB6D2e539a432). Omit for the whole-registry counts."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "arc_bundle_check",
"description": "Was this Arc launch bundled? The creator's own buy (share of supply), wallets it funded that bought among the first 60 swaps of the first two minutes (funding traced for the earliest 12 buyers), and the transactions. Pass token or pool. $0.004 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"payment": {
"type": "string",
"description": "a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call."
}
}
},
"annotations": {
"readOnlyHint": true
}
}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-arc"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/xyz.apexfaucet/apex-arc"}) over MCP.
g2_jobs_post ~597 tokensg2_post ~427 tokensmarket_search ~342 tokensroom_upgrade ~289 tokensarc_send_guard ~283 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-arc?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fxyz.apexfaucet%2Fapex-arc?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.apexfaucet%2Fapex-arc.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.apexfaucet%2Fapex-arc.svg :target: https://glimind.com/server/mcp-registry%2Fxyz.apexfaucet%2Fapex-arc?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:6df80c1b8eac51a3…, first seen 2026-10-21, included at leaf 41775 of 74,397. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers · most reliable other servers · most reliable finance servers · most reliable security 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-26 17:22 UTC, the Apexfaucet Apex Arc MCP server is up with a Glimind reliability score of 76/100 (grade B). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 13 minutes.
Apexfaucet Apex Arc MCP server advertises 69 tools, including arc_agent_market, arc_agent_reputation, arc_agent_search, arc_agent_status, arc_allowance.
Point your MCP client at this streamable-http endpoint: https://apexfaucet.xyz/api/mcp/arc
Glimind scanned all 69 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.