Ranked active signals across security, crypto, environment, tech, and more.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Get current data for one sector. Sector slugs from list_active_signals output.
e.g. nvd-new-cves-count, kraken-btc-usd
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http volatiai-mcp https://volatiai-mcp.fourieranalys.workers.dev/mcp
Get current data for one sector. Sector slugs from list_active_signals output.
| Argument | Type | Description |
|---|---|---|
| sector |
| string |
| e.g. nvd-new-cves-count, kraken-btc-usd |
{
"type": "object",
"required": [
"sector"
],
"properties": {
"sector": {
"type": "string",
"description": "e.g. nvd-new-cves-count, kraken-btc-usd"
}
}
}List ranked active signals from VolatiAI (severity x confidence x magnitude x novelty). Filter by severity or category.
| Argument | Type | Description |
|---|---|---|
| limit | integer | |
| category | string | Security, Crypto, Environment, Tech, Markets, Health, Governance, or Other |
| severity | string |
{
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 25,
"maximum": 100,
"minimum": 1
},
"category": {
"type": "string",
"description": "Security, Crypto, Environment, Tech, Markets, Health, Governance, or Other"
},
"severity": {
"enum": [
"info",
"notice",
"warning",
"alert",
"critical"
],
"type": "string"
}
}
}List signal categories with counts.
No arguments.
{
"type": "object",
"properties": {}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 8, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.