Content Tools
vetclinic.info
Provides veterinary clinic and procedure information for specialty searches.
ENDPOINT 1
https://vetclinic.info/mcp
MCP server metadata
- Name
- vetclinic.info MCP server
- Version
- 1.24.0
vetclinic.info — board-certified specialty + emergency veterinary directory (US). Tools: search_clinics, get_clinic, get_procedure, list_specialties, list_procedures, find_specialists_by_procedure, estimate_procedure_cost, quote_for_case. Resources: procedure-article://<slug>. Read tools are anonymous; quote_for_case requires X-Agent-Attribution when PII is supplied.
Known tools 8
get_clinicFetch a single clinic's full record by slug: credentials, inline reviews, procedures performed, contact action, canonical URL.
Inferred read-onlyget_procedureFetch a procedure article with cost band, contraindications, emergency signals, FAQ, citations.
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.vetclinic-info-mcp-server]
url = "https://vetclinic.info/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vetclinic-info-mcp-server": {
"type": "http",
"url": "https://vetclinic.info/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vetclinic-info-mcp-server
Remote MCP URL: https://vetclinic.info/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": {
"vetclinic-info-mcp-server": {
"url": "https://vetclinic.info/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vetclinic-info-mcp-server": {
"type": "http",
"url": "https://vetclinic.info/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vetclinic-info-mcp-server",
"transport": "streamable-http",
"url": "https://vetclinic.info/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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.