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 what Lowdown has recorded about an MCP server, agent, tool, or service before choosing or connecting to it. For MCP Registry servers it returns, in order: a |
| 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
Each tool targets a distinct operation: get_lowdown retrieves detailed recorded facts for a single target, compare_tools orders multiple candidates by interaction data, record_interaction writes new data, and get_node_stats reports the user's own node. The descriptions clearly delineate these boundaries with no meaningful overlap.
All tool names follow a consistent snake_case verb_noun pattern: get_lowdown, get_node_stats, record_interaction, compare_tools. The verbs (get, record, compare) are standard and predictable within the set.
Four tools is well-scoped for a reputation proxy that needs to support lookups, comparisons, contributions, and node stats. Each tool clearly earns its place without redundancy or bloat.
The core lifecycle of querying reputation (get_lowdown), comparing candidates (compare_tools), contributing data (record_interaction), and checking personal stats (get_node_stats) is covered. Minor gaps exist, such as no broad discovery/search or list operation for servers or agents, but core workflows are functional.