lowdown-proxy MCP server
io.github.PetShopBros/lowdown-proxyPetShopBrosstreamable-httpv0.1.23Scanned
Dated facts on MCP servers: daily checks, Registry and card declarations, packages, payment terms.
2 tools: 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 lowdown-proxy MCP server can do
The lowdown-proxy MCP server is published by the GitHub account PetShopBros. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 0.1.23.
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.
2 tools
Only reads 2Show 2 read-only tools
find_serversLowdown(로우다운) lists public MCP servers by observed facts, when you do not have a server name yet.2 findings
Why it is in this group
- The name "find_servers" says "find": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...wered initialize and tools/list without credentials), days answered in the last 30, how lon..."
- Info
The input schema at properties.state.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.state.description: "...answered' = answered tools/list with no credentials"
Description, as the server wrote it 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.
Annotations the server declares
- title: Find MCP servers by observed facts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_lowdownLowdown(로우다운) looks up recorded facts about an MCP server before installing or connecting to it.No findings
Why it is in this group
- The name "get_lowdown" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Look up recorded facts about an MCP server
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.
Looked at Nov 21, 2026, 19:23 UTC, unchanged since Oct 30, 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
- 0
- 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
Findings
Matches of fixed checks, with the text they matched.
- Infofind_servers
The description mentions "credentials".
What this check looks forMatched text
description: "...wered initialize and tools/list without credentials), days answered in the last 30, how lon..."
- Infofind_servers
The input schema at properties.state.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.state.description: "...answered' = answered tools/list with no credentials"
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:find_serversOnly readsdescription
- Changed:get_lowdownOnly readsdescription
Tools2 changed.~2 changedView diff
- Changed:find_serversOnly readsinputSchema
- Changed:get_lowdownOnly readsdescriptioninputSchema
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:find_serversOnly reads
- Changed:get_lowdownOnly readsinputSchema
Install
Pinned to version 0.1.23. Values in angle brackets are yours to fill in.
claude mcp add --transport http lowdown-proxy https://lowdown-proxy.vercel.app/mcpclaude mcp add --transport http lowdown-proxy https://lowdown-proxy.vercel.app/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__lowdown-proxy__get_lowdown",
"mcp__lowdown-proxy__find_servers"
],
"ask": [],
"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 lowdown-proxy. 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/io.github.PetShopBros/lowdown-proxy/verify?hash=3c952637ad877ec9d1fbfcaa1b225aa80dacf3954724e25e8f2f3c4b8b2b4196" | jq -e '.changed == false'Pinned hash 3c952637ad87, from Nov 14, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.PetShopBros/lowdown-proxy/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.PetShopBros/lowdown-proxy)Source: MCP Registry · repository. Synced Nov 14, 2026, 18:17 UTC.
lowdown-proxy MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the lowdown-proxy MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, all of which only read, and 2 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the lowdown-proxy MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the lowdown-proxy 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 lowdown-proxy MCP server have?
- 2 tools: 2 read. get_lowdown and find_servers.
Does the lowdown-proxy MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the lowdown-proxy MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the lowdown-proxy MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.