Analytics
spectre.markets
An MCP server providing SPECTRE Markets instrument lists, daily price levels, and ranked session path trade ideas for financial instruments.
ENDPOINT 1
https://spectre.markets/mcp
MCP server metadata
- Name
- spectre-markets
Live index-options levels and session scenarios from SPECTRE Markets (spectre.markets). Free tier only: the regime, the named free levels, a read excerpt, and today's ranked paths with their trade ideas. Research/education only, not financial advice. Levels, not calls.
Known tools 3
list_symbolsList the instruments SPECTRE Markets publishes a levels board for, with the session each board is for and a link to the full board.
Inferred read-onlyget_pathsToday's ranked possible session paths for one instrument, each with its waypoints and a trade idea (entry zone, invalidation, target).
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.spectre-markets]
url = "https://spectre.markets/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"spectre-markets": {
"type": "http",
"url": "https://spectre.markets/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: spectre-markets
Remote MCP URL: https://spectre.markets/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"spectre-markets": {
"url": "https://spectre.markets/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"spectre-markets": {
"type": "http",
"url": "https://spectre.markets/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "spectre-markets",
"transport": "streamable-http",
"url": "https://spectre.markets/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.