Is the Tooloracle Predictionguard MCP server down?

mcp-registry/io.tooloracle/predictionguard · v1.0.0

healthy
Last checked 2026-10-20 04:33 UTC · handshake 502ms

As of 2026-10-20 04:33 UTC, the Tooloracle Predictionguard MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 15 minutes.

uptime (30d checks)
99.9%
checks observed
3,876
outages (90d)
1
tools
41

Polymarket integrity MCP — 28 tools for wallet risk, whales, UMA scans, SAR/STR reports.

Install Tooloracle Predictionguard MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http tooloracle-predictionguard-mcp-server https://feedoracle.io/predictionguard/mcp/

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "tooloracle-predictionguard-mcp-server": {
      "type": "http",
      "url": "https://feedoracle.io/predictionguard/mcp/"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 5 warning(s) across 41 tool(s); ~7,772 tokens of tool definitions.
Scores higher than 6% of 15,386 MCP servers Glimind has audited.
Its tool list costs an agent ~7,772 tokens per session — more than 65% of servers.
70 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions76
Safety hints16
Token cost75
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (6)

41 of 41 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 →

Tools: pg_adverse_media_entity, pg_classified_keyword_match, pg_evidence_bundle_market, pg_information_advantage_score, pg_insider_alert_signed and 36 more

41 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 →

13 parameter(s) across 8 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 →

Tools: pg_kalshi_search, pg_kyc_bundle_entity, pg_market_integrity_scan, pg_market_volume_profile, pg_pre_event_flow_analysis and 3 more

2 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 →

Tools: pg_kalshi_orderbook_analysis, pg_whale_remove

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. 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 →

Auto-fix: 12 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.tooloracle%2Fpredictionguard/fixes

pg_information_advantage_score 1 change
{
  "name": "pg_information_advantage_score",
  "description": "Composite A-F rating for whether a wallet appears to have had non-public information on a specific market. Aggregates pg_position_timing_anomaly (50% weight) + pg_insider_signal_scan (30%) plus bonuses for being in top positioners (+10), new to market (+10), and sensitive category (+10). Returns letter grade A-F, composite score 0-100, all component scores, and interpretation guide. Pattern-matches reported cases (Van Dyke, Hyperliquid whale). Statistical signal only — not a legal determination.",
  "inputSchema": {
    "type": "object",
    "required": [
      "wallet"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "Market id / conditionId"
      },
      "slug": {
        "type": "string",
        "description": "Market slug"
      },
      "wallet": {
        "type": "string",
        "description": "Wallet to score (0x + 40 hex)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
pg_kalshi_conflict_of_interest_check 1 change
{
  "name": "pg_kalshi_conflict_of_interest_check",
  "description": "CFTC Rule 5.17(z) conflict-of-interest pre-trade check. Analyzes a Kalshi market's metadata to detect whether trading it would expose decision-makers (election candidates, government officials, athletes, regulators) to insider-trading liability. Pattern-matches against the Kalshi April 2026 disciplinary cases (Moran/Klein/Enriquez) and the CFTC Van Dyke complaint. Returns ALLOW/MONITOR/WARN/BLOCK recommendation + 0-100 score + reference cases. Cannot identify actual trader identity (Kalshi publi",
  "inputSchema": {
    "type": "object",
    "properties": {
      "ticker": {
        "type": "string",
        "description": "Kalshi market ticker"
      },
      "event_ticker": {
        "type": "string",
        "description": "Or event_ticker for the whole event"
      },
      "candidate_name": {
        "type": "string",
        "description": "Optional: specific person's name to match against title (e.g. 'Mark Moran')"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
pg_kalshi_orderbook_analysis 1 change
{
  "name": "pg_kalshi_orderbook_analysis",
  "description": "Forensic orderbook analysis for one Kalshi market. Detects manipulation-vulnerable patterns: (1) wide spread (>$0.10), (2) shallow depth (<10 contracts), (3) few price levels, (4) single-order dominance (>80% in top level), (5) penny-wall pattern (large bids at ≤$0.005, commonly used to fake depth). Returns 0-100 score, severity, and full level-by-level data. Kalshi returns bids only — implied asks computed via yes_bid + no_bid = $1 reciprocity.",
  "inputSchema": {
    "type": "object",
    "required": [
      "ticker"
    ],
    "properties": {
      "ticker": {
        "type": "string",
        "description": "Kalshi market ticker"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

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/io.tooloracle/predictionguard"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.tooloracle/predictionguard"}) over MCP.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fpredictionguard.svg)](https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fpredictionguard?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fpredictionguard?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fpredictionguard.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fpredictionguard.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fpredictionguard?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:af30535078193a43…, first seen 2026-10-17, included at leaf 12163 of 30,751. Version history · verify what your client received.

Tools (41)

Compare: most reliable security servers · most reliable data servers · most reliable blockchain servers · most reliable finance servers · most reliable search servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Tooloracle Predictionguard MCP server down right now?

As of 2026-10-20 04:33 UTC, the Tooloracle Predictionguard MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 15 minutes.

How many tools does Tooloracle Predictionguard MCP server provide?

Tooloracle Predictionguard MCP server advertises 41 tools, including pg_adverse_media_entity, pg_classified_keyword_match, pg_evidence_bundle_market, pg_information_advantage_score, pg_insider_alert_signed.

How do I install Tooloracle Predictionguard MCP server?

Point your MCP client at this streamable-http endpoint: https://feedoracle.io/predictionguard/mcp/

Is the Tooloracle Predictionguard MCP server safe to connect to an AI agent?

Glimind scanned all 41 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.

Operator of Tooloracle Predictionguard MCP server?

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.

Feedback
Help us improve