Sector Pulse MCP Server

by christianhonap7-sys Your server? Claim it

not responding

Sector Pulse is listed as active in the registry but did not answer our last check. It exposes 3 tools.

Live US sector rotation: 30 sector baskets ranked every session, versioned rosters, daily record.

Uptime history 15 days of history · worst day 2%

15 days agonow

2.2%

Uptime 24h

2 of 92 checks

Tools

read from the server

419 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 September 2026. No other catalogue keeps this.

21 Sep a tool description was rewritten get_sectors

Sector Pulse does not always answer

Over the last week it answered 11.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add sector-pulse --transport http https://sector-pulse.app/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "sector-pulse": {
      "url": "https://sector-pulse.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.sector-pulse]
url = "https://sector-pulse.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "sector-pulse": {
      "url": "https://sector-pulse.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "sector-pulse": {
      "url": "https://sector-pulse.app/api/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

history

get_history

Daily close record for one date (rank, % move, breadth per sector; close ranks only before 2026-07-31), or the 5-minute intraday rows with intraday=true. Daily from 2026-07-21, intraday from 2026-08-19, never backfilled. Requires a Sector API key.

roster

get_roster

The ticker lists behind each sector basket, versioned and immutable: pass a version to see exactly what a basket contained at that time. Requires a Sector API key.

sectors

get_sectors

All 30 Sector Pulse baskets right now: average % move, median, breadth, and three rank bases per sector (session rank, close-basis rank, previous close rank). Same data as the public board. Requires a Sector API key; a free key comes by email from the docs page.

Endpoints

URL	Transport	State	Latency	Checked
https://sector-pulse.app/api/mcp	streamable-http	answering	32 ms	0 min ago

Alternatives to Sector Pulse

same job, measured the same way

Crumbtrail

by crumbtraildev

Recorded browser sessions, backend spans, and database row diffs as one ranked fix bundle.

97 installs/wk local only

Contractorroster

by contractorroster

Verified US licensed-contractor data: 879k+ state-board records, metered per record, free discovery.

5 tools answering

Nist Beacon

by pipeworx-io

NIST Randomness Beacon v2 — signed public random pulses every 60s.

40 tools answering

Alaska Jobs

by alaskajobs

Every public-sector job in Alaska, daily: search listings, salary data, state pay schedule.

6 tools answering

x402 Bazaar Rank

by mike-lblc

Ranked search over 15k+ live x402 services by real 30-day usage; free top-5, paid depth via x402.

2 tools answering

Minutes

by silverstein

The private, owned conversation-memory layer for AI. Record, transcribe, and search every meeting.

238 installs/wk local only

TechSnif

by techsnif

Agent-first tech news: ranked story clusters, coverage and discussion links, trends, and events.

35 installs/wk 13 tools answering

Data

by commonelements

Query 390,000+ HOA and condo association records, statutes, rosters, and flood risk data.

answering

Sector Pulse — questions

Answers built from our own checks of this server.

What can Sector Pulse do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_history, get_roster, get_sectors. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Sector Pulse working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 2 of 92 checks got a reply (2.2%), average response time 419 ms. The bar chart above shows every period we have measured.

The registry lists Sector Pulse as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Sector Pulse?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Sector Pulse need an API key?

No. Sector Pulse completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Sector Pulse?

It answers our handshake in 419 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.