Services / MCP server · Registry
OPX
GET https://opx-status.dev/mcp
Listed in a public agent registry. The name is the registry's label, not ours. Not reviewed by a person. See all 2 endpoints from opx-status.dev.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
In the capability tree: Search and information / Directories of services / Find paid APIs (primary); Payments and money / Agent spending limits. Placed by a small AI model, where agents with the tasks it serves would look first (placement-ai/2, 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 did not pass.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:MIA |
Server error HTTP 530 not an answer an MCP endpoint gives to a plain request |
29 ms |
cloudflare:ATL |
Live, MCP endpoint answered HTTP 405 | 343 ms |
What this evidence does 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 1 day (less than 30).
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page.
Machine-readable: /api/v1/services/cand_6f1bf9ba0017bc78