Pinpoint
NPM · PINPOINT-BRIDGE
Click an element in your running app or iOS Simulator, say what should change; your agent gets it.
Available components
Last scanned (13 hours ago)
Scores higher than 62% of npm servers
Category Browser Automation
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to gowtham012/PinPoint). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability47
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 967 tokens (~107/item across 9 items; 8 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clear_annotations" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 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.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.7.1 → 0.7.2 functional
- 20 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.7.0 → 0.7.1 functional
- 19 Oct 26 +11
- Stability: 0.50 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: gowtham012/PinPoint security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.6.0 → 0.7.0 functional
- 18 Oct 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Tool coverage: 75% → 70% ▼ functional
- Schema quality: 788 → 919 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: pass → unverified ▼ functional
- Package version: 0.5.0 → 0.6.0 functional
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 24 Oct 2026 · Analysed npm/pinpoint-bridge@0.7.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | gowtham012/PinPoint |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/gowtham012/PinPoint/.github/workflows/release.yml@refs/tags/v0.7.2 |
| Rekor log index | 3358580061 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a39ed8e04ca00d35867db026425b3d3954f5f97b6db51d41bd473fbba0b83377e0ebf02cc0ec839f82dc6737f5d17c8869e53c79aac59fa3279ae487e |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
clear_annotations Clear annotations ~16
Delete all annotations (pending and resolved).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_annotation Get one annotation ~38
Full details and screenshot for a single annotation by id or number.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Annotation id (8 chars) or its pin number |
No output schema declared.
No examples provided.
get_pending_annotations Get pending annotations ~46
Return every pending annotation (comment + element details + screenshot) as a markdown task list. Use this first.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | – | Only annotations whose page URL starts with this |
No output schema declared.
No examples provided.
list_annotations List annotations ~26
One-line summary per annotation. Defaults to pending only.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
No output schema declared.
No examples provided.
recheck_annotation Re-check an annotation against the live page ~117
Ask the developer's browser to find this element again, right now, and report what changed since they marked it — with a fresh crop next to the original one. Call it before editing anything marked a while ago, and whenever an annotation says it may be stale. A verdict of gone or moved means the selector in the annotation should not be trusted as-is.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Annotation id (8 chars) or its pin number |
| timeoutSeconds | number | – | How long to wait for the browser. Default 10 |
No output schema declared.
No examples provided.
reply_annotation Ask the developer about a note ~131
Ask the developer a question about an annotation instead of resolving it — when the request is ambiguous, or you need a decision before you change code. They read your message on the pin in their browser and answer there; the note then comes back to you as pending with the whole conversation attached (it reaches wait_for_annotation and the Claude Code hook like a new note). Until they answer it is off the pending list. Never use this to report a finished change — that is resolve_annotation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| message | string | yes | Your question or message, shown to the developer on the pin |
No output schema declared.
No examples provided.
resolve_annotation Resolve annotation ~153
Mark an annotation done after applying the change. Always call this when you have made the change. `note` is REQUIRED and is not bookkeeping: the developer reads it in their browser as your reply to what they asked for, next to their original note. Say what you actually changed and where — e.g. "Made the field full-width below 640px in Hero.tsx:42 and added the hint text". "Done" or "Fixed" is not an answer. If you could not do it, say that here instead.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| note | string | yes | Your reply to the developer, shown in their browser: what changed and where, or why it could not be done |
No output schema declared.
No examples provided.
wait_for_annotation Wait for the next annotation ~77
Block until the developer adds a new annotation in the browser (or timeout). Useful for a live 'watch' loop: wait → apply → resolve → wait. Each new annotation is handed to exactly one waiting agent, so several agents can watch at once without doing the same note twice.
| Name | Type | Req | Description |
|---|---|---|---|
| timeoutSeconds | number | – | Default 120 |
No output schema declared.
No examples provided.
How do I install the Pinpoint MCP server?
Pinpoint runs locally as an npm package, launched with npx -y pinpoint-bridge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pinpoint-bridge
claude mcp add gowtham012-pinpoint -- npx -y pinpoint-bridge
What is the Pinpoint MCP server?
Pinpoint is an MCP server listed in the public MCP registry as io.github.gowtham012/pinpoint. Click an element in your running app or iOS Simulator, say what should change; your agent gets it. This page covers its npm package (pinpoint-bridge).
Is the Pinpoint MCP server safe to use?
Pinpoint scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 24 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Pinpoint MCP server expose?
Pinpoint exposes 8 tools: get_pending_annotations, list_annotations, get_annotation, recheck_annotation, resolve_annotation, and 3 more. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.
Is the Pinpoint MCP server still maintained?
Pinpoint is still listed as active in the MCP registry. We last reached this channel on 24 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 Pinpoint MCP server under?
Pinpoint declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.