Karrinyup Dental Centre Agent Integration
Use this guide to retrieve public information from Karrinyup Dental Centre, a dental clinic in Karrinyup, Western Australia. Cite the original page when sharing clinic information.
Read public pages
Start with /llms.txt to find relevant pages. Request a page with Accept: text/markdown, or append index.md to a page path for an explicit Markdown representation. Ordinary browser requests return HTML. Unknown pages return a 404.
The examples use relative paths. Resolve them against the website origin you are visiting. Source links retain the clinic’s canonical identity at https://karrinyupdental.com.au.
GET /contact-us/
Accept: text/markdown
GET /contact-us/index.mdRead the public JSON API
GET /api/v1/clinic returns published clinic contact details and opening hours. GET /api/v1/services lists public service summaries; add the optional path query parameter for one exact local service page. GET /api/v1/search requires q (1–200 characters after trimming) and accepts limit (integer 1–9, default 5). These endpoints also support HEAD without a response body.
No authentication, account or API key is required. The OpenAPI 3.1 contract at /openapi.json describes typed parameters, success bodies and errors. JSON API errors use application/problem+json (RFC 9457), with type, title, status, detail, instance and the extension fields code and resolution. Invalid or duplicate arguments return 400; unknown endpoints and absent services return 404; write methods return 405 with Allow: GET, HEAD.
The REST API and MCP share the same public facts, local search and validation limits. Neither interface can access patient data, diagnose conditions, submit forms or book appointments. Do not put personal or health information in query parameters.
GET /api/v1/clinic
GET /api/v1/services?path=%2Fgeneral-dentistry%2Fscale-and-clean%2F
GET /api/v1/search?q=scale%20and%20clean&limit=3Connect with MCP
Configure your MCP client with the Streamable HTTP endpoint /mcp on this website’s origin. The public endpoint requires no API key. It provides stateless JSON responses using the official Model Context Protocol TypeScript SDK. The implemented protocol revision is 2025-11-25; initialization negotiates compatible versions.
Send initialize first, then notifications/initialized, then tools/list or tools/call. Each JSON-RPC message is a separate POST with Content-Type: application/json and Accept: application/json, text/event-stream. Subsequent requests should include MCP-Protocol-Version with the negotiated version. No Mcp-Session-Id is issued. GET and DELETE return 405 because this server has no persistent notification stream or session to terminate.
Requests are limited to 16 KiB. Unknown methods, invalid arguments and unsupported protocol versions return protocol errors. Tool execution failures return isError. Browser Origins are restricted to the clinic and configured deployment origins; untrusted Origins return 403. Native MCP clients normally omit Origin.
POST /mcp
Content-Type: application/json
Accept: application/json, text/event-stream
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"public-information-client","version":"1.0.0"}}}
POST /mcp
Content-Type: application/json
Accept: application/json, text/event-stream
MCP-Protocol-Version: 2025-11-25
{"jsonrpc":"2.0","method":"notifications/initialized"}Choose a public information tool
get_clinic_info takes an empty object. Use it for published contact details, address and opening hours. Confirm changes and appointment availability directly with the clinic.
get_service_info takes an optional path such as /general-dentistry/scale-and-clean/. Omit path to list public service summaries and their source links. Only existing dental service pages are available.
search_public_content takes a query of 1–200 characters and an optional integer limit of 1–9 (default 5). Use it to find relevant public pages and short descriptions in the website’s local search index. It does not search patient information or external websites.
POST /mcp
Content-Type: application/json
Accept: application/json, text/event-stream
MCP-Protocol-Version: 2025-11-25
{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"search_public_content","arguments":{"query":"scale and clean","limit":3}}}Discovery metadata
/.well-known/mcp redirects to /mcp/server-card for convenient discovery. The server card follows the current experimental Server Cards extension; the compatibility address /.well-known/mcp/server-card.json returns the same card. These cards are advisory metadata, not an accepted core MCP discovery standard.
/.well-known/ard.json and /.well-known/ai-catalog.json provide the same ARD-compatible resource catalog. The separate RFC 9727 API catalog at /.well-known/api-catalog links the public REST endpoints to their OpenAPI contract, documentation and authentication guide.
Read tools/list after initialization for the authoritative tool schemas. Discovery cards intentionally describe identity and connection details rather than duplicating the live tool list.
Scope and limitations
All tools are read-only and expose already-public website information. There is no access to patient records, messages, form submissions, appointment schedules or booking actions. The tools do not diagnose conditions, decide treatment suitability or provide individual treatment advice.
Do not include personal or health information in tool arguments. Public educational content can help locate information, but a dental professional must assess individual needs. For bookings or questions about care, use the clinic’s existing contact page and booking links.
This integration describes the clinic. It does not represent a hosting provider’s product or imply endorsement by a hosting provider.