Direct Detailing Services MCP server
com.directdetailingservicesllc/bookingdirectdetailingservicesllc.comstreamable-httpv1.0.0Scanned
Mobile car detailing in Temecula & Murrieta, CA: quotes, open times and booking requests.
8 tools: 1 can delete or cancel things, 4 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- 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 Direct Detailing Services MCP server can do
The Direct Detailing Services MCP server is published by directdetailingservicesllc.com, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (1 tool: cancel_booking) and create or change data (4 tools: check_service_area, request_booking, change_booking_time and apply_mud_run_code). 3 tools only read.
1 tool reads private data (get_booking); 1 tool brings in text other people can write (get_booking); 1 tool can send data out of your system (request_booking). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 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 1Claude Code: deny
cancel_bookingCancel a booking (confirm with your user first).No findings
Why it is in this group
- The name "cancel_booking" says "cancel": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Cancel a booking (confirm with your user first). Free until 24 hours before; after that, the customer texts Ryan.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Changes things 4Claude Code: ask
apply_mud_run_codePut the customer's own Mud Run code on their Full detail: 10% off the detail (their first Full detail only).No findings
Why it is in this group
- The name "apply_mud_run_code" says "apply": a word for a change.
Description, as the server wrote it Put the customer's own Mud Run code on their Full detail: 10% off the detail (their first Full detail only).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
change_booking_timeMove a booking to another open time (find_open_times with the booking's job).No findings
Why it is in this group
- The description's first verb is "move": a word for a change.
Description, as the server wrote it Move a booking to another open time (find_open_times with the booking's job). Free until 24 hours before; it goes back to Ryan to confirm.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_service_areaIs a ZIP code in Ryan's service area?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 Is a ZIP code in Ryan's service area? He covers Temecula, Murrieta, Menifee, Wildomar, French Valley, Winchester.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
request_bookingBook a time for your user (confirm the details with them first).Can send data outNo findings
Why it is in this group
- The name "request_booking" says "request": a word for a change.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it Book a time for your user (confirm the details with them first). It goes to Ryan as a request: nothing is charged, he texts to confirm, and the customer gets an email with the details and a private link to change or cancel.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 3Show 3 read-only tools
find_open_timesRyan's open start times for this job (they depend on how long it takes).No findings
Why it is in this group
- The name "find_open_times" says "find": a word for reading.
Description, as the server wrote it Ryan's open start times for this job (they depend on how long it takes). Use a start_time exactly as given.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_bookingA booking, from the private change-or-cancel link in its confirmation email.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_booking" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it A booking, from the private change-or-cancel link in its confirmation email.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_quoteThe price for a service, with the plan prices (every 2 or 4 weeks) to offer once.No findings
Why it is in this group
- The name "get_quote" says "get": a word for reading.
Description, as the server wrote it The price for a service, with the plan prices (every 2 or 4 weeks) to offer once. Quotes are the price; Ryan confirms by text.
Annotations the server declares
- readOnlyHint: true
- 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.
1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__booking__request_booking"
]
}
}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:18 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 (1 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://directdetailingservicesllc.com/mcp: tools/list returned 8 tools to an anonymous client, including cancel_booking (destructive), check_service_area (write), request_booking (write), change_booking_time (write), apply_mud_run_code (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http booking https://directdetailingservicesllc.com/mcpclaude mcp add --transport http booking https://directdetailingservicesllc.com/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__booking__get_quote",
"mcp__booking__find_open_times",
"mcp__booking__get_booking"
],
"ask": [
"mcp__booking__check_service_area",
"mcp__booking__request_booking",
"mcp__booking__change_booking_time",
"mcp__booking__apply_mud_run_code"
],
"deny": [
"mcp__booking__cancel_booking"
]
}
}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 booking. Review it before you use it.
Capability tags behind 2 rules
- mcp__booking__request_booking outbound
- mcp__booking__get_booking private-data, 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/com.directdetailingservicesllc/booking/verify?hash=f43af875e28e9ef003aa2b7333fed367eb1be750841dcd561232b7bc6f5533e1" | jq -e '.changed == false'Pinned hash f43af875e28e, from Nov 20, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.directdetailingservicesllc/booking/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.directdetailingservicesllc/booking)Source: MCP Registry. Synced Nov 20, 2026, 02:17 UTC.
Direct Detailing Services MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Direct Detailing Services MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Direct Detailing Services MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: cancel_booking.
Can the Direct Detailing Services 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 Direct Detailing Services MCP server have?
- 8 tools: 1 destructive, 4 write, 3 read. cancel_booking, check_service_area, request_booking, change_booking_time, apply_mud_run_code, get_quote, find_open_times and get_booking.
Does the Direct Detailing Services MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Direct Detailing Services MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): request_booking.
Has the Direct Detailing Services MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.