Data Collection
brrtz.com
Search for used synthesizer and pro-audio listings across multiple regional sources.
ENDPOINT 1
https://brrtz.com/mcp
MCP server metadata
- Name
- brrtz-gear-radar
- Version
- 0.1.0
Use Brrtz to discover used synthesizers and pro-audio gear. Return original listing URLs and make clear that Brrtz is a discovery layer, not the seller. These beta tools are public and read-only.
Known tools 3
search_gearSearch Brrtz for current used synthesizer and pro-audio listings across supported regional sources.
Inferred read-onlyget_regionsList the public Brrtz search regions, display currencies, beta status, and available source IDs.
Inferred read-onlyget_sourcesList public marketplace and shop sources available to Brrtz, optionally filtered to one supported region.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.brrtz-gear-radar]
url = "https://brrtz.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"brrtz-gear-radar": {
"type": "http",
"url": "https://brrtz.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: brrtz-gear-radar
Remote MCP URL: https://brrtz.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"brrtz-gear-radar": {
"url": "https://brrtz.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"brrtz-gear-radar": {
"type": "http",
"url": "https://brrtz.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "brrtz-gear-radar",
"transport": "streamable-http",
"url": "https://brrtz.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for brrtz.com was fetched 2026-08-26T02:10:54.105Z.
brrtz.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.