# PinAppAI (remote · mcp.pinappai.com)

Visual website feedback your coding agent applies: pin change requests on the live site over MCP.

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

## Components

- remote · `mcp.pinappai.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-pinappai-mcp/mcp.md), [page](https://verifymcp.io/servers/com-pinappai-mcp/mcp)
- npm · `@pinappai/mcp`: 12/100, [markdown](https://verifymcp.io/servers/com-pinappai-mcp/pinappai-mcp.md), [page](https://verifymcp.io/servers/com-pinappai-mcp/pinappai-mcp)

## Channel facts

- Endpoint: `https://mcp.pinappai.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.9.9`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-08-03.

- **Endpoint Security**: 81/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4113 tokens (~108/item across 38 items; 38 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-pinappai-mcp https://mcp.pinappai.com/mcp
```

### Codex

```toml
[mcp_servers.com-pinappai-mcp]
url = "https://mcp.pinappai.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-pinappai-mcp": {
      "type": "remote",
      "url": "https://mcp.pinappai.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-pinappai-mcp --url https://mcp.pinappai.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-pinappai-mcp:
    url: "https://mcp.pinappai.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-pinappai-mcp": {
      "type": "http",
      "url": "https://mcp.pinappai.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-08-02 (score 78, +1)

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

### 2026-07-31 (score 77, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 74, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 73, +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-07-27 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 71)

First indexed and scored.

## MCP tools (38)

### `list_projects` (~57 tokens)

List PinAppAI projects this API key can access. Returns one entry per project in the key's workspace, with slug, name, derived domain, and created_at. Call this first to see what projects are available before drilling into specific ones.

### `get_review_summary` (~62 tokens)

Cheap one-call summary of change-request state for a project. Returns totals + by-page + by-reviewer breakdowns + oldest/newest unresolved timestamps. Call this BEFORE drilling into individual CRs to frame the work.

Input parameters:

- `project` (string, required): The project slug.

### `list_change_requests` (~254 tokens)

List change requests for a project with filters + cursor pagination. Defaults to include=['change_requested'] (highest-signal subset). Returns digest fields per row (including element_kind=text|mixed|field|null and suggested_text — a literal text replacement on text/field picks); no inline images at this tier (token-cheap by design). Use get_change_request for full detail + screenshots.

Input parameters:

- `cursor` (string): Opaque pagination cursor from a previous response's next_cursor. Pass it to fetch the next page.
- `include` (array): Which feedback kinds to include: change_requested (a decision requesting a change), rejected (a decision rejecting the pick), approved (a decision approving the pick), comment (a comment-only pin, no…
- `limit` (integer): Max rows to return per page. Defaults to 50, maximum 200.
- `page_url` (string): Filter to change requests captured on this exact page URL.
- `project` (string, required): The project slug.
- `reviewer` (string): Filter by reviewer name or email (matches either field).
- `since` (string): ISO 8601 timestamp. Only return change requests created after this time.

### `get_change_request` (~272 tokens)

Full detail for one change request. Returns the CR (including element_kind=text|mixed|field|null and suggested_text — a literal text-replacement the reviewer typed when picking a text/field element), plus related[] (other CRs on the same selector + same page) so you can detect patterns from a single fetch. Set include_image=true to embed the screenshot inline as an MCP image content block. When suggested_text is non-null on a text/field pick, paste it verbatim — do not interpret or rewrite. When element_kind=mixed, the element contains more than text (icons/images/structure) — rely on the comment + screenshot, not just the visible text.

Input parameters:

- `id` (string, required): The FEEDBACK id (fb_*), NOT a change-request id (cr_*). When you have a CR row from pinappai_list_apply_inbox / list_change_requests, pass its `source_feedback_id` (or just `id` in list_change_reques…
- `include_image` (boolean): When true, also returns the change request's screenshot inline as an MCP image content block, in addition to the JSON text response. Defaults to false (JSON only).
- `project` (string, required): The project slug.

### `analyze_patterns` (~329 tokens)

Server-side deterministic groupings (by selector / page / reviewer / keyword) plus heuristic suggested_clusters of change requests. Set ai_clusters="auto" (default) to also request semantic clustering via the host's MCP sampling capability — returns ai_clustering_hint for the host AI to apply inline if sampling is unsupported. Use this BEFORE drilling into individual CRs to find patterns across the dataset.

Input parameters:

- `ai_clusters` (string): Controls semantic clustering via the host's MCP sampling capability. off skips it and returns only the deterministic groupings. auto (default) attempts it and falls back to an ai_clustering_hint for…
- `ai_model_preference` (string): Optional model preference hint for the sampling request. Currently accepted but not forwarded to the host's createMessage call (the sampling request always uses a fixed speed/intelligence preference)…
- `group_by` (array): Which deterministic groupings to compute: selector (by CSS selector), page (by page URL), reviewer (by reviewer). Defaults to ['selector', 'page']. Keyword extraction (common_keywords) is always comp…
- `include` (array): Which feedback kinds to pull into the analysis: change_requested (a decision requesting a change), rejected (a decision rejecting the pick), approved (a decision approving the pick), comment (a comme…
- `project` (string, required): The project slug.

### `get_screenshot` (~106 tokens)

Return the screenshot for a change request as an inline MCP image content block. Use when you want vision context without the full JSON envelope from get_change_request.

Input parameters:

- `id` (string, required): The FEEDBACK id (fb_*), NOT a change-request id (cr_*). When you have a CR row from pinappai_list_apply_inbox, pass its `source_feedback_id` here. Passing a cr_* value returns 404.
- `project` (string, required): The project slug.

### `get_project` (~51 tokens)

Get a single project by slug — name, allowed_origins, archive state, and the embeddable widget api_key. Scoped to the API key's workspace.

Input parameters:

- `project` (string, required): The project slug.

### `create_project` (~110 tokens)

Create a new PinAppAI project inside the API key's workspace. Returns the project plus its widget api_key for embedding. Requires editor role on the workspace.

Input parameters:

- `allowed_origins` (array): Origins where the widget will load (e.g. https://example.com or *.example.com). Up to 20 entries.
- `name` (string, required): Human-readable project name.
- `slug` (string, required): Project slug (lowercase, hyphens). Must be unique across all PinAppAI projects.

### `update_project` (~312 tokens)

Update editable fields on a project — slug, name, owner_email, allowed_origins, allow_anonymous_reviewers, primary_origin (review link), preview_origin (preview review link). Requires editor role.

Input parameters:

- `allow_anonymous_reviewers` (boolean): When true, any verified email on a CORS-allowed origin can submit feedback. When false, the email must be on the workspace or project_reviewers list.
- `allowed_origins` (array): REPLACES the existing list. Pass an empty array [] to clear all allowed origins.
- `name` (string): New display name for the project.
- `owner_email` (string): Reassign project ownership to a different email (for display only — does not change permissions).
- `preview_origin`: Optional branch/preview deploy origin. review.pinappai.com/p/<slug>~preview/ serves it so reviewers can check APPLIED changes before they ship — records still write against primary_origin. Set this a…
- `primary_origin`: Canonical site origin powering the no-install review link (review.pinappai.com/p/<slug>/). Any URL is normalized down to its origin. null (or an empty string) clears it and disables the link.
- `project` (string, required): Current project slug (the lookup key).
- `slug` (string): New slug (renames the project; widget snippets keep working since they reference api_key, not slug).

### `archive_project` (~51 tokens)

Soft-archive a project — the widget stops accepting new feedback but the project + history is preserved. Reversible via unarchive_project. Owner role required.

Input parameters:

- `project` (string, required): The project slug to archive.

### `unarchive_project` (~45 tokens)

Restore an archived project — the widget starts accepting feedback again on pages that still embed the snippet. Owner role required.

Input parameters:

- `project` (string, required): The project slug to unarchive.

### `list_workspaces` (~55 tokens)

List all workspaces the API key's user is a member of, with role per workspace. The api-key remains bound to its original workspace — to operate on another, mint a new key for that workspace in the admin UI.

### `create_workspace` (~85 tokens)

Create a new workspace owned by the API key's user. Free/Pro plans cap at 1 workspace; Team/Business unlimited. To use the new workspace from MCP, mint a fresh key for it in the admin UI.

Input parameters:

- `name` (string, required): Human-readable workspace name.
- `slug` (string, required): Workspace slug (lowercase, hyphens). Globally unique.

### `get_workspace` (~38 tokens)

Get the API key's workspace details (slug, name, plan, tier) plus the user's role in that workspace. Useful as a permissions probe.

### `update_workspace` (~66 tokens)

Rename or re-slug the API key's workspace. Owner role required. Slug changes break existing dashboard URLs.

Input parameters:

- `name` (string): New display name for the workspace.
- `slug` (string): Renaming slug breaks every URL pointing at the old slug — use sparingly.

### `delete_workspace` (~50 tokens)

Schedule the API key's workspace for permanent deletion (7-day grace window). Reversible only via the email magic-link sent to the owner. Subsequent MCP calls with this key will fail not_found until cancelled.

### `list_members` (~45 tokens)

List members of the API key's workspace with their roles, sorted owner → admin → editor → viewer. The user_id field is the lookup key for update_member_role and remove_member.

### `invite_member` (~90 tokens)

Invite a user to the API key's workspace as admin / editor / viewer (default editor). Admin role required to call. Sends a welcome email.

Input parameters:

- `email` (string, required): Invitee's email address.
- `name` (string): Optional display name; defaults to the email's local-part.
- `role` (string): Defaults to editor. Admins can't invite owners — that requires an existing owner.

### `update_member_role` (~73 tokens)

Change a workspace member's role. Caller must outrank both the current role and the new role; promoting to owner requires owner role. Last-owner demotion is rejected with last_owner.

Input parameters:

- `role` (string, required): The new role.
- `user_id` (string, required): The member's user_id (from list_members).

### `remove_member` (~62 tokens)

Remove a member from the API key's workspace. Self-removal works for any role; cross-removal requires admin+ and outranking the target. Last-owner removal returns last_owner.

Input parameters:

- `user_id` (string, required): The member's user_id (from list_members).

### `list_reviewers` (~51 tokens)

List external reviewers on a project (people invited via invite_reviewer). Workspace members are implicitly authorized and not listed here. Status: pending / verified / revoked.

Input parameters:

- `project` (string, required): The project slug.

### `invite_reviewer` (~80 tokens)

Invite an external reviewer to a project. They'll get a welcome email; status starts pending and flips to verified when they OTP through the widget. Editor role required.

Input parameters:

- `email` (string, required): Reviewer's email address.
- `name` (string): Optional display name; defaults to the email's local-part.
- `project` (string, required): The project slug.

### `revoke_reviewer` (~76 tokens)

Revoke an external reviewer's access. First call soft-revokes (status=revoked, audit trail preserved); second call hard-deletes (status=removed). Editor role required.

Input parameters:

- `project` (string, required): The project slug.
- `reviewer_id` (string, required): The project_reviewers row id (from list_reviewers).

### `list_audit_events` (~141 tokens)

Read audit log entries for the API key's workspace. Owner role + Business tier required. Returns newest-first; supports filters action / actor (email substring) / from / to (Unix ms).

Input parameters:

- `action` (string): Exact dotted action name (e.g. "feedback.update", "member.invite").
- `actor` (string): Substring match on actor_email.
- `from` (integer): Start of time range (Unix ms, inclusive).
- `limit` (integer): Default 100, max 500.
- `offset` (integer): Default 0.
- `to` (integer): End of time range (Unix ms, exclusive).

### `list_api_keys` (~40 tokens)

List API keys (active + recently-revoked) in the calling key's workspace. Plaintext / hash never returned. Owner or admin role required.

### `get_api_key` (~57 tokens)

Get a single API key's metadata by id (no plaintext / hash). Owner or admin role required. Wrong-role and nonexistent-id both surface as not_found.

Input parameters:

- `id` (string, required): The api_keys.id (from list_api_keys).

### `revoke_api_key` (~59 tokens)

Soft-revoke an API key (reversible via restore_api_key for 7 days). Owner or admin role required. Refuses to revoke the calling key with cannot_revoke_self.

Input parameters:

- `id` (string, required): The api_keys.id to revoke.

### `restore_api_key` (~65 tokens)

Restore a soft-revoked API key (within 7 days of revocation). Owner or admin role required. Returns restore_window_expired if the row was never revoked or was revoked > 7 days ago.

Input parameters:

- `id` (string, required): The api_keys.id to restore.

### `get_me` (~47 tokens)

Whoami probe — returns the user behind the API key, the workspace it's bound to, the user's role in that workspace, and the API key's metadata. Run this first to establish context.

### `update_me_profile` (~35 tokens)

Update the API key user's display name. Email is identity and not editable.

Input parameters:

- `name` (string, required): The new display name.

### `export_my_data` (~56 tokens)

GDPR Art. 15 right-of-access export — every row PinAppAI holds about the API key's user. Sensitive columns (password hash, OAuth tokens) are server-side redacted. Personal data of OTHER reviewers is NOT included.

### `pinappai_get_iteration_coverage` (~94 tokens)

Read coverage metrics for an iteration: items_decided / manifest_size + items_undecided + per-reviewer decided_count + disagreement_count. Useful for the AI to summarize "you have N items still waiting on M reviewers" and identify CRs needing admin attention. Read-only.

Input parameters:

- `iteration_id` (string, required): The iteration id (it_*).
- `project` (string, required): The project slug.

### `pinappai_list_iterations` (~120 tokens)

Paginated history of iterations for a project, newest first. Each entry includes seq_no, opened_at, applied_at (NULL while open), bundle_summary, and the frozen manifest_cr_ids_json + manifest_reviewer_ids_json. Pair with pinappai_get_iteration_coverage to summarize outcomes per iteration.

Input parameters:

- `before_seq` (integer): Pagination cursor — return iterations with seq_no strictly less than this.
- `limit` (integer): Max iterations to return (default 50, max 200).
- `project` (string, required): The project slug.

### `pinappai_list_apply_inbox` (~131 tokens)

v3 Apply-inbox listing. Returns every change request in an Apply-eligible inbox substate (inbox_new / inbox_rejected / inbox_change_requested) with the prior cr_marked_applied event payload AND the latest reviewer/admin decision payload inlined per row. Used by /pinappai:apply to drive substate-specific edits (new = standard apply; rejected = revert via swap; change_requested = apply with new wording) in one round-trip.

Input parameters:

- `limit` (integer): Max rows to return (default 100).
- `project` (string, required): The project slug.

### `pinappai_apply_change_requests` (~174 tokens)

v3 atomic apply primitive. Takes a list of {cr_id, before_text, after_text} after the AI has edited source for each. Creates one iteration record (audit trail visible in the Project history page) and transitions every eligible CR from inbox_* state to 'in_review' atomically. Per-CR errors (CR not in eligible state, e.g. someone deferred it mid-session) are returned in the response without failing the whole batch. Editor role required.

Input parameters:

- `applies` (array, required): List of CRs to mark applied in one atomic batch.
- `bundle_summary` (string): Short human-readable summary of this Apply batch — shows up in the project history page. e.g. "applied 7 CRs across 3 pages".
- `project` (string, required): The project slug.

### `pinappai_reset_review_data` (~159 tokens)

Permanently deletes a project's review data: all change requests (+ their event history), iterations, reviewer decisions, ALL freeform pins/comments with their screenshots, and the /changes/-page registration tables. NOT recoverable — no grace window. Requires admin role. Ask the user for explicit confirmation before calling, and prefer the /pinappai:reset-project prompt, which also offers to clean up the repo's static /changes/ page and .pinappai/last-applied.json.

Input parameters:

- `confirm` (boolean, required): Must be literally true. The caller must have shown the user what will be deleted and received explicit confirmation first — there is no grace window; this is not recoverable.
- `project` (string, required): The project slug.

### `pinappai_register_change_items` (~170 tokens)

Register the items of a freshly written /changes/ review page with the server — REQUIRED after generating or regenerating the page, or the in-page review chip and decision bars have no data. Pass every [data-pp-item] in document order with the same attribute values you put in the markup. This replaces the removed client-side self-registration: the page itself can no longer register anything. Editor role required.

Input parameters:

- `items` (array, required): Every [data-pp-item] on the page you just wrote, in DOCUMENT ORDER (order drives the review queue). The FULL active set — items you omit are deactivated server-side.
- `page_path` (string): Path of the /changes/ page on the site. Default '/changes'.
- `project` (string, required): The project slug.

### `pinappai_get_workflow` (~305 tokens)

Return the full procedure for a PinAppAI guided workflow, rendered exactly as the
/pinappai:<name> prompt delivers it. Call this when the user asks for one of these
and this client does not surface MCP prompts. Follow the returned text verbatim and
do not improvise a workflow from its name or description.

Available workflows:
  analyze                Read-only pattern analysis of change requests
  apply                  v3 PinAppAI Apply — drain the project Inbox by editing source for every Apply-eligible change…
  audit-review           Pull recent audit-log events for the workspace and summarize unusual activity
  auth-help              Walk through PinAppAI MCP authentication — recommend the browser-flow login first, fall back…
  embed-widget           Embed the PinAppAI widget snippet into an EXISTING project's site, then bootstrap the…
  generate-changes-page  Generate a temporary /changes/ review page for a multi-page rewrite
  remove                 Remove ALL PinAppAI integration from this repository (widget script, /changes/ pages, optional…
  reset-project          Reset a project's review data to zero — permanently delete its change requests, iterations,…
  setup-project          Walk the user through creating a new PinAppAI project from scratch — pick or create a…
  summarize              Generate a PR description / changelog / customer email from completed work, referencing the…

Input parameters:

- `name` (string, required): The workflow to fetch. See the description for what each does.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-pinappai-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 78
- 2026-08-02: 78
- 2026-08-01: 77
- 2026-07-31: 77
- 2026-07-30: 74
- 2026-07-29: 73
- 2026-07-28: 73
- 2026-07-27: 72
- 2026-07-26: 71

## Links

- Remote endpoint: https://mcp.pinappai.com/mcp
- Website: https://pinappai.com/docs/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-pinappai-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pinappai-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-pinappai-mcp/mcp