General Tools
collisionrepairrva.com
Provides business information and quote request submission for a service provider.
ENDPOINT 1
https://collisionrepairrva.com/api/mcp/collision-repair-rva
MCP server metadata
- Name
- leadlord-collision-repair-rva
- Version
- 1.0.0
# LeadLord Site Builder — Recipe You are building a complete, lead-optimized website for one local service business by calling the LeadLord builder MCP tools. Your input is a single freeform brief (a paragraph or a page of notes). Your output is a **draft** tenant site — pages, globals, collections, forms, and media — that passes the build report and is ready for a human to review and publish. This recipe is the source of truth for *how* to build. It is deliberately **principles, a block palette, and guardrails, not a fixed page skeleton**: two different briefs must produce two materially different sites. Read the whole thing before you start calling tools. The companion file `block-catalog.md` is the "use-when" menu over the block palette; the live `describeBlocks` tool is the authority on exact block fields. The recipe is organized in four layers: - **Layer A — Block vocabulary.** What blocks exist and their real field shapes. Read at runtime via `describeBlocks`; never hard-code field names from memory. - **Layer B — Hard guardrails.** Non-negotiable MUSTs. These mirror exactly what `getBuildReport` checks. If you break one, the report will flag it and you cannot ship. - **Layer C — Composition heuristics.** Advisory, brief-conditioned. How to choose and order sections for *this* business. - **Layer D — Content & brand transformation.** How to turn the brief's brand and voice into theme tokens, copy, per-city angles, and imagery queries. Working with this server: - For the full recipe, load the `build_lead_gen_site` MCP prompt and pass your freeform brief as its `brief` argument. - If your client does not support MCP prompts, follow the overview above: call `describeBlocks` for exact block field shapes and rely on each tool's description for its guardrails. - Everything is written as a DRAFT. Run `getBuildReport` and resolve every item until it is clean before recommending publish; publishing is a separate, gated step.
Known tools 5
getBusinessInfoReturns the business name, tagline, and niche information for this tenant.
Inferred read-onlygetContactInfoReturns phone, email, address, and business hours for this tenant.
Potential side effectsCONNECT 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.leadlord-collision-repair-rva]
url = "https://collisionrepairrva.com/api/mcp/collision-repair-rva"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"leadlord-collision-repair-rva": {
"type": "http",
"url": "https://collisionrepairrva.com/api/mcp/collision-repair-rva"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: leadlord-collision-repair-rva
Remote MCP URL: https://collisionrepairrva.com/api/mcp/collision-repair-rva
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": {
"leadlord-collision-repair-rva": {
"url": "https://collisionrepairrva.com/api/mcp/collision-repair-rva"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"leadlord-collision-repair-rva": {
"type": "http",
"url": "https://collisionrepairrva.com/api/mcp/collision-repair-rva"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "leadlord-collision-repair-rva",
"transport": "streamable-http",
"url": "https://collisionrepairrva.com/api/mcp/collision-repair-rva"
}
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 collisionrepairrva.com was fetched 2026-08-24T05:07:27.345Z and is being refreshed.
collisionrepairrva.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.