# Capital Signal: ASX announcements (npm · capsig-mcp)

Every ASX announcement since 2018 as structured, source-linked data: raises, guidance, trades, cash.

- Trust score: 26/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `capitalsignal.io`: 39/100, [markdown](https://verifymcp.io/servers/io-capitalsignal-capital-signal/api-mcp.md), [page](https://verifymcp.io/servers/io-capitalsignal-capital-signal/api-mcp)
- npm · `capsig-mcp`: 26/100 (this document), [markdown](https://verifymcp.io/servers/io-capitalsignal-capital-signal/capsig-mcp.md), [page](https://verifymcp.io/servers/io-capitalsignal-capital-signal/capsig-mcp)

## Channel facts

- Registry: `npm`
- Package: `capsig-mcp`
- Version: `1.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license.
  - Actively maintained (last published 2 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the Capital Signal: ASX announcements MCP server?

Capital Signal: ASX announcements runs locally as an npm package, launched with npx -y capsig-mcp. 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 io-capitalsignal-capital-signal -- npx -y capsig-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "io-capitalsignal-capital-signal": {
      "command": "npx",
      "args": [
        "-y",
        "capsig-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-capitalsignal-capital-signal": {
      "command": "npx",
      "args": [
        "-y",
        "capsig-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add io-capitalsignal-capital-signal -- npx -y capsig-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-capitalsignal-capital-signal": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "capsig-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-capitalsignal-capital-signal --command npx --arg -y --arg capsig-mcp
```

### Hermes

```yaml
mcp_servers:
  io-capitalsignal-capital-signal:
    command: "npx"
    args: ["-y", "capsig-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "io-capitalsignal-capital-signal": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "capsig-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-capitalsignal-capital-signal -t stdio -c npx -a -y capsig-mcp
```

### Other

```json
{
  "mcpServers": {
    "io-capitalsignal-capital-signal": {
      "command": "npx",
      "args": [
        "-y",
        "capsig-mcp"
      ]
    }
  }
}
```

## 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-11-03 (score 26, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 11)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/io-capitalsignal-capital-signal/capsig-mcp#diagnostics

## Score history

- 2026-11-05: 26
- 2026-11-04: 26
- 2026-11-03: 26
- 2026-11-02: 11

## Common questions

### What is the Capital Signal: ASX announcements MCP server?

Capital Signal: ASX announcements is an MCP server listed in the public MCP registry as io.capitalsignal/capital-signal. Every ASX announcement since 2018 as structured, source-linked data: raises, guidance, trades, cash. This page covers its npm package (capsig-mcp).

### Is the Capital Signal: ASX announcements MCP server safe to use?

Capital Signal: ASX announcements scores 26 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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.

### Is the Capital Signal: ASX announcements MCP server still maintained?

Capital Signal: ASX announcements is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Capital Signal: ASX announcements MCP server under?

Capital Signal: ASX announcements declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

### What did VerifyMCP test on the Capital Signal: ASX announcements MCP server?

VerifyMCP ran 8 checks on Capital Signal: ASX announcements, covering Malware scan, Known CVEs, Install scripts, Dependency health and 4 more. 6 items could not be completed, a gap on our side rather than a finding about Capital Signal: ASX announcements: Security disclosure, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/capsig-mcp
- Socket report: https://socket.dev/npm/package/capsig-mcp
- Website: https://capitalsignal.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-capitalsignal-capital-signal/capsig-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-capitalsignal-capital-signal/capsig-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-capitalsignal-capital-signal/capsig-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-capitalsignal-capital-signal/capsig-mcp