# io.github.PetShopBros/lowdown-proxy (remote · lowdown-proxy.vercel.app)

Dated facts on MCP servers: daily checks, Registry and card declarations, packages, payment terms.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `lowdown-proxy.vercel.app`: 81/100 (this document), [markdown](https://verifymcp.io/servers/petshopbros-lowdown-proxy/lowdown-proxy-2.md), [page](https://verifymcp.io/servers/petshopbros-lowdown-proxy/lowdown-proxy-2)
- npm · `lowdown-proxy`: 82/100, [markdown](https://verifymcp.io/servers/petshopbros-lowdown-proxy/lowdown-proxy.md), [page](https://verifymcp.io/servers/petshopbros-lowdown-proxy/lowdown-proxy)

## Channel facts

- Endpoint: `https://lowdown-proxy.vercel.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.23`

## 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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1074 tokens (~537/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.PetShopBros/lowdown-proxy MCP server?

io.github.PetShopBros/lowdown-proxy is a hosted endpoint at https://lowdown-proxy.vercel.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.

### Claude

```bash
claude mcp add --transport http petshopbros-lowdown-proxy 'https://lowdown-proxy.vercel.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "petshopbros-lowdown-proxy": {
      "url": "https://lowdown-proxy.vercel.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "petshopbros-lowdown-proxy": {
      "type": "http",
      "url": "https://lowdown-proxy.vercel.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.petshopbros-lowdown-proxy]
url = "https://lowdown-proxy.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "petshopbros-lowdown-proxy": {
      "type": "remote",
      "url": "https://lowdown-proxy.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add petshopbros-lowdown-proxy --url 'https://lowdown-proxy.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  petshopbros-lowdown-proxy:
    url: "https://lowdown-proxy.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "petshopbros-lowdown-proxy": {
      "Transport": "http",
      "Url": "https://lowdown-proxy.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add petshopbros-lowdown-proxy -t streamable-http -u 'https://lowdown-proxy.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "petshopbros-lowdown-proxy": {
      "type": "http",
      "url": "https://lowdown-proxy.vercel.app/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-11-20 (score 81, +1)

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

### 2026-11-19 (score 80, 0)

- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28

### 2026-11-18 (score 80, +1)

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

### 2026-11-16 (score 79, +1)

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

### 2026-11-14 (score 78, +1)

- [security] Tool “get_lowdown” rewrote its description, which is the text the model reads
- [security] Tool “find_servers” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.0 → 0.1.23

### 2026-11-12 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_lowdown” rewrote its description, which is the text the model reads
- [cosmetic] “get_lowdown” reworded the description of “menu”

### 2026-11-11 (score 77, +1)

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

### 2026-11-09 (score 76, +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.

## MCP tools (2)

### `get_lowdown` (~381 tokens)

Look up recorded facts about an MCP server

Lowdown(로우다운) looks up recorded facts about an MCP server before installing or connecting to it. Accepts an MCP Registry name ('mcp:io.github.user/server'), a short name, or a package ('npm:@scope/name', 'pypi:name'). Returns dated facts, not scores: `status` (latest daily initialize/tools/list check: answered, required authentication, or no response), `registry` (what the official MCP Registry declares, and changes in the last 30 days), `packages` (declared npm/PyPI packages: deprecated, yanked, archived, or 404), `scanner` (tool definition changes and content markers such as a new URL or invisible characters), `payment` (HTTP 402 terms on the latest check: x402, MPP or L402; payment support declared in the server card or ERC-8004 file; Lowdown does not pay), and agent reports. Optional `menu` returns one part, e.g. 'install-check' or 'payment'. Absence of data says nothing about a server. Each answer ends with a `source` block (dataset, CC BY 4.0, retrieval time).

Input parameters:

- `menu` (string): Optional. Before installing, use 'install-check' (status, payment, packages, declared-vs-observed, content-flags). 'change-watch' = what changed recently, or one part: status, payment, packages, tool…
- `target` (string, required): MCP Registry name with the mcp: prefix (e.g. 'mcp:io.github.user/server'), a short name, or a package with the npm: or pypi: prefix

### `find_servers` (~463 tokens)

Find MCP servers by observed facts

Lowdown(로우다운) lists public MCP servers by observed facts, when you do not have a server name yet. Use does to find servers by what they do (words in the Registry name or tool names, e.g. 'postgres'). Filter by the latest daily check (e.g. state 'answered' = answered initialize and tools/list without credentials), days answered in the last 30, how long the tool list has been unchanged, tool count, Registry status and package state; sort by one key. No score or ranking: order is only the chosen sort key. Each result carries a lookup URL; call get_lowdown with its name for the full record. Tool lists are recorded from 2026-10-20, so a long stable_days returns nothing yet.

Input parameters:

- `answered_days` (integer): Minimum daily checks in the last 30 days that answered tools/list
- `does` (string): What the server does: 1-3 words separated by spaces, e.g. 'postgres' or 'github issue'. Every word must appear in the Registry name or in a tool name from the latest observed tool list; results show…
- `limit` (integer): 1-50, default 20
- `offset` (integer): For the next page, use next_offset from the previous answer
- `order` (string): Default depends on sort
- `package` (string): ok = declared packages with no deprecated/yanked/404 latest; flagged = at least one; none = no declared packages
- `q` (string): Part of the Registry name, e.g. 'github' or 'io.github.user'
- `registry` (string): MCP Registry status
- `sort` (string): Sort key (default name). tools = tool count, answering = days answered, stable = tool list unchanged longest, newest, updated, changed, release
- `stable_days` (integer): Current tool list first observed at least this many days ago
- `state` (string): Latest daily check result (only servers checked in the last 2 days). 'answered' = answered tools/list with no credentials
- `tools_max` (integer): Maximum tool count
- `tools_min` (integer): Minimum tool count

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/petshopbros-lowdown-proxy/lowdown-proxy-2#diagnostics

## Score history

- 2026-11-21: 81
- 2026-11-20: 81
- 2026-11-19: 80
- 2026-11-18: 80
- 2026-11-17: 79
- 2026-11-16: 79
- 2026-11-15: 78
- 2026-11-14: 78
- 2026-11-13: 77
- 2026-11-12: 77
- 2026-11-11: 77
- 2026-11-10: 76
- 2026-11-09: 76
- 2026-11-08: 75
- 2026-11-07: 75
- 2026-11-06: 74
- 2026-11-05: 74
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 73
- 2026-10-30: 73

## Common questions

### What is the io.github.PetShopBros/lowdown-proxy MCP server?

io.github.PetShopBros/lowdown-proxy is an MCP server listed in the public MCP registry as io.github.PetShopBros/lowdown-proxy. Dated facts on MCP servers: daily checks, Registry and card declarations, packages, payment terms. This page covers its hosted endpoint (https://lowdown-proxy.vercel.app/mcp).

### Is the io.github.PetShopBros/lowdown-proxy MCP server safe to use?

io.github.PetShopBros/lowdown-proxy scores 81 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 io.github.PetShopBros/lowdown-proxy MCP server expose?

io.github.PetShopBros/lowdown-proxy exposes 2 tools: get_lowdown, find_servers. Their descriptions and schemas cost roughly 844 tokens of context every time the server is loaded.

### Does the io.github.PetShopBros/lowdown-proxy MCP server require authentication?

No. We connected to io.github.PetShopBros/lowdown-proxy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.PetShopBros/lowdown-proxy MCP server still maintained?

io.github.PetShopBros/lowdown-proxy is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the io.github.PetShopBros/lowdown-proxy MCP server?

VerifyMCP ran 13 checks on io.github.PetShopBros/lowdown-proxy, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://lowdown-proxy.vercel.app/mcp
- Repository: https://github.com/PetShopBros/lowdown-proxy
- Changelog RSS feed: https://verifymcp.io/servers/petshopbros-lowdown-proxy/lowdown-proxy-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/petshopbros-lowdown-proxy/lowdown-proxy-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/petshopbros-lowdown-proxy/lowdown-proxy-2.json
- HTML version of this page: https://verifymcp.io/servers/petshopbros-lowdown-proxy/lowdown-proxy-2
