Desk by Ouroboros Apps

Name: Desk by Ouroboros Apps
Author: LAHutchins91

MCP serverMCP

Customer support answers, refund rules, and escalation limits for AI assistants

by LAHutchins91repository ↗homepage ↗v1.0.3

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"desk","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability13/13 checks ok

30 days ago

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	126 ms	server Desk 0.1.0 · protocol 2025-06-18 · 13 tools
2 h ago	mcp initialize	ok	200	136 ms	server Desk 0.1.0 · protocol 2025-06-18 · 13 tools
9 h ago	mcp initialize	ok	200	133 ms	server Desk 0.1.0 · protocol 2025-06-18 · 13 tools
15 h ago	mcp initialize	ok	200	194 ms	server Desk 0.1.0 · protocol 2025-06-18 · 13 tools
22 h ago	mcp initialize	ok	200	161 ms	server Desk 0.1.0 · protocol 2025-06-18 · 13 tools
28 h ago	mcp initialize	ok	200	133 ms	server Desk 0.1.0 · protocol 2025-06-18 · 13 tools
34 h ago	mcp initialize	ok	200	130 ms	server Desk 0.1.0 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	158 ms	server Desk 0.1.0 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	155 ms	server Desk 0.1.0 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	146 ms	server Desk 0.1.0 · protocol 2025-06-18 · 13 tools

Tools observed via MCP handshake

list_support_desks — List this team's support desks. Use the returned id. Do not guess a desk.
create_support_desk — Create a support desk when the user asks for a new policy home. Does not approve answers, refunds, features, or timelines.
save_approved_answer — Store or revise an answer the user has explicitly approved. Identical retries keep the same revision. A changed answer requires expectedRevision from a previous
search_approved_answers — 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 pro
save_refund_rule — 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
list_refund_rules — 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 r
save_escalation_limit — 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 th
list_escalation_limits — Read escalation limits. A channel with no APPROVED limit cannot promise a refund, feature, or timeline and cannot be given an invented escalation path.
save_approved_commitment — 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
list_approved_commitments — Read approved feature and timeline statements. Listing them does not approve a different promise. Call evaluate_commitment with the exact wording before saying
evaluate_commitment — 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 revi
evaluate_escalation — 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
get_desk_context — Retrieve selected approved answers for a customer question, plus the desk's approved refund rules, commitments, and escalation limits. This is evidence, not per

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.LAHutchins91/desk

first seen 3 d ago · fetched 2 h agoopen ↗

Field history (12 recent events)

2 h ago · declared · name → "Desk by Ouroboros Apps"
2 h ago · declared · summary → "Customer support answers, refund rules, and escalation limits for AI assistants"
2 h ago · declared · description → "Customer support answers, refund rules, and escalation limits for AI assistants"
2 h ago · declared · homepageUrl → "https://ouroborosapps.com/docs/desk"
2 h ago · declared · version → "1.0.3"
3 d ago · declared · version → "1.0.1"
3 d ago · declared · summary → "Approved support answers, refund rules, and escalation limits for AI assistants, over MCP."
3 d ago · declared · protocols → ["mcp"]
3 d ago · declared · description → "Approved support answers, refund rules, and escalation limits for AI assistants, over MCP."
3 d ago · declared · publisherName → "LAHutchins91"
3 d ago · declared · homepageUrl → "https://desk-mcp.vercel.app"
3 d ago · declared · repoUrl → "https://github.com/LAHutchins91/desk-mcp"

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from