# Pinpoint (npm · pinpoint-bridge)

Click an element in your running app or iOS Simulator, say what should change; your agent gets it.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `pinpoint-bridge`
- Version: `0.7.2`
- 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-24.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to gowtham012/PinPoint).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 47/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 967 tokens (~107/item across 9 items; 8 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 70% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 10 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 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.

### Claude

```bash
claude mcp add gowtham012-pinpoint -- npx -y pinpoint-bridge
```

### Cursor

```json
{
  "mcpServers": {
    "gowtham012-pinpoint": {
      "command": "npx",
      "args": [
        "-y",
        "pinpoint-bridge"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "gowtham012-pinpoint": {
      "command": "npx",
      "args": [
        "-y",
        "pinpoint-bridge"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add gowtham012-pinpoint -- npx -y pinpoint-bridge
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add gowtham012-pinpoint --command npx --arg -y --arg pinpoint-bridge
```

### Hermes

```yaml
mcp_servers:
  gowtham012-pinpoint:
    command: "npx"
    args: ["-y", "pinpoint-bridge"]
```

### Netclaw

```json
{
  "McpServers": {
    "gowtham012-pinpoint": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pinpoint-bridge"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add gowtham012-pinpoint -t stdio -c npx -a -y pinpoint-bridge
```

### Other

```json
{
  "mcpServers": {
    "gowtham012-pinpoint": {
      "command": "npx",
      "args": [
        "-y",
        "pinpoint-bridge"
      ]
    }
  }
}
```

## 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-24 (score 78, −5)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-23 (score 83, +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.

### 2026-10-22 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-21 (score 67, 0)

- [security improvement] Malware scan: unverified → pass
- [functional] Package version: 0.7.1 → 0.7.2

### 2026-10-20 (score 67, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.7.0 → 0.7.1

### 2026-10-19 (score 81, +11)

- [security regression] Stability: 0.50 → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] Provenance: fail → pass
- [security] The attested source repository moved: gowtham012/PinPoint
- [functional regression] Capabilities: pass → unverified
- [functional regression] Schema quality: 0 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Package version: 0.6.0 → 0.7.0

### 2026-10-18 (score 70, 0)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.47 → unverified
- [functional regression] Tool coverage: 75% → 70%
- [functional regression] Schema quality: 788 → 919
- [functional regression] Capabilities: pass → unverified
- [functional regression] Schema quality: 0 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Security disclosure: pass → unverified
- [functional] Package version: 0.5.0 → 0.6.0

### 2026-10-17 (score 70, +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.

## MCP tools (8)

### `get_pending_annotations` (~46 tokens)

Get pending annotations

Return every pending annotation (comment + element details + screenshot) as a markdown task list. Use this first.

Input parameters:

- `url` (string): Only annotations whose page URL starts with this

### `list_annotations` (~26 tokens)

List annotations

One-line summary per annotation. Defaults to pending only.

Input parameters:

- `status` (string)

### `get_annotation` (~38 tokens)

Get one annotation

Full details and screenshot for a single annotation by id or number.

Input parameters:

- `id` (string, required): Annotation id (8 chars) or its pin number

### `recheck_annotation` (~117 tokens)

Re-check an annotation against the live page

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.

Input parameters:

- `id` (string, required): Annotation id (8 chars) or its pin number
- `timeoutSeconds` (number): How long to wait for the browser. Default 10

### `resolve_annotation` (~153 tokens)

Resolve annotation

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.

Input parameters:

- `id` (string, required)
- `note` (string, required): Your reply to the developer, shown in their browser: what changed and where, or why it could not be done

### `reply_annotation` (~131 tokens)

Ask the developer about a note

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.

Input parameters:

- `id` (string, required)
- `message` (string, required): Your question or message, shown to the developer on the pin

### `wait_for_annotation` (~77 tokens)

Wait for the next annotation

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.

Input parameters:

- `timeoutSeconds` (number): Default 120

### `clear_annotations` (~16 tokens)

Clear annotations

Delete all annotations (pending and resolved).

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/gowtham012-pinpoint/pinpoint-bridge#diagnostics

## Score history

- 2026-10-24: 78
- 2026-10-23: 83
- 2026-10-22: 82
- 2026-10-21: 67
- 2026-10-20: 67
- 2026-10-19: 81
- 2026-10-18: 70
- 2026-10-17: 70
- 2026-10-16: 69
- 2026-10-15: 69
- 2026-10-14: 69
- 2026-10-13: 63
- 2026-10-12: 63
- 2026-10-11: 63
- 2026-10-05: 63
- 2026-10-04: 63
- 2026-10-03: 48

## Common questions

### 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.

## Links

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