_ registry / mcp streamable-http · checked 29m ago

pixever-mcp

https://pixever.app

Registry code: 6fe388902a7fc559

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://pixever.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pixever-mcp live?
Yes — it answered the hub's last check (checked 29m ago). It answered 100% of checks over the last 30 days.
Is pixever-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does pixever-mcp have?
7 tools: pixever_upload_media, pixever_info, pixever_upload_link, pixever_react, pixever_star, pixever_interactions, pixever_media_list.
Is pixever-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
586ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • pixever_upload_media unknown never probed

    Ú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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug",
        "token",
        "source_url"
      ],
      "properties": {
        "slug": {
          "type": "string"
        },
        "token": {
          "type": "string",
          "description": "Token de invitado (x-guest-token) ya emitido — requerido. Nunca se guarda ni se loguea."
        },
        "source_url": {
          "type": "string",
          "description": "URL https pública de la imagen a guardar. Nunca se loguea."
        }
      }
    }
    arguments 21 lines
  • pixever_info unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Slug del Pixever, p.ej. 'boda-maria'."
        }
      }
    }
    arguments 12 lines
  • pixever_upload_link unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string"
        },
        "token": {
          "type": "string",
          "description": "Acceso (puerta×alcance) ya emitido por el host — nunca se guarda ni se loguea."
        }
      }
    }
    arguments 15 lines
  • pixever_react unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug",
        "token",
        "media_id"
      ],
      "properties": {
        "slug": {
          "type": "string"
        },
        "emoji": {
          "type": "string",
          "description": "Requerido si remove no es true. Uno de: ❤️ 😂 😮 😢 🔥 👏"
        },
        "token": {
          "type": "string",
          "description": "Token de invitado (x-guest-token) ya emitido — requerido. Nunca se guarda ni se loguea."
        },
        "remove": {
          "type": "boolean",
          "description": "true quita la reacción propia (DELETE) en vez de crearla/actualizarla; ignora emoji."
        },
        "media_id": {
          "type": "string"
        }
      }
    }
    arguments 28 lines
  • pixever_star unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug",
        "token",
        "media_id"
      ],
      "properties": {
        "slug": {
          "type": "string"
        },
        "token": {
          "type": "string",
          "description": "Token de invitado (x-guest-token) ya emitido — requerido. Nunca se guarda ni se loguea."
        },
        "media_id": {
          "type": "string"
        }
      }
    }
    arguments 20 lines
  • pixever_interactions unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug",
        "media_id"
      ],
      "properties": {
        "slug": {
          "type": "string"
        },
        "token": {
          "type": "string",
          "description": "Token de invitado (x-guest-token) opcional — nunca se guarda ni se loguea."
        },
        "media_id": {
          "type": "string"
        }
      }
    }
    arguments 19 lines
  • pixever_media_list unknown 28m ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string"
        },
        "after": {
          "type": "string",
          "description": "Cursor opaco de `pageInfo.endCursor` de una llamada previa."
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Default 20, máximo 50."
        },
        "token": {
          "type": "string",
          "description": "Token de invitado (x-guest-token) ya emitido — nunca se guarda ni se loguea."
        }
      }
    }
    arguments 25 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6fe388902a7fc559.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6fe388902a7fc559/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6fe388902a7fc559/badge.svg)](https://brick.blue/agent/6fe388902a7fc559?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.