# Canopy by Copp Oak > Book local service pros from your AI assistant: real availability, instant booking, easy cancels. - name: com.coppoak/canopy - version: 0.1.1 - connection class: R0 (autonomous) - trust: 83/100 flags: no-repository - quality: 91/100 (strong) - owner: not claimed - descriptor: https://api.protogrid.dev/v1/servers/com.coppoak%2Fcanopy - tools: https://api.protogrid.dev/v1/servers/com.coppoak%2Fcanopy/tools **An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe. ## Connection (mcpServers) ```json { "mcpServers": { "canopy": { "type": "http", "url": "https://mcp.coppoak.com/mcp/public" } } } ``` ## Trust - hygiene: 80 - liveness: 100 - freshness: 100 - provenance: 55 - drivers: +dns-namespace +website +reachable +uptime-100% +updated-3d-ago -no-repository - Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. ## Quality 91/100 (strong) ### protocol: 75 (weight 25) - warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28 - n/a `protocol.stateless`: only applies to 2026-07-28 servers - pass `protocol.transport`: streamable HTTP - n/a `protocol.list_ttl`: only applies to 2026-07-28 servers ### authorization: n/a (weight 15) - n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth - n/a `auth.secret_in_url`: no templated URL ### tool hygiene: 100 (weight 30) - pass `tools.descriptions`: every tool has a description - pass `tools.description_length`: descriptions are concise - pass `tools.schemas`: every tool has an object input schema - pass `tools.annotations`: 10 of 10 tools declare readOnlyHint or destructiveHint - pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint - pass `tools.token_cost`: about 6,538 tokens to load every tool - pass `tools.api_dump`: tools are not a one-to-one API dump - pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations ### stability: 100 (weight 15) - pass `stability.changes`: 1 tool changes in 30 days - pass `stability.rug_pull`: no tool changed its meaning under the same name - pass `stability.new_links`: no tool change named a new site ### dependencies: n/a (weight 15) - n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package - tools: 10, about 6,538 tokens to load them all - tool set hash: 3e4ed0394fa2b94436be94d3c04bb37b - tools last changed: 2026-11-04T02:02:21.598Z - badge: [![protogrid quality](https://protogrid.dev/badge/com.coppoak/canopy.svg)](https://protogrid.dev/servers/com.coppoak/canopy) - Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. ### Tool changes - 2026-11-04 `canopy_check_bookable` changed (description) - before: Given businesses you already found for the user (name plus phone, website or address), report which ones can be booked through Canopy and how (booking_mode). Results come back in exactly the order you sent them. Canopy never ranks, filters or recommends businesses. Results are returned in the same order as the input. - after: Given businesses you already found for the user (name plus phone, website or address with ZIP code), report which ones can be booked through Canopy and how (booking_mode). An entry that is not bookable says why (reason); needs_confirmation means use resolve_business so the user can confirm it. Results come back in exactly the order you sent them. Canopy never ranks, filters or recommends businesses. Results are returned in the same order as the input. Full history: https://api.protogrid.dev/v1/servers/com.coppoak%2Fcanopy/changes ## Remotes - https://mcp.coppoak.com/mcp/public (streamable-http, auth none, reachable true, uptime30d 1) ## Packages _none_ ## Tools (10) - `cancel_booking`: Cancel a booking made through Canopy. The appointment is called off in the business's calendar right away and the customer is emailed. This cannot be undone: confirm with the customer before calling. An appointment that has already started cannot be cancelled here. Needs the manage_token that came back with the booking_id. - `canopy_check_bookable`: Given businesses you already found for the user (name plus phone, website or address with ZIP code), report which ones can be booked through Canopy and how (booking_mode). An entry that is not bookable says why (reason); needs_confirmation means use resolve_business so the user can confirm it. Results come back in exactly the order you sent them. Canopy never ranks, filters or recommends businesses. Results are returned in the same order as the input. - `get_availability`: List open appointment slots for a Canopy business, optionally for one service and one location, between two dates. Slots are cached from the business calendar (see synced_at); the time is re-checked live when you book. - `get_business_terms`: Get the prices of a Canopy business's bookable services, its fees and its cancellation terms, exactly as the business has them on file. Anything the business has not put on file comes back as on_file=false: tell the customer it is not on file (they can ask the business) and never estimate or fill in a value. - `get_request_status`: This is Canopy's get-booking tool (there is no other): it looks up a booking request, and the booking an approved request became. Pass request_id and the manage_token that came back when the request was made (request_booking at a request-times business, propose_times or request_callback). Returns pending, approved, rejected, counter_proposed, expired, or converted, plus booking_confirmed and booking_status, and, once the business approves a time, the booking_id and booking_manage_token that reschedule_booking and cancel_booking need. An instant-confirm booking has no request_id: the request_booking response is already its record. Needs the manage_token. - `propose_times`: Propose preferred times to a business that reviews booking requests. The business will approve one time (that books it; the customer is emailed a confirmation) or propose an alternative (the customer confirms it from an emailed code). Check status with get_request_status. - `request_booking`: Start a booking with a Canopy-connected business. Canopy automatically routes to the correct flow based on the operator's booking mode: auto-confirm (booked right away in the business's calendar; the customer is emailed a confirmation), request-times (propose preferred times), or submission-only (callback request). Summarize the booking and get the customer's go-ahead before calling. - `request_callback`: Request a callback from a business. They will contact the customer directly. No calendar booking is created. - `reschedule_booking`: Ask to move a booking the customer already confirmed (booked with the business) to another open slot of the same service and location (slot_id from get_availability). Nothing moves right away: Canopy emails the customer a link to approve the new time, and the business calendar changes only after they approve. A hold the customer has not confirmed yet cannot be moved. Calling again with the same slot_id reports whether it was approved. Needs the manage_token that came back with the booking_id. - `resolve_business`: Match one business the user named to its Canopy listing, by phone, website, or name (add the city, state or ZIP code when you know it). Returns at most one match, with its booking_mode and locations, or found=false. When a name alone is not certain, found=false comes with up to 5 candidates in alphabetical order for the user to choose from.