# @reticlehq/server

Reticle CLI, bridge and MCP server: a coding agent drives your running web app from the inside and gets a verdict with evidence, for change verification, access control, accessibility, performance and SEO checks.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 3.7.0
- **Author:** Reticle contributors
- **License:** FSL-1.1-ALv2
- **npm:** @reticlehq/server
- **Source:** https://github.com/reticlehq/reticle
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 2 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-15T07:22:20.456Z
- **Version scanned:** 3.7.0
- **CVEs:** none found by OSV at scan time

## Tools

1 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `finish` — Call this when you have finished driving the app, or when you cannot make further progress. Summarise what you drove and what you observed. This does not decide

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"server\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@reticlehq/server\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40reticlehq%2Fserver
- Install plan: https://forgeregistry.com/api/v1/packages/%40reticlehq%2Fserver/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40reticlehq%2Fserver
- HTML page: https://forgeregistry.com/registry/%40reticlehq%2Fserver
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.