
Rodi Scales MCP server
Which MCP servers are Rodi Scales's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-28
- Registry namecom.rodiscales/bay-motorsverified in the MCP registry
The registry name sits under rodiscales.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-28
- Tools6
- Server calls itselfagent-front-door/bay-motors
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 755 ms.
- Its tools do none of the product's use cases we checked: Answer calls the shop misses after hours and when lines are busy; Capture caller name, vehicle and symptom for missed repair jobs; Run a free count of how many calls the shop misses.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score71 of 100answers 100 · does the job 0 · definitions 94 · context 100 · connects 100
- What an agent can do with it0 of 3 use cases
- Answered100% of days7 of 7 daily checks
- Median first answer980 ms
- Space in an agent's context≈ 953 tokensthe definitions of all its tools (6), which an agent carries on every turn
- Tool definitionsA · 94 of 100
- Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
- Not saying whether it only reads or can destroy: 2 of 6
What an agent can do with it
- cannot · Answer calls the shop misses after hours and when lines are busy
- cannot · Capture caller name, vehicle and symptom for missed repair jobs
- cannot · Run a free count of how many calls the shop misses
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
get_shopShop profile: name, address, phone, hours, what it works on, what it does not, booking policy, and who verified the listing. Read-only.
list_servicesServices the shop offers in plain language, with exclusions. Read-only.
get_availabilityOpen drop-off windows for the next N days from the shop booking policy. Not a live calendar; the shop confirms every request. Read-only.
request_quoteAsk the shop for a quote. Creates a request the shop answers by phone or text; returns a reference and status "requested". The shop confirms estimates directly.
request_bookingRequest a drop-off appointment. Creates a booking request the shop confirms or declines; returns a reference and status "requested". No payment, no OTP; the shop calls or texts the contact to confirm.
get_statusStatus of a quote or booking request by reference: requested, confirmed or declined. Returns no contact data. Read-only.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"bay-motors": {
"type": "http",
"url": "https://agents.rodiscales.com/bay-motors/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http rodiscales https://agents.rodiscales.com/bay-motors/mcpclaude.ai, ChatGPT and other clients: add https://agents.rodiscales.com/bay-motors/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.