Pixever
REMOTE · PIXEVER.APP
Collective, moderated event photo spaces: read status, list media, save a guest photo, react, star.
Available components
Last scanned (13 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Documents and Files
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1257 tokens (~179/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.27 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 14 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 62
First indexed and scored.
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 18 Oct 2026 · Probed https://pixever.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pixever.app | CN=YE1,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 598c3a61e429898b19fb96c7ae7316efa76 |
| SANs: *.pixever.app, pixever.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pixever.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| pixever.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pixever.app/mcp | Verified | 200 | |
| http (plaintext) | http://pixever.app/mcp | HTTPS enforced | 302 | https://pixever.app/mcp |
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 →
pixever_info ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Slug del Pixever, p.ej. 'boda-maria'. |
No output schema declared.
No examples provided.
pixever_interactions ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| media_id | string | yes | – |
| slug | string | yes | – |
| token | string | – | Token de invitado (x-guest-token) opcional — nunca se guarda ni se loguea. |
No output schema declared.
No examples provided.
pixever_media_list ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Cursor opaco de `pageInfo.endCursor` de una llamada previa. |
| limit | integer | – | Default 20, máximo 50. |
| slug | string | yes | – |
| token | string | – | Token de invitado (x-guest-token) ya emitido — nunca se guarda ni se loguea. |
No output schema declared.
No examples provided.
pixever_react ~237
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 ❤️ 😂 😮 😢 🔥 👏). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| emoji | string | – | Requerido si remove no es true. Uno de: ❤️ 😂 😮 😢 🔥 👏 |
| media_id | string | yes | – |
| remove | boolean | – | true quita la reacción propia (DELETE) en vez de crearla/actualizarla; ignora emoji. |
| slug | string | yes | – |
| token | string | yes | Token de invitado (x-guest-token) ya emitido — requerido. Nunca se guarda ni se loguea. |
No output schema declared.
No examples provided.
pixever_star ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| media_id | string | yes | – |
| slug | string | yes | – |
| token | string | yes | Token de invitado (x-guest-token) ya emitido — requerido. Nunca se guarda ni se loguea. |
No output schema declared.
No examples provided.
pixever_upload_link ~169
Construye la URL pública de la puerta de subida (/p/:slug) de un Pixever, agregando el acceso del invitado como ?access= si se provee `token`. Si el espacio está cerrado (vida free agotada), no ofrece el enlace: devuelve `ok:false` con `code: FREE_LIFE_CLOSED` y un mensaje en positivo (sigue visible para siempre, ya no entra contenido nuevo, Obtén Pro). No emite ni valida el token — solo lo adjunta cuando el espacio está abierto; la validación ocurre al abrir el enlace. Solo lectura.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
| token | string | – | Acceso (puerta×alcance) ya emitido por el host — nunca se guarda ni se loguea. |
No output schema declared.
No examples provided.
pixever_upload_media ~253
Ú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).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
| source_url | string | yes | URL https pública de la imagen a guardar. Nunca se loguea. |
| token | string | yes | Token de invitado (x-guest-token) ya emitido — requerido. Nunca se guarda ni se loguea. |
No output schema declared.
No examples provided.
How do I install the Pixever MCP server?
Pixever is a hosted endpoint at https://pixever.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pixever.app
claude mcp add --transport http app-pixever-mcp 'https://pixever.app/mcp'
What is the Pixever MCP server?
Pixever is an MCP server listed in the public MCP registry as app.pixever/mcp. Collective, moderated event photo spaces: read status, list media, save a guest photo, react, star. This page covers its hosted endpoint (https://pixever.app/mcp).
Is the Pixever MCP server safe to use?
Pixever scores 65 out of 100 on VerifyMCP. 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 Pixever MCP server expose?
Pixever exposes 7 tools: pixever_info, pixever_media_list, pixever_upload_link, pixever_upload_media, pixever_react, and 2 more. Their descriptions and schemas cost roughly 1,257 tokens of context every time the server is loaded.
Does the Pixever MCP server require authentication?
No. We connected to Pixever without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pixever MCP server still maintained?
Pixever is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.