Sector Pulse
REMOTE · SECTOR-PULSE.APP · SCANNED SEP 25
Live US sector rotation: 30 sector baskets ranked every session, versioned rosters, daily record.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 369 tokens (~123/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · sector-pulse.app
claude mcp add --transport http christianhonap7-sys-sector-pulse 'https://sector-pulse.app/api/mcp'
{
"mcpServers": {
"christianhonap7-sys-sector-pulse": {
"url": "https://sector-pulse.app/api/mcp"
}
}
} {
"servers": {
"christianhonap7-sys-sector-pulse": {
"type": "http",
"url": "https://sector-pulse.app/api/mcp"
}
}
} [mcp_servers.christianhonap7-sys-sector-pulse] url = "https://sector-pulse.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"christianhonap7-sys-sector-pulse": {
"type": "remote",
"url": "https://sector-pulse.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add christianhonap7-sys-sector-pulse --url 'https://sector-pulse.app/api/mcp' --transport streamable-http
mcp_servers:
christianhonap7-sys-sector-pulse:
url: "https://sector-pulse.app/api/mcp" {
"McpServers": {
"christianhonap7-sys-sector-pulse": {
"Transport": "http",
"Url": "https://sector-pulse.app/api/mcp"
}
}
} assistant mcp add christianhonap7-sys-sector-pulse -t streamable-http -u 'https://sector-pulse.app/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 23 Sept 26 +1
- 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 security
- Schema quality: 105 → 123 ▼ functional
- Server version: 1.0.0 → 1.3.0 functional
- 21 Sept 26 +1
- 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 security
- Schema quality: good → excellent functional
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://sector-pulse.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sector-pulse.app | CN=YR2,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | RSA 2048 | SHA256-RSA | 616a5db583973e659477a26ae2f3c113aeb |
| SANs: sector-pulse.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sector-pulse.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| sector-pulse.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sector-pulse.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://sector-pulse.app/api/mcp | HTTPS enforced | 308 | https://sector-pulse.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_history Sector history for a date ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | YYYY-MM-DD, ET trading day |
| intraday | boolean | – | true = 5-minute rows instead of the daily close |
No output schema declared.
No examples provided.
get_roster Basket roster (versioned) ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| version | integer | – | Archived roster version; omit for current |
No output schema declared.
No examples provided.
get_sectors Live sector board ~69
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.