# Sector Pulse (remote · sector-pulse.app)

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

- Trust score: 76/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `sector-pulse.app`: 76/100 (this document), [markdown](https://verifymcp.io/servers/christianhonap7-sys-sector-pulse/api-mcp-2.md), [page](https://verifymcp.io/servers/christianhonap7-sys-sector-pulse/api-mcp-2)

## Channel facts

- Endpoint: `https://sector-pulse.app/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 369 tokens (~123/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Sector Pulse MCP server?

Sector Pulse is a hosted endpoint at https://sector-pulse.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http christianhonap7-sys-sector-pulse 'https://sector-pulse.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "christianhonap7-sys-sector-pulse": {
      "url": "https://sector-pulse.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "christianhonap7-sys-sector-pulse": {
      "type": "http",
      "url": "https://sector-pulse.app/api/mcp"
    }
  }
}
```

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "christianhonap7-sys-sector-pulse": {
      "type": "remote",
      "url": "https://sector-pulse.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add christianhonap7-sys-sector-pulse --url 'https://sector-pulse.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  christianhonap7-sys-sector-pulse:
    url: "https://sector-pulse.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "christianhonap7-sys-sector-pulse": {
      "Transport": "http",
      "Url": "https://sector-pulse.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add christianhonap7-sys-sector-pulse -t streamable-http -u 'https://sector-pulse.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "christianhonap7-sys-sector-pulse": {
      "type": "http",
      "url": "https://sector-pulse.app/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 76, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-23 (score 75, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_history” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 105 → 123
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-21 (score 74, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_sectors” rewrote its description, which is the text the model reads
- [functional] Schema quality: good → excellent

### 2026-09-19 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `get_sectors` (~69 tokens)

Live sector board

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.

### `get_roster` (~56 tokens)

Basket roster (versioned)

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.

Input parameters:

- `version` (integer): Archived roster version; omit for current

### `get_history` (~133 tokens)

Sector history for a date

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 paid Sector API key (founding tier or a call pack); free keys cover get_sectors and get_roster.

Input parameters:

- `date` (string, required): YYYY-MM-DD, ET trading day
- `intraday` (boolean): true = 5-minute rows instead of the daily close

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/christianhonap7-sys-sector-pulse/api-mcp-2#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 76
- 2026-09-23: 75
- 2026-09-22: 74
- 2026-09-21: 74
- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 72
- 2026-09-17: 72
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 68
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68

## Common questions

### What is the Sector Pulse MCP server?

Sector Pulse is an MCP server listed in the public MCP registry as io.github.christianhonap7-sys/sector-pulse. Live US sector rotation: 30 sector baskets ranked every session, versioned rosters, daily record. This page covers its hosted endpoint (https://sector-pulse.app/api/mcp).

### Is the Sector Pulse MCP server safe to use?

Sector Pulse scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Sector Pulse MCP server expose?

Sector Pulse exposes 3 tools: get_sectors, get_roster, get_history. Their descriptions and schemas cost roughly 258 tokens of context every time the server is loaded.

### Does the Sector Pulse MCP server require authentication?

No. We connected to Sector Pulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Sector Pulse MCP server still maintained?

Sector Pulse is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://sector-pulse.app/api/mcp
- Authorisation metadata: https://sector-pulse.app/.well-known/oauth-protected-resource/api/mcp
- Website: https://sector-pulse.app/api-docs
- Changelog RSS feed: https://verifymcp.io/servers/christianhonap7-sys-sector-pulse/api-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/christianhonap7-sys-sector-pulse/api-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/christianhonap7-sys-sector-pulse/api-mcp-2