Booqer MCP server
ai.booqer/booqerbooqer.aistreamable-httpv1.0.0Scanned
Verified Booqer shops. A keyless consult is confirmed when the slot is open.
8 tools: 2 can delete or cancel things, 2 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Booqer MCP server can do
The Booqer MCP server is published by booqer.ai, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (2 tools: request_booking and submit_service_request) and create or change data (2 tools: check_availability and request_service). 4 tools only read.
2 tools bring in text other people can write (request_booking and submit_service_request).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Deletes or cancels 2Claude Code: deny
request_bookingUse this when the user wants to book a local home-service appointment and has already chosen an open time.Reads text others writeNo findings
Why it is in this group
- The name "request_booking" says "request": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Use this when the user wants to book a local home-service appointment and has already chosen an open time. Confirms a free consult when the slot is open. Calling this again with the same details can create a second booking; if unsure, check get_booking_status first. Requires consent: before calling, show the user the consent text in the consent field and get their agreement. Also requires a name, a valid email, and a problem description. service_address is optional for a phone consult and required for an on-site visit. Disposable, reserved, and blocked email domains are rejected. job_summary falls back to problem. service_area is inferred from the address or city, otherwise the shop city. A phone consult accepts a street, a city and ZIP, or a PO Box. An on-site visit needs a street address. Shop-specific booking rules and emergency_phone come from get_business. offering is an id from get_business. start is an ISO-8601 timestamp, for example 2026-10-20T14:00:00-04:00. The start is at least 2 hours ahead and no more than 21 days ahead. A start outside that window names the field start. Returns status confirmed, a cancel link, and verify_url when the signed receipt is ready. The receipt page does not show the customer. An optional idempotency_key repeats the same result for that shop. Rate limited per IP and per shop, with a per-shop daily cap.
Annotations the server declares
- title: Request a consult
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: true
submit_service_requestSends the user's quote request (name, email, optional phone, service location, preferred time) to the chosen business.Reads text others writeNo findings
Why it is in this group
- The name "submit_service_request" says "submit": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Sends the user's quote request (name, email, optional phone, service location, preferred time) to the chosen business. Called by the quote form only.
Annotations the server declares
- title: Submit a service request
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Changes things 2Claude Code: ask
check_availabilityUse this when the user wants to check availability for a local home-service appointment before booking.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this when the user wants to check availability for a local home-service appointment before booking. Lists the open 30-minute slots for one shop and one date. Booked and blocked times are left out. Each start and end is ISO-8601 with an offset. The shop timezone is America/New_York. date is YYYY-MM-DD, or start is an ISO-8601 timestamp. offering selects that shop's rules from get_business. Does not reserve a slot. Rate limited per IP and per shop.
Annotations the server declares
- title: Check availability
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
request_serviceUse this when the user wants to open a quote form for a local home-service business rather than book a confirmed appointment time.1 finding
Why it is in this group
- The name "request_service" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "request_service" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "request_service" says "request": a word for a change.
Description, as the server wrote it Use this when the user wants to open a quote form for a local home-service business rather than book a confirmed appointment time. Opens the quote widget for one enrolled business. business_id is the provider_business_id from the business feed. shop_id is accepted when business_id is empty. The widget is ui://widget/request-service.html. This call does not store a request and does not confirm a booking. It is rate-limited.
Annotations the server declares
- title: Request a quote
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_booking_statusUse this when the user wants to check the status of a local home-service appointment.No findings
Why it is in this group
- The name "get_booking_status" says "get": a word for reading.
Description, as the server wrote it Use this when the user wants to check the status of a local home-service appointment. status is confirmed, pending, canceled, or failed. No customer name, phone, or email.
Annotations the server declares
- title: Booking status
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_businessUse this when the user wants to read one enrolled local home-service business and search_businesses or resolve_business already returned its id.No findings
Why it is in this group
- The name "get_business" says "get": a word for reading.
Description, as the server wrote it Use this when the user wants to read one enrolled local home-service business and search_businesses or resolve_business already returned its id. Returns one enrolled shop as JSON: id, brand, legal_name, page, booking_url, phone when published, sms, services as id and name, hours, timezone, verification status and verify_url, and booking_rules and emergency_phone when that shop has them.
Annotations the server declares
- title: Get a business
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
resolve_businessUse this when the user wants to resolve one enrolled local home-service business from a domain, a place, or a phone number.No findings
Why it is in this group
- The name "resolve_business" says "resolve": a word for reading.
Description, as the server wrote it Use this when the user wants to resolve one enrolled local home-service business from a domain, a place, or a phone number. An ambiguous match is refused. Returns that one identity. No phone, email, or street address is returned.
Annotations the server declares
- title: Resolve a business
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
search_businessesUse this when the user wants to find a local home-service business or appointment: plumber, HVAC, electrician, gate, fence, or security install, pole barn, or builder.No findings
Why it is in this group
- The name "search_businesses" says "search": a word for reading.
Description, as the server wrote it Use this when the user wants to find a local home-service business or appointment: plumber, HVAC, electrician, gate, fence, or security install, pole barn, or builder. Searches the Booqer directory of enrolled home-service businesses by name, category, service, location, or phone. Coverage is limited to enrolled businesses (currently Florida pole barn and gate/security). Returns id, name, domain, booking URL, and booking status. A trade that is not enrolled returns no businesses and the message says no shop is available. A city outside a business's service area is left out. booqer-demo-shop is omitted unless the query is that shop's exact name or id.
Annotations the server declares
- title: Search businesses
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:25 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (3 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://booqer.ai/mcp: tools/list returned 9 tools to an anonymous client, including request_booking (destructive), cancel_booking (destructive), submit_service_request (destructive), check_availability (write), request_service (write)
Posture changes
- Nov 20, 2026
- Tools that change things, listed without credentials: 4 to 5
Findings
Matches of fixed checks, with the text they matched.
- Warnrequest_service
The server marks "request_service" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "request_service" says "request": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 5.View diff
- Tools that change things, listed without credentials: 4 to 5
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http booqer https://booqer.ai/mcpclaude mcp add --transport http booqer https://booqer.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__booqer__search_businesses",
"mcp__booqer__get_business",
"mcp__booqer__resolve_business",
"mcp__booqer__get_booking_status"
],
"ask": [
"mcp__booqer__check_availability",
"mcp__booqer__request_service"
],
"deny": [
"mcp__booqer__request_booking",
"mcp__booqer__submit_service_request"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as booqer. Review it before you use it.
Capability tags behind 2 rules
- mcp__booqer__request_booking untrusted-input
- mcp__booqer__submit_service_request untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.booqer/booqer/verify?hash=1991b9841b5facc6dd6f68fc7d869f48adbb09c7091dce03f445414c0a8389fa" | jq -e '.changed == false'Pinned hash 1991b9841b5f, from Nov 11, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.booqer/booqer/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.booqer/booqer)Source: MCP Registry. Synced Oct 21, 2026, 17:41 UTC.
Booqer MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Booqer MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Booqer MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: request_booking and submit_service_request.
Can the Booqer MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Booqer MCP server have?
- 8 tools: 2 destructive, 2 write, 4 read. request_booking, submit_service_request, check_availability, request_service, search_businesses, get_business, resolve_business and get_booking_status.
Does the Booqer MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Booqer MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Booqer MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.