Desk by Ouroboros Apps MCP server
io.github.LAHutchins91/deskLAHutchins91streamable-httpv1.0.3Scanned
Customer support answers, refund rules, and escalation limits for AI assistants
13 tools: 4 can delete or cancel things, 3 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 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 Desk by Ouroboros Apps MCP server can do
The Desk by Ouroboros Apps MCP server is published by the GitHub account LAHutchins91. It has 13 tools. It can delete or cancel things (4 tools: save_approved_answer, save_refund_rule, save_escalation_limit and save_approved_commitment) and create or change data (3 tools: create_support_desk, evaluate_commitment and evaluate_escalation). 6 tools only read.
2 tools can send data out of your system (evaluate_commitment and evaluate_escalation).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.0.3.
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.
13 tools
Deletes or cancels 4Claude Code: deny
save_approved_answerStore or revise an answer the user has explicitly approved.No findings
Why it is in this group
- The name "save_approved_answer" says "save": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Store or revise an answer the user has explicitly approved. Identical retries keep the same revision. A changed answer requires expectedRevision from a previous read.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
save_approved_commitmentStore a feature or timeline statement the user has explicitly approved.No findings
Why it is in this group
- The name "save_approved_commitment" says "save": a word for a change.
- The input takes a statement or command to run (input.statement), which can change anything it can reach.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Store a feature or timeline statement the user has explicitly approved. The statement is the only wording that can later pass evaluate_commitment. Do not save a date or a feature the user did not approve.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
save_escalation_limitStore the escalation limit the user has explicitly approved for one channel.No findings
Why it is in this group
- The name "save_escalation_limit" says "save": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Store the escalation limit the user has explicitly approved for one channel. maxTier must be on tierLadder. Promise flags default closed unless the user sets them true. A limit does not itself approve refund, feature, or timeline wording.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
save_refund_ruleStore a refund rule the user has explicitly approved.No findings
Why it is in this group
- The name "save_refund_rule" says "save": a word for a change.
- The name "save_refund_rule" also says "refund": a word that usually means money moves, which cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Store a refund rule the user has explicitly approved. matchTerms must name a specific situation. The word refund alone is not a rule. remedy is the only wording that may later be approved. decision ALLOW grants that wording. decision DENY refuses a refund and records the denial script.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Changes things 3Claude Code: ask
create_support_deskCreate a support desk when the user asks for a new policy home.No findings
Why it is in this group
- The name "create_support_desk" says "create": a word for a change.
Description, as the server wrote it Create a support desk when the user asks for a new policy home. Does not approve answers, refunds, features, or timelines.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
evaluate_commitmentDecide whether a proposed refund, feature, or timeline is in the approved set.Can send data out1 finding
Why it is in this group
- The name "evaluate_commitment" says "evaluate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.channel): what the tool writes goes there.
Findings
- Warn
The server marks "evaluate_commitment" 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 "evaluate_commitment" says "evaluate": a word for a change.
Description, as the server wrote it Decide whether a proposed refund, feature, or timeline is in the approved set. REFUSED means do not say it, do not invent a substitute, and draft for human review instead of promising the customer. APPROVED means sayOnly is the only permitted wording. Pass channel to also enforce the escalation limit.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
evaluate_escalationDecide whether this channel may escalate or may promise a refund, feature, or timeline.Can send data out1 finding
Why it is in this group
- The name "evaluate_escalation" says "evaluate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.channel): what the tool writes goes there.
Findings
- Warn
The server marks "evaluate_escalation" 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 "evaluate_escalation" says "evaluate": a word for a change.
Description, as the server wrote it Decide whether this channel may escalate or may promise a refund, feature, or timeline. REFUSED means do not escalate, do not invent a tier, and draft for human review instead of promising the customer. Permission to promise still requires evaluate_commitment for the exact wording.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 6Show 6 read-only tools
get_desk_contextRetrieve selected approved answers for a customer question, plus the desk's approved refund rules, commitments, and escalation limits.No findings
Why it is in this group
- The name "get_desk_context" says "get": a word for reading.
Description, as the server wrote it Retrieve selected approved answers for a customer question, plus the desk's approved refund rules, commitments, and escalation limits. This is evidence, not permission. A missing or RETIRED answer is not an invitation to invent one. Call evaluate_commitment before promising a refund, feature, or timeline. If tools fail or return gaps or REFUSED, draft for human review instead of promising the customer.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_approved_commitmentsRead approved feature and timeline statements.No findings
Why it is in this group
- The name "list_approved_commitments" says "list": a word for reading.
Description, as the server wrote it Read approved feature and timeline statements. Listing them does not approve a different promise. Call evaluate_commitment with the exact wording before saying one.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_escalation_limitsRead escalation limits.No findings
Why it is in this group
- The name "list_escalation_limits" says "list": a word for reading.
Description, as the server wrote it Read escalation limits. A channel with no APPROVED limit cannot promise a refund, feature, or timeline and cannot be given an invented escalation path.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_refund_rulesRead refund rules on a desk.No findings
Why it is in this group
- The name "list_refund_rules" says "list": a word for reading.
Description, as the server wrote it Read refund rules on a desk. Only APPROVED rules can authorize wording, and only through evaluate_commitment. Do not treat this list as permission to invent a refund.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_support_desksList this team's support desks.No findings
Why it is in this group
- The name "list_support_desks" says "list": a word for reading.
Description, as the server wrote it List this team's support desks. Use the returned id. Do not guess a desk.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_approved_answersLook up approved answers by topic, question, or answer text.No findings
Why it is in this group
- The name "search_approved_answers" says "search": a word for reading.
Description, as the server wrote it Look up approved answers by topic, question, or answer text. An empty result means there is no approved answer. Draft for human review; do not invent one or promise the customer. Page with offset.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: 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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- 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:58 UTC, unchanged since Oct 22, 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
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://desk-mcp-continuity2.vercel.app/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://rwmcpgsdugkishzsgxnw.supabase.co/auth/v1
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (4 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://desk-mcp-continuity2.vercel.app/mcp: tools/list returned 13 tools to an anonymous client, including save_approved_answer (destructive), save_refund_rule (destructive), save_escalation_limit (destructive), save_approved_commitment (destructive), create_support_desk (write) and 2 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "evaluate_commitment" 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 "evaluate_commitment" says "evaluate": a word for a change.
The server marks "evaluate_escalation" 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 "evaluate_escalation" says "evaluate": a word for a change.
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.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http desk https://desk-mcp-continuity2.vercel.app/mcpclaude mcp add --transport http desk https://desk-mcp-continuity2.vercel.app/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__desk__list_support_desks",
"mcp__desk__search_approved_answers",
"mcp__desk__list_refund_rules",
"mcp__desk__list_escalation_limits",
"mcp__desk__list_approved_commitments",
"mcp__desk__get_desk_context"
],
"ask": [
"mcp__desk__create_support_desk",
"mcp__desk__evaluate_commitment",
"mcp__desk__evaluate_escalation"
],
"deny": [
"mcp__desk__save_approved_answer",
"mcp__desk__save_refund_rule",
"mcp__desk__save_escalation_limit",
"mcp__desk__save_approved_commitment"
]
}
}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 desk. Review it before you use it.
Capability tags behind 2 rules
- mcp__desk__evaluate_commitment outbound
- mcp__desk__evaluate_escalation 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/io.github.LAHutchins91/desk/verify?hash=a9ea1bc8b737f1ee3fd14d6b3335f0eab2decad822d3e529895416683a5020d2" | jq -e '.changed == false'Pinned hash a9ea1bc8b737, from Nov 15, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.LAHutchins91/desk/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.LAHutchins91/desk)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:17 UTC.
Desk by Ouroboros Apps MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Desk by Ouroboros Apps MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 7 of which can change, send or delete something, and 2 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 Desk by Ouroboros Apps MCP server delete data?
- Yes. 4 tools can delete, cancel or revoke something: save_approved_answer, save_refund_rule, save_escalation_limit and save_approved_commitment.
Can the Desk by Ouroboros Apps 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 Desk by Ouroboros Apps MCP server have?
- 13 tools: 4 destructive, 3 write, 6 read. save_approved_answer, save_refund_rule, save_escalation_limit, save_approved_commitment, create_support_desk, evaluate_commitment, evaluate_escalation, list_support_desks and 5 more.
Does the Desk by Ouroboros Apps MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Desk by Ouroboros Apps MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): evaluate_commitment and evaluate_escalation.
Has the Desk by Ouroboros Apps MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.