Pointcast
NPM · POINTCAST
Talk and Alt+click on your web app: your agent gets the exact elements and the code behind them.
Available components
Last scanned (2 hours ago)
Scores higher than 58% of npm servers
Category Developer Tools
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 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 4 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 15 Oct 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.
- 13 Oct 26 +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.
- 11 Oct 26 +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.
- 6 Oct 26 +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.
- 3 Oct 26 +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.
- 30 Sept 26 +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.
- 29 Sept 26 +14
- Known CVEs: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: 0.84 → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- 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 functional
- 28 Sept 26 56
First indexed and scored.
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 17 Oct 2026 · Analysed npm/pointcast@0.8.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_element ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | Event id within the session, e.g. "e3". |
| id | string | yes | 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. |
No output schema declared.
No examples provided.
get_session ~230
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 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… |
No output schema declared.
No examples provided.
list_sessions ~114
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
wait_for_recording ~330
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
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.
npm · pointcast
claude mcp add hugelidus-pointcast -- npx -y pointcast
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.