lowdown-proxy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOWDOWN_SUPABASE_KEY | No | Supabase key used for recording interactions. Required for recording; the proxy works as a pure pass-through without it. | |
| LOWDOWN_SUPABASE_URL | No | Supabase URL used for recording interactions. Required for recording; the proxy works as a pure pass-through without it. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_lowdownA | Look 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 an npm package ('npm:@scope/name'). Returns, in order: |
| record_interactionA | Record an interaction with an agent, tool, or service after using it. Helps build the shared reputation dataset for the community. If the call was an intentional negative test (e.g. deliberately invalid input), set source to 'synthetic' so it is not counted as a failure of the target. |
| compare_toolsA | Compare 2 to 5 tools or agents by the interactions reported to Lowdown. Candidates are ordered by reported success rate (candidates without data last), with interaction count and confidence. Scanner observations are not used for the ordering. A suggestion is included only when the first candidate has at least 5 rated interactions. |
| get_node_statsB | Get your node's contribution stats and network position. Shows how much your proxy has contributed to the Lowdown network. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The four tools have clearly distinct actions: lookup server facts, compare candidate tools/agents, view node stats, and record an interaction. Although interaction data appears in both get_lowdown and compare_tools, their outputs and purposes are distinct enough to avoid confusion.
All tool names use a consistent snake_case verb_noun pattern: get_lowdown, compare_tools, get_node_stats, record_interaction. The convention is predictable throughout.
Four tools is a well-scoped set for a reputation/proxy server: one lookup tool, one comparison tool, one contribution recorder, and one node-status tool. Each has a clear role and there is no unnecessary bloat.
The surface covers the core lifecycle of looking up a server, comparing candidates, contributing interaction data, and checking node contribution. Minor gaps exist, such as no search/list operation and no dedicated single-agent profile beyond compare_tools, but agents can work around them.