MCP servers observed by Lowdown
io.github.pixelvault-dev/pixelvault MCP server: daily status and tool changes
On the latest check (2026-11-16) its remotes differed: 1 answered tools/list, 1 required authentication. (Lowdown checks this server every 3 days) MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.pixelvault-dev/pixelvault
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.pixelvault-dev/pixelvault?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server its remotes gave different results.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 0
- Required authentication: 0
- No response: 0
- Remotes differed: 3
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-16: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 19 → 22
- 2026-11-13: descriptions changed
What tools does it list?
22 tools on 2026-11-16:
close_collectioncreate_upload_urldelete_imagedescribe_imageedit_imagegenerate_imageget_collectionget_imageget_usagelist_collectionslist_image_tagslist_imagesmanage_billingoptimize_videorescue_imgursign_urltransform_imageupdate_image_metadataupgrade_planupload_batchupload_imageupload_video
MCP Registry declaration
- Registry name:
io.github.pixelvault-dev/pixelvault - Declared version: 0.10.0
- Status: active
- Declared hosts:
mcp.pixelvault.dev
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.pixelvault-dev/pixelvault", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.pixelvault-dev/pixelvault?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).