Skip to content

Pixever MCP server

app.pixever/mcppixever.appstreamable-httpv1.0.0Scanned

Collective, moderated event photo spaces: read status, list media, save a guest photo, react, star.

7 tools: 6 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 6 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Pixever MCP server can do

The Pixever MCP server is published by pixever.app, a domain the MCP Registry verified. It has 7 tools. It can create or change data (6 tools: pixever_info, pixever_upload_link, pixever_upload_media, pixever_react and 2 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 6Claude Code: ask
  • pixever_infoIdentidad y estado público de un Pixever: nombre (si está disclosed), privacidad, estado de ciclo de vida, y la vida free — `state` ('open'|'closed'), `open_until` (hasta cuándo si…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Identidad y estado público de un Pixever: nombre (si está disclosed), privacidad, estado de ciclo de vida, y la vida free — `state` ('open'|'closed'), `open_until` (hasta cuándo sigue abierto a contenido nuevo) y `risk_counter_active` (true solo en los 7 días previos a un corte de extensión, fin de mes 3/4/5). Si está cerrado, lo dice junto con desde cuándo (`closed_since`) — sin ofrecer subida. Solo lectura.
  • pixever_interactionsAgregado de interacciones de un media: `star` (count, recent_actors, starred_by_me), `reactions` (chips con conteos, recent_actors) y `views` (count).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Agregado de interacciones de un media: `star` (count, recent_actors, starred_by_me), `reactions` (chips con conteos, recent_actors) y `views` (count). `token` es opcional en espacios públicos; en closed/semi_private se requiere identidad (x-guest-token) o un x-view-secret válido ya resuelto por el host. Solo lectura, devuelve el agregado tal cual.
  • pixever_reactReacciona a un media con un emoji del catálogo, o quita la reacción propia (`remove:true`).No findings

    Why it is in this group

    • The name "pixever_react" says "react": a word for a change.
    Description, as the server wrote itContains invisible characters, shown as [U+…]
    Reacciona a un media con un emoji del catálogo, o quita la reacción propia (`remove:true`). Requiere `token` (x-guest-token) — sin identidad de invitado no hay reacción. `emoji` es requerido salvo con `remove:true` (uno de ❤[U+FE0F] 😂 😮 😢 🔥 👏). Con `remove:true` se ignora `emoji` y se usa DELETE. Errores reales de la API (429 `REACTION_RATE_LIMITED`, etc.) se devuelven como `ok:false` con su `code`, nunca como éxito inventado.
  • pixever_starPone o quita la estrella de un media — funciona como un 'like': el toggle la pone si no estaba, o la quita si ya estaba.No findings

    Why it is in this group

    • The name "pixever_star" says "star": a word for a change.
    Description, as the server wrote it
    Pone o quita la estrella de un media — funciona como un 'like': el toggle la pone si no estaba, o la quita si ya estaba. Requiere `token` (x-guest-token) — sin identidad de invitado no hay estrella. Devuelve `starred` (estado después del toggle) y `count` (total de estrellas del media). Errores reales de la API se devuelven como `ok:false` con su `code` cuando la API lo tipa, nunca como éxito inventado.
  • pixever_upload_mediaÚNICA tool de escritura: descarga una imagen pública desde `source_url` y la sube a `POST /api/v1/pixevers/:slug/media` a nombre del invitado dueño de `token` (x-guest-token, reque…No findings

    Why it is in this group

    • The name "pixever_upload_media" says "upload": a word for a change.
    Description, as the server wrote it
    ÚNICA tool de escritura: descarga una imagen pública desde `source_url` y la sube a `POST /api/v1/pixevers/:slug/media` a nombre del invitado dueño de `token` (x-guest-token, requerido — sin token no hay escritura). Solo imágenes (jpeg/png/webp/heic/heif, máx 20 MB); no video, no creación de Pixevers, no moderación. `source_url` debe ser https pública y no resolver a una red interna — se rechaza si no cumple, sin tocar la red. Si el espacio ya cerró su vida free, rechaza con `ok:false` y `code: FREE_LIFE_CLOSED` (mensaje en positivo: sigue visible para siempre, ya no entra contenido nuevo, Obtén Pro) — nunca por un reloj de 48h (retirado, ya no existe).
Only reads 1Show 1 read-only tool
  • pixever_media_listLista paginada (cursor-based) de media visible del feed de un Pixever.No findings

    Why it is in this group

    • The name "pixever_media_list" says "list": a word for reading.
    Description, as the server wrote it
    Lista paginada (cursor-based) de media visible del feed de un Pixever. Pixevers públicos no requieren `token`; cerrados/semi-privados sí (el x-guest-token de un invitado ya registrado). Usa `pageInfo.endCursor` de la respuesta como `after` para pedir la siguiente página. Solo lectura.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:30 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://pixever.app/mcp: tools/list returned 7 tools to an anonymous client, including pixever_info (write), pixever_upload_link (write), pixever_upload_media (write), pixever_react (write), pixever_star (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http pixever https://pixever.app/mcp
claude mcp add --transport http pixever https://pixever.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pixever__pixever_media_list"
    ],
    "ask": [
      "mcp__pixever__pixever_info",
      "mcp__pixever__pixever_upload_link",
      "mcp__pixever__pixever_upload_media",
      "mcp__pixever__pixever_react",
      "mcp__pixever__pixever_star",
      "mcp__pixever__pixever_interactions"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pixever. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.pixever/mcp/verify?hash=e348d4a42bc9a3979ac4953996a7f22e60fa0308e39c168577c67e1de22c257b" | jq -e '.changed == false'

Pinned hash e348d4a42bc9, from Nov 12, 2026, 03:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.pixever/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.pixever/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/app.pixever/mcp.svg)](https://radar.anlyon.com/servers/app.pixever/mcp)

Source: MCP Registry. Synced Oct 21, 2026, 17:44 UTC.

Pixever MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Pixever MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Pixever MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Pixever MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Pixever MCP server have?

7 tools: 6 write, 1 read. pixever_info, pixever_upload_link, pixever_upload_media, pixever_react, pixever_star, pixever_interactions and pixever_media_list.

Does the Pixever MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Pixever MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Pixever MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.