Data Collection

louvue.com

Provides tools to search Louisville, KY restaurant inspection records, retrieve detailed inspection and violation histories, and view city-wide inspection statistics.

1 endpoint3 known toolsFirst detected October 15, 2026Last detected October 15, 2026

ENDPOINT 1

https://louvue.com/mcp

No auth detected

MCP server metadata

Name: louvue-mcp
Version: 0.1.0

Capabilities

tools

Known tools 3

searchRestaurants

Search Louisville, KY restaurants by name/address/city/ZIP.

Inferred read-only

getRestaurantDetail

Return full inspection + violation history for one restaurant by numeric ID.

Inferred read-only

getInspectionStats

City-wide aggregate stats: total restaurants, total inspections, grade distribution.

Inferred read-only

CONNECT 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.louvue-mcp]
url = "https://louvue.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "louvue-mcp": {
      "type": "http",
      "url": "https://louvue.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: louvue-mcp
Remote MCP URL: https://louvue.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": {
    "louvue-mcp": {
      "url": "https://louvue.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "louvue-mcp": {
      "type": "http",
      "url": "https://louvue.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "louvue-mcp",
  "transport": "streamable-http",
  "url": "https://louvue.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.