mcp-registry/com.predictasiax/mcp · v2.0.0
As of 2026-10-22 19:18 UTC, the Predictasiax MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Asia-native prediction-market MCP: markets, portfolio, orders. Attribution + fee_ledger coded.
Claude Code
claude mcp add --transport http predictasiax-mcp-server https://mcp.predictasiax.com
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"predictasiax-mcp-server": {
"type": "http",
"url": "https://mcp.predictasiax.com"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
44 of 44 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 →
44 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 →
44 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).
Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →
108 parameter(s) across 38 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 →
15 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 →
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. 38 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.predictasiax%2Fmcp/fixes
{
"name": "pax_access_request_create",
"description": "Submit an access-request for a builder track (no email required — provide Telegram / Signal / Discord / Matrix / X DM handle).",
"inputSchema": {
"type": "object",
"required": [
"contact_channel",
"contact_handle",
"use_case"
],
"properties": {
"track": {
"enum": [
"sandbox",
"trade_capped",
"trade_full",
"genesis",
"partner"
],
"type": "string"
},
"org_name": {
"type": "string"
},
"use_case": {
"type": "string",
"maxLength": 2000,
"minLength": 20
},
"jurisdiction": {
"type": "string"
},
"contact_handle": {
"type": "string"
},
"contact_channel": {
"enum": [
"telegram",
"signal",
"discord",
"matrix",
"x_dm"
],
"type": "string"
},
"intended_scopes": {
"type": "array",
"items": {
"type": "string"
}
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "pax_access_request_status",
"description": "Check status of a pending access request by its request_id.",
"inputSchema": {
"type": "object",
"required": [
"request_id"
],
"properties": {
"request_id": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "pax_balance_get",
"description": "USDT free + reserved balance for a subaccount.",
"inputSchema": {
"type": "object",
"required": [
"user_id"
],
"properties": {
"user_id": {
"type": "string"
},
"subaccount_id": {
"type": "string"
}
}
},
"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/com.predictasiax/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.predictasiax/mcp"}) over MCP.
pax.place_order ~225 tokenspax.access_request_create ~192 tokenspax.market_search ~164 tokenspax.composer_proposal_submit ~163 tokenspax.probability_movers ~147 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%2Fcom.predictasiax%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.predictasiax%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.predictasiax%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.predictasiax%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.predictasiax%2Fmcp?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:ff78f8540832696d…, first seen 2026-10-17, included at leaf 196 of 47,672. Version history · verify what your client received.
Compare: most reliable other servers · most reliable security servers · most reliable finance servers · most reliable data servers · most reliable knowledge 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-22 19:18 UTC, the Predictasiax MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Predictasiax MCP server advertises 44 tools, including pax.access_request_create, pax.access_request_status, pax.balance_get, pax.builder_apikeys_list, pax.builder_apps_list.
Point your MCP client at this streamable-http endpoint: https://mcp.predictasiax.com
Glimind scanned all 44 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.