Sweepless in Seattle MCP server
com.sweeplessinseattle/quotesweeplessinseattle.comstreamable-httpv1.0.0Scanned
Request a free house cleaning quote from Sweepless in Seattle, a Seattle cleaning company.
1 tool: 1 do something that can't be undone.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Sweepless in Seattle MCP server can do
The Sweepless in Seattle MCP server is published by sweeplessinseattle.com, a domain the MCP Registry verified. It has 1 tool. It can do things that cannot be undone, such as sending, paying or publishing (request_quote), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (request_quote); 1 tool can send data out of your system (request_quote).
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 21, 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.
1 tool
Can't be undone 1Claude Code: ask
request_quoteSend a house cleaning quote request to Sweepless in Seattle for a customer who asked for one.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "request_quote" says "request": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it Send a house cleaning quote request to Sweepless in Seattle for a customer who asked for one. Covers Seattle, the Eastside and the South Sound. The request goes straight into the business scheduling system, and they reply to the customer with a flat, upfront price within one business day. Confirm the details with the customer before calling, and call once per quote.
Annotations the server declares
- title: Request a cleaning quote
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
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.
- Reads private data0
- 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.
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 21, 2026, 19:19 UTC, unchanged since Nov 21, 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
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://sweeplessinseattle.com/.well-known/oauth-protected-resource/mcp
- 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 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://sweeplessinseattle.com/mcp: tools/list returned 1 tool to an anonymous client, including request_quote (irreversible)
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 quote https://sweeplessinseattle.com/mcpclaude mcp add --transport http quote https://sweeplessinseattle.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": [],
"ask": [
"mcp__quote__request_quote"
],
"deny": []
}
}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 quote. Review it before you use it.
Capability tags behind 1 rule
- mcp__quote__request_quote untrusted-input, outbound
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.sweeplessinseattle/quote/verify?hash=8ba01a932a60107b544c37626d30d21c73d9f076fcbb528c6611bf5b13d6ddfb" | jq -e '.changed == false'Pinned hash 8ba01a932a60, from Nov 21, 2026, 04:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.sweeplessinseattle/quote/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.sweeplessinseattle/quote)Source: MCP Registry. Synced Nov 21, 2026, 05:17 UTC.
Sweepless in Seattle MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Sweepless in Seattle MCP server safe?
- No scan can promise that. What its definitions show: 1 tool, 1 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 Sweepless in Seattle MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Sweepless in Seattle MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: request_quote.
What tools does the Sweepless in Seattle MCP server have?
- 1 tool: 1 irreversible. request_quote.
Does the Sweepless in Seattle MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Sweepless in Seattle 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_quote.
Has the Sweepless in Seattle MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.