# Pointcast (npm · pointcast)

Talk and Alt+click on your web app: your agent gets the exact elements and the code behind them.

- Trust score: 78/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- npm · `pointcast`: 78/100 (this document), [markdown](https://verifymcp.io/servers/hugelidus-pointcast/pointcast.md), [page](https://verifymcp.io/servers/hugelidus-pointcast/pointcast)

## Channel facts

- Registry: `npm`
- Package: `pointcast`
- Version: `0.8.1`
- 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-10-17.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 17 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 810 tokens (~202/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 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 4 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Pointcast MCP server?

Pointcast runs locally as an npm package, launched with npx -y pointcast. 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 hugelidus-pointcast -- npx -y pointcast
```

### Cursor

```json
{
  "mcpServers": {
    "hugelidus-pointcast": {
      "command": "npx",
      "args": [
        "-y",
        "pointcast"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hugelidus-pointcast": {
      "command": "npx",
      "args": [
        "-y",
        "pointcast"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add hugelidus-pointcast -- npx -y pointcast
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hugelidus-pointcast": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "pointcast"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hugelidus-pointcast --command npx --arg -y --arg pointcast
```

### Hermes

```yaml
mcp_servers:
  hugelidus-pointcast:
    command: "npx"
    args: ["-y", "pointcast"]
```

### Netclaw

```json
{
  "McpServers": {
    "hugelidus-pointcast": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pointcast"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add hugelidus-pointcast -t stdio -c npx -a -y pointcast
```

### Other

```json
{
  "mcpServers": {
    "hugelidus-pointcast": {
      "command": "npx",
      "args": [
        "-y",
        "pointcast"
      ]
    }
  }
}
```

## 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-10-15 (score 78, +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-10-13 (score 77, +1)

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

### 2026-10-11 (score 76, +3)

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

### 2026-10-06 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 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-10-03 (score 72, +1)

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

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

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

### 2026-09-29 (score 70, +14)

- [security regression] Known CVEs: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Dependency health: 0.84 → unverified
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.6.0 → 0.8.1
- [functional] Package version: 0.6.0 → 0.8.0
- [functional] Package version: 0.6.0 → 0.7.0

### 2026-09-28 (score 56)

First indexed and scored.

## MCP tools (4)

### `list_sessions` (~114 tokens)

List recent pointcast recordings, newest first: id, date, duration, the pages pointed at, how many requests and elements, a preview of the first request, whether its source files are in this project (matchesProject), and whether its spec is already on disk (rendered).

Input parameters:

- `limit` (integer): Max sessions to return (default 20).
- `repo` (string): Absolute path of the project the recording was made on, to find its code locations in. Default: the project this server was started for.

### `get_session` (~230 tokens)

Get a session's Markdown spec (session.md), rendering it from session.json + words.json if it is not on disk yet. Pass "latest-here" for the most recent recording made on this project, or "latest" for the most recent one of any project. Code locations are resolved against the project's source when the recording has them.

Input parameters:

- `id` (string, required): Session id (the folder name), "latest-here" (newest recording made on this project) or "latest" (newest of all).
- `repo` (string): Absolute path of the project the recording was made on, to find its code locations in. Default: the project this server was started for.
- `style` (string): How the spec tells you to apply the requests. "intent": build what a request for something new means, in the app's style; "precise": change only the elements pointed at, and only as asked. Default: w…

### `get_element` (~136 tokens)

Get the full captured details (ElementInfo) of one event in a session by its event id, with the page errors captured around it (stack frames included) when there were any.

Input parameters:

- `eventId` (string, required): Event id within the session, e.g. "e3".
- `id` (string, required): Session id (the folder name), "latest-here" (newest recording made on this project) or "latest" (newest of all).
- `repo` (string): Absolute path of the project the recording was made on, to find its code locations in. Default: the project this server was started for.

### `wait_for_recording` (~330 tokens)

Wait for the user's next pointcast recording and return its spec. Use when the user asks you to listen/watch for recordings; after applying one, call it again to keep listening. Returns as soon as a new recording arrives (the user pressed Stop in the extension), with the same spec and warnings as get_session, or after timeoutSeconds with "No new recording yet": that is not an error, call it again to keep listening. By default only recordings made on this project count (as with get_session's "latest-here"); anyProject: true returns every recording.

Input parameters:

- `anyProject` (boolean): Return recordings from any project. Default false: recordings whose source files are all missing from this project are skipped (and left for an agent session on the right project); ones that name no…
- `repo` (string): Absolute path of the project the recording was made on, to find its code locations in. Default: the project this server was started for.
- `style` (string): How the spec tells you to apply the requests. "intent": build what a request for something new means, in the app's style; "precise": change only the elements pointed at, and only as asked. Default: w…
- `timeoutSeconds` (integer): How long to wait, at most 1500. Default: what this client allows a tool call (540 for Claude Code and Gemini CLI, 50 for others).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/hugelidus-pointcast/pointcast#diagnostics

## Score history

- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 77
- 2026-10-13: 77
- 2026-10-12: 76
- 2026-10-11: 76
- 2026-10-06: 73
- 2026-10-04: 72
- 2026-10-03: 72
- 2026-10-02: 71
- 2026-10-01: 71
- 2026-09-30: 71
- 2026-09-29: 70
- 2026-09-28: 56

## Common questions

### What is the Pointcast MCP server?

Pointcast is an MCP server listed in the public MCP registry as io.github.Hugelidus/pointcast. Talk and Alt+click on your web app: your agent gets the exact elements and the code behind them. This page covers its npm package (pointcast).

### Is the Pointcast MCP server safe to use?

Pointcast scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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.

### What tools does the Pointcast MCP server expose?

Pointcast exposes 4 tools: list_sessions, get_session, get_element, wait_for_recording. Their descriptions and schemas cost roughly 810 tokens of context every time the server is loaded.

### Is the Pointcast MCP server still maintained?

Pointcast is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Pointcast MCP server under?

Pointcast declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/pointcast
- Socket report: https://socket.dev/npm/package/pointcast
- Repository: https://github.com/Hugelidus/pointcast
- Changelog RSS feed: https://verifymcp.io/servers/hugelidus-pointcast/pointcast.xml
- Changelog JSON feed: https://verifymcp.io/servers/hugelidus-pointcast/pointcast.json
- HTML version of this page: https://verifymcp.io/servers/hugelidus-pointcast/pointcast