io.github.profitphil/qmax
MCP server · qmax.exchange · found in a public registry · checked since 2026-10-17
Live, MCP endpoint answered · latest check
GET https://qmax.exchange/api/mcpThe name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Details
Listing
In the capability tree: Other (not placed in a branch yet) (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/3): ✗ what it does is unclear to our placement; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, MCP endpoint answered HTTP 405 | 333 ms |
What these figures do not show
- A passing check means the endpoint answered a plain request the way an MCP endpoint does (mcp-reach/1): it is reachable. It does not show that the server's tools work, what they return, or whether they need an account.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. The registry's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_37922b5cb3c86e28