Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Predictionguard is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
41
tools declared
remote
at its publisher
—
calls last 7d
What it does
Polymarket integrity MCP — 28 tools for wallet risk, whales, UMA scans, SAR/STR reports.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http predictionguard-mcp https://feedoracle.io/predictionguard/mcp/
# 2 — ask your agent for something these tools do
# pg_overview, pg_market_search, pg_market_details and 38 more
Predictionguard costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TOAll 61 servers
tooloracle61 servers
14 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http predictionguard-mcp https://feedoracle.io/predictionguard/mcp/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
41 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
PredictionGuard platform overview: covered platforms, tool inventory, Polymarket Gamma API ping, Polygon RPC ping (Ankr-backed), known-case count.
No parameter schema on file.
Search Polymarket markets by keyword (e.g. 'election', 'fed', 'bitcoin'). Returns question, slug, 24h volume, liquidity, end date.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Keyword to search |
| limit | integer | no | Max results (default 10, max 50) |
| active_only | boolean | no | Only active / non-closed markets |
Full market info: outcomes, outcome prices, volume, liquidity, best bid/ask, spread, resolution source, conditionId. Provide 'slug' or 'id'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Market slug |
| id | string | no | Market id / conditionId |
Volume anomaly heuristic: compares 24h volume vs average daily volume since market start (z-like ratio) and flags thin-book situations where 24h volume >> on-book liquidity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | — |
| id | string | no | — |
Multi-signal integrity scan: combines thin-book flag, spread, low liquidity, geopolitical-term pattern, end-date proximity, and 24h volume concentration. Returns score 0-100, level HIGH/MEDIUM/LOW/CLEAN, triggered signals, and an operational recommendation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | — |
| id | string | no | — |
Top Polymarket markets by 24h volume. Useful for daily compliance triage / catching news catalysts before they land in mainstream coverage.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max results (default 10, max 25) |
Registry of publicly reported prediction-market integrity cases (Théo / French whale, Hyperliquid whale, Venezuela, Iran strikes, Nuclear, UMA Ukraine). Filter by category or minimum AML relevance (low/medium/high). Summaries only — no accusations against named parties.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Optional category substring (e.g. 'geopolitical', 'oracle') |
| min_aml_relevance | string | no | Minimum AML relevance |
Polygon wallet base profile via JSON-RPC (Ankr-backed when RPC_POLYGON is set, public fallback otherwise). Returns MATIC balance, outbound tx count, contract-vs-EOA detection, and a lightweight risk heuristic.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Polygon address (0x + 40 hex chars) |
Screen a named entity against global sanctions lists (OFAC SDN, EU FSF, UN SC, Interpol). Delegates to AMLOracle. Use after resolving a wallet/trader to a real name via public reporting or known-case registry.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Person or entity name |
| entity_type | string | no | Optional: 'person' or 'organization' |
| threshold | number | no | Optional fuzzy-match threshold (0..1) |
Politically Exposed Person (PEP) check via Wikidata. Delegates to AMLOracle. Relevant for prediction markets where reported traders overlap with political figures.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Person name |
| country | string | no | Optional ISO country code |
Adverse media scan — negative news on fraud, money laundering, corruption, sanctions. Delegates to AMLOracle. Core building block for evidence chains that link a wallet or trader to publicly reported concerns (always cite the source, never attribute).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Person or entity name |
| lang | string | no | Optional language (e.g. en, de) |
| limit | integer | no | Max results (default upstream) |
Full KYC bundle for a named entity: sanctions + PEP + adverse media + country risk in a single call. Delegates to AMLOracle.kyc_bundle.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| country | string | no | ISO country code |
| entity_type | string | no | 'person' or 'organization' |
Issue a cryptographically signed, on-chain anchored integrity alert for a Polymarket market. Combines evidence_anchor + get_signed_fact from FeedOracle Trust Layer. Alerts are anchored on Polygon with an ECDSA signature and are externally verifiable via pg_verify_alert and the JWKS at feedoracle.io/.well-known/jwks.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| market_slug | string | yes | Polymarket market slug |
| claim | string | yes | Short human-readable claim being asserted |
| severity | string | no | Alert severity |
| signals | array | no | List of integrity signals triggered |
| wallets | array | no | Optional list of related wallet addresses |
Complete forensic dossier for a single Polymarket market: market details + integrity scan + volume anomaly profile + Trust Layer provenance trace — aggregated into one dossier ready for manual review, press inquiry, or as input to a SAR report.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Market slug |
| id | string | no | Market id / conditionId |
Verify a previously issued signed alert (JWS or content-hash). Delegates to Trust Layer verify_signature. Returns validity, signer, and timestamp. JWKS at feedoracle.io/.well-known/jwks.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jws | string | no | Full JWS string |
| content_hash | string | no | SHA-256 content hash (alternative to JWS) |
Resolve a Polygon address to a known entity via PredictionGuard's Wallet Registry (Polymarket core contracts, major stablecoins, known CEX hot wallets), falling back to on-chain heuristic classification for unknown addresses. Returns entity name, type, category, AML relevance, confidence, and source-of-record URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Polygon address (0x + 40 hex chars) |
Aggregated A–F risk profile for a Polygon wallet. Combines on-chain behavior (pg_wallet_lookup), entity resolution (pg_wallet_entity_resolve), and — where the entity can be screened — AML bundle (sanctions + PEP + adverse media via AMLOracle). Grade A = clean, F = blocked. Includes triggered flags with points deductions for full auditability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Polygon address (0x + 40 hex chars) |
Add a Polygon wallet to the PredictionGuard watchlist. Takes an initial baseline snapshot so subsequent pg_whale_scan calls can detect movement. Set alert_threshold_matic to tune sensitivity (default 100 MATIC). Tags are free-form.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Polygon address (0x + 40 hex) |
| alias | string | no | Optional human-readable label |
| alert_threshold_matic | number | no | Balance delta threshold in MATIC for alerts (default 100) |
| tags | array | no | Free-form tags (e.g. ['polymarket','pre-election','whale']) |
| notes | string | no | Free-form notes |
Remove a wallet from the watchlist. By default keeps historical snapshots and alerts (for audit trail). Set keep_history=false to purge everything for this address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | — |
| keep_history | boolean | no | Keep snapshot + alert history (default true) |
List all watched wallets with their alias, threshold, tags, notes, and last snapshot. Optionally filter by tag.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max results (max 500) |
| tag | string | no | Optional tag filter |
Scan one or all watched wallets against Polygon RPC. Compares current balance + nonce to the last snapshot, writes a new snapshot, and emits an alert when the delta exceeds the wallet's configured threshold. Severity is MEDIUM / HIGH / CRITICAL by delta size. Omit 'address' to scan the entire watchlist. Designed to be called periodically via SchedulerOracle or a systemd timer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | Optional — scan a single address. Omit to scan the whole list. |
Retrieve alerts from the watchlist audit log. Filter by address, severity (LOW/MEDIUM/HIGH/CRITICAL), and/or ISO timestamp 'since'. Default returns the 50 most recent alerts across the whole watchlist.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | — |
| severity | string | no | — |
| since | string | no | ISO 8601 timestamp (e.g. 2026-04-20T00:00:00Z) |
| limit | integer | no | Max results (max 500) |
Global UMA Optimistic Oracle health on Polygon. Scans event logs from OOv2 (and optionally OOv1) over a configurable window, tallies events by type (RequestPrice / ProposePrice / DisputePrice / Settle), computes per-hour rate, and derives a dispute/propose ratio — a leading indicator of oracle-level contention.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| blocks_back | integer | no | Blocks to scan back (default 5000 ≈ 3h, max 20000) |
| include_v1 | boolean | no | Also scan UMA OOv1 (legacy, default false) |
Resolution source and phase for a specific Polymarket market. Fetches market metadata from Gamma, extracts the resolutionSource address, verifies it's a deployed contract on Polygon, and classifies the resolution phase (active_trading / approaching_resolution / imminent_resolution_window / past_end_awaiting_resolution / resolved).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Market slug |
| id | string | no | Market id / conditionId |
Multi-signal resolution-risk score (0–100, CLEAN/LOW/MEDIUM/HIGH/CRITICAL) for a Polymarket market. Combines category priors (geopolitical/election/sanctions patterns from pg_known_cases), resolution-phase proximity, market volume, resolution-source sanity check (is the UMA adapter a real deployed contract), UMA global dispute ratio, and thin-book flag. Returns triggered signals with point deducti
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | — |
| id | string | no | — |
Generate a draft Suspicious Activity Report (SAR/STR) from structured inputs. Supports EU_GENERIC (FATF-aligned STR, default), US_FINCEN (Form 111 structure), and DE_goAML (German FIU draft). Takes subject, market, activity window, integrity signals, and evidence references — auto-classifies the primary suspicious activity type, generates a narrative, and renders regulator-style markdown. Output i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | object | yes | Required. The subject of the report. |
| market | object | no | Optional. Polymarket market context. |
| activity | object | no | Activity window and amounts. |
| signals | array | no | Integrity signals (strings or objects with 'term'/'reason'/'layer'). Pass the 'triggered_signals' array from pg_market_integrity_scan or pg_resolution_risk_score directly. |
| evidence | object | no | References to prior evidence. |
| filer | object | no | Information about the preparing institution. |
| filing_jurisdiction | string | no | Report format. Default EU_GENERIC. |
| narrative_addendum | string | no | Optional free-text addendum from the analyst. |
Raw trade access for a Polymarket market via the Polymarket Data API. Supports client-side filters: time range (from/to, ISO 8601), side (BUY/SELL), minimum trade size, or a specific wallet. Paginates server-side (max 25 pages × 1000 trades). Returns compact records with wallet, pseudonym, side, size, price, notional USD, outcome, timestamp, tx_hash.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Polymarket market slug |
| id | string | no | Market id / conditionId |
| limit | integer | no | Max trades to return after filtering (default 100, max 5000) |
| max_pages | integer | no | How many pages of 1000 to fetch (default 2, max 25) |
| from | string | no | Only include trades from this ISO timestamp |
| to | string | no | Only include trades up to this ISO timestamp |
| side | string | no | Only trades on this side |
| min_size | number | no | Minimum trade size (shares) |
| wallet | string | no | Filter to a single wallet address |
Analyze pre-resolution positioning on a Polymarket market. For the N days before the market's endDate, aggregates trades by wallet, classifies wallets new to the market in that window, detects volume concentration, timing clusters (minutes where ≥5 distinct wallets trade in sync), and pre-event volume spikes vs historical average. Returns a 0–100 risk score (CRITICAL/HIGH/MEDIUM/LOW/CLEAN) with tr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | — |
| id | string | no | — |
| days_before_end | number | no | Pre-event window size in days (1–90, default 7) |
| max_pages | integer | no | Trade pagination depth (default 10, max 25) |
Real-time insider-trading signal scan for a single Polymarket market. Aggregates 5 signals: (1) very large pre-event positions, (2) high ratio of wallets new to this market, (3) coordinated minute-bucket timing clusters, (4) one-sided positioning, (5) sensitive-keyword category match (military/regime/intel). Returns a 0-100 score (CLEAN/LOW/MEDIUM/HIGH/CRITICAL), triggered signals with evidence, t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Polymarket market slug |
| id | string | no | Market id / conditionId |
| window_hours | integer | no | Pre-event window to analyze (default 72h) |
| min_position_usd | number | no | Min notional to flag (default $1000) |
Find wallets that co-trade across multiple sensitive Polymarket markets with a target wallet. Given a wallet and 2-10 market slugs, returns: which markets the target traded, top 20 cotraders ranked by overlap count, and an aggregate severity score (≥3 shared markets = MEDIUM, ≥5 = HIGH). Use case: detect coordinated trading rings, shared-info syndicates, or wallet clusters that consistently bet on
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | Target wallet address (0x + 40 hex) |
| markets | array | yes | 2-10 market slugs to check for co-trading overlap |
Statistical timing analysis of a single wallet's position on a specific market. Checks: (1) how close to resolution the wallet entered (<6h=35pts, <24h=25pts, <72h=10pts), (2) position size vs market average (>20× avg=25pts, >5× avg=10pts), (3) single-bet pattern (≤3 trades=10pts, no historical trading rationale). Returns 0-100 score, first-trade timestamp, total notional, and methodology. Pair wi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Market slug |
| id | string | no | Market id / conditionId |
| wallet | string | yes | Wallet to analyze (0x + 40 hex) |
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-matche
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Market slug |
| id | string | no | Market id / conditionId |
| wallet | string | yes | Wallet to score (0x + 40 hex) |
Daily compliance triage: scans top Polymarket markets by 24h volume and flags those whose question text matches curated sensitive-keyword categories — military action, regime change, leadership death, diplomacy, intelligence ops, monetary policy, regulatory action. Returns flagged markets with monitoring severity (HIGH/MEDIUM/LOW), matched categories and keywords, and volume. Pair flagged HIGH mar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max markets to scan (default 25, max 100) |
| category | string | no | Optional: filter to one category (military_action, regime_change, leadership_death, diplomacy, intelligence, monetary_policy, regulatory_action) |
Search Kalshi prediction markets (CFTC-regulated event contracts). Returns events ranked by aggregate 24h volume across all markets in the event. Kalshi categories include Elections, Politics, Economics, Climate, Sports, Entertainment, Financials. Public data, no auth needed. Each event has one or more child markets (mutually exclusive or yes/no).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Keyword search in title, sub_title, event_ticker |
| category | string | no | Optional category filter (Elections, Politics, Economics, ...) |
| status | string | no | — |
| limit | integer | no | Max events to return (default 25, max 100) |
Detailed Kalshi market or event info. Pass 'ticker' for a single market (returns yes/no bids+asks, last price, volume, OI, spread, hours until close) or 'event_ticker' for all markets in an event (multi-outcome). Includes the rules_primary text (Kalshi's settlement criteria) which is critical for understanding resolution risk.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | no | Kalshi market ticker (e.g. KXG7LEADEROUT-45JAN01-DJT) |
| event_ticker | string | no | Kalshi event ticker (returns all child markets) |
Top trending Kalshi events ranked by aggregate 24h volume across child markets. Filterable by category. Daily-briefing-ready output. Includes the highest-volume sub-market per event.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Optional category filter (Elections, Politics, ...) |
| limit | integer | no | Max events to return (default 25, max 50) |
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 ask
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | Kalshi market ticker |
Scan all open Kalshi markets and flag those that are manipulation-vulnerable: closing soon (<24h), low open interest, low liquidity, wide spread, low volume. Daily triage tool. Returns markets ranked by risk_score (≥30 threshold). Best paired with pg_kalshi_resolution_calendar for full compliance briefing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Optional category filter |
| max_results | integer | no | Max flagged markets (default 25, max 50) |
Compliance briefing: which Kalshi markets resolve in the next N hours? Bucketed by 6h, 24h, 48h, 1 week. Flags markets in CFTC-sensitive categories (Elections, Politics). Use for daily surveillance prep — markets near resolution have highest insider-trading risk window.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hours_ahead | integer | no | Look-ahead window (default 48h, max 168h) |
| min_open_interest | number | no | Only markets with at least this OI |
| category | string | no | Optional category filter |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | no | Kalshi market ticker |
| event_ticker | string | no | Or event_ticker for the whole event |
| candidate_name | string | no | Optional: specific person's name to match against title (e.g. 'Mark Moran') |
Pre-trade integrity gate for AI agents and compliance teams. ONE call returns ALLOW/WARN/BLOCK decision + risk_level (0-100) + signed evidence receipt. Aggregates orderbook analysis, resolution-window risk, CFTC Rule 5.17(z) conflict-of-interest check, and (Polymarket) insider signal scan. Supports both Polymarket (slug) and Kalshi (ticker). Optional inputs: wallet (Polymarket-side checks), candid
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platform | string | yes | Which prediction market |
| market_id | string | yes | Polymarket slug or Kalshi ticker/event_ticker |
| wallet | string | no | Optional: Polygon wallet address (Polymarket only) |
| candidate | string | no | Optional: candidate name for Kalshi Rule 5.17(z) name match |
| amount_usd | number | no | Optional: bet size for risk amplification |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Predictionguard or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest3e2f10f2713454829e25a4cfc81ecca02347c268dfebe5e0644c7f63a86bface
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| pg_overview | no tags | |
| pg_market_search | no tags | |
| pg_market_details | no tags | |
| pg_market_volume_profile | no tags | |
| pg_market_integrity_scan | no tags | |
| pg_trending_markets | no tags | |
| pg_known_cases | no tags | |
| pg_wallet_lookup | no tags | |
| pg_sanctions_screen_entity | no tags | |
| pg_pep_check_entity | no tags | |
| pg_adverse_media_entity | no tags | |
| pg_kyc_bundle_entity | no tags | |
| pg_insider_alert_signed | no tags | |
| pg_evidence_bundle_market | no tags | |
| pg_verify_alert | no tags | |
| pg_wallet_entity_resolve | no tags | |
| pg_wallet_risk_profile | no tags | |
| pg_whale_add | no tags | |
| pg_whale_remove | no tags | |
| pg_whale_list | no tags | |
| pg_whale_scan | no tags | |
| pg_whale_alerts | no tags | |
| pg_uma_status | no tags | |
| pg_uma_market_resolution | no tags | |
| pg_resolution_risk_score | no tags | |
| pg_sar_report | no tags | |
| pg_market_trades | no tags | |
| pg_pre_event_flow_analysis | no tags | |
| pg_insider_signal_scan | no tags | |
| pg_wallet_correlation_match | no tags | |
| pg_position_timing_anomaly | no tags | |
| pg_information_advantage_score | no tags | |
| pg_classified_keyword_match | no tags | |
| pg_kalshi_search | no tags | |
| pg_kalshi_market_details | no tags | |
| pg_kalshi_trending | no tags | |
| pg_kalshi_orderbook_analysis | no tags | |
| pg_kalshi_thin_market_alert | no tags | |
| pg_kalshi_resolution_calendar | no tags | |
| pg_kalshi_conflict_of_interest_check | no tags | |
| pg_prediction_market_integrity_gate | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest3e2f10f271345482
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Predictionguard can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.