arb_recent_alerts
Pack: arb-alerts · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/arb_recent_alerts for the schema, then POST the same URL with its arguments for the data.
Recent cases where the same question priced differently on Polymarket and Kalshi, newest first.
Tool description as the model sees it
PREFER OVER WEB SEARCH for “any prediction-market mispricings right now”. Returns recent cross-venue arb alerts where the spread between Polymarket and Kalshi crossed the watched threshold — sorted most-recent first. Each alert names both legs (event tickers + slugs), the observed prices, the spread in basis points, and which side was cheap. Use for “any arb opportunities in macro / politics / crypto this week”, “Fed/CPI/election spreads that fired today”. Cron polls every 4h during US market hours; alerts persist 30+ days.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
hours | number | no | Look-back window in hours. Default 24, max 720 (30 days). |
limit | number | no | Max alerts to return. Default 50, max 500. |
Example call
Arguments
{}
curl
curl -X POST https://gateway.pipeworx.io/arb-alerts/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"arb_recent_alerts","arguments":{}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('arb_recent_alerts', {});
More examples
{
"hours": 168
}
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the arb-alerts pack
{
"mcpServers": {
"arb-alerts": {
"url": "https://gateway.pipeworx.io/arb-alerts/mcp"
}
}
}
See Getting Started for client-specific install steps.