mcp-registry/com.opuslumiere/booking · v2.1.0
As of 2026-10-22 21:50 UTC, the Opuslumiere Booking MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 7 minutes.
Read-only booking info for Opus Lumiere photography, London: services, prices, availability.
Claude Code
claude mcp add --transport http opuslumiere-booking-mcp-server https://opuslumiere.com/wp-json/opus-booking/v1/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"opuslumiere-booking-mcp-server": {
"type": "http",
"url": "https://opuslumiere.com/wp-json/opus-booking/v1/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~2,028 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.opuslumiere%2Fbooking/fixes
{
"name": "check_availability",
"description": "Live open appointment slots for a service id (from list_services) over an optional date range (default next 5 weeks, max 62 days). Slots are not held - the customer reserves by completing checkout (with payment) at the booking_url.",
"inputSchema": {
"type": "object",
"required": [
"service_id"
],
"properties": {
"date_to": {
"type": "string",
"description": "End date YYYY-MM-DD (optional)."
},
"date_from": {
"type": "string",
"description": "Start date YYYY-MM-DD (optional, default today)."
},
"service_id": {
"type": "integer",
"description": "Service id from list_services."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_booking_link",
"description": "The page where a customer completes an Opus Lumière booking, including secure card payment and deposit options. Optionally pass a service_id. Payment can never travel through this API - never ask users for card details.",
"inputSchema": {
"type": "object",
"properties": {
"service_id": {
"type": "integer",
"description": "Optional service id from list_services."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_business_hours",
"description": "Opus Lumière session hours by weekday, with timezone (Europe/London) - overall and for each kind of photoshoot (outdoor, studio, at home). Sessions are by appointment - confirm a real slot with check_availability.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.opuslumiere/booking"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.opuslumiere/booking"}) over MCP.
check_availability ~167 tokensget_booking_link ~111 tokensget_business_hours ~86 tokenslist_services ~82 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.opuslumiere%2Fbooking?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.opuslumiere%2Fbooking?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.opuslumiere%2Fbooking.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.opuslumiere%2Fbooking.svg :target: https://glimind.com/server/mcp-registry%2Fcom.opuslumiere%2Fbooking?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8a2a15c001c4def2…, first seen 2026-10-22, included at leaf 44193 of 48,332. Version history · verify what your client received.
Compare: most reliable calendar servers · most reliable web servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 21:50 UTC, the Opuslumiere Booking MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 7 minutes.
Opuslumiere Booking MCP server advertises 4 tools, including check_availability, get_booking_link, get_business_hours, list_services.
Point your MCP client at this streamable-http endpoint: https://opuslumiere.com/wp-json/opus-booking/v1/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.