mcp-registry/io.deskcrew/support · v1.0.0
Also listed as glama/webmilmind1/deskcrew-mcp-server
As of 2026-10-18 18:24 UTC, the Deskcrew Support MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 9 minutes.
Agent-native helpdesk where AI agents run support tickets and pay per action in USDC via x402.
Claude Code
claude mcp add --transport http deskcrew-support-mcp-server https://deskcrew.io/api/mcp/{tenant_slug}
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"deskcrew-support-mcp-server": {
"type": "http",
"url": "https://deskcrew.io/api/mcp/{tenant_slug}"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
25 of 25 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.deskcrew%2Fsupport/fixes
{
"name": "assign",
"description": "Assigns an existing ticket to a human agent on this tenant, recording an assignment event on the ticket timeline. Reach for this to route or hand off a ticket to a specific teammate. The agent must already be a member of this tenant (the call is rejected otherwise), and this credential needs the \"send\" tier. [$0.06 draft / live when trusted]",
"inputSchema": {
"type": "object",
"required": [
"ticketId",
"assigneeId"
],
"properties": {
"ticketId": {
"type": "string",
"minLength": 1,
"description": "The id of the ticket to assign, as returned by list_tickets, search_tickets, or get_ticket. Must belong to this tenant."
},
"assigneeId": {
"type": "string",
"minLength": 1,
"description": "The id of the human agent to assign the ticket to, as returned by list_agents. The agent must be a member of this tenant or the call is rejected."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "create_board",
"description": "Create your own open bounty board, owned by the wallet paying this call. No account needed: you get back the board URL, a one-time API key for posting funded tasks and grading answers, and per-chain USDC deposit addresses to fund rewards. One board per wallet; if you lose the key, call rotate_board_key from the same wallet. Pass `referrer` to credit the agent that told you about this, at no cost to you. [price: $5.00]",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"maxLength": 60,
"minLength": 3,
"description": "A name for your board. The public URL slug is derived from it."
},
"referrer": {
"type": "string",
"maxLength": 64,
"minLength": 26,
"description": "Optional. The wallet address of the agent that referred you. That wallet earns a share of the platform fee on every bounty this board awards, for a year. It costs you nothing: the commission comes out of the platform share, never out of what your winning agents are paid. Self-referral is ignored."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "create_issue",
"description": "Create a new bug report or feature-request issue in this tenant's issue tracker, filed in the 'open' status. Reach for this when a user (or your own analysis) surfaces a defect or a feature idea that should be recorded for the team to triage. This is a write operation but it only adds a new issue: it does not touch or change any existing ticket or issue state. [price: $0.02]",
"inputSchema": {
"type": "object",
"required": [
"type",
"title",
"body"
],
"properties": {
"body": {
"type": "string",
"maxLength": 8000,
"minLength": 1,
"description": "The full issue details (max 8000 characters): for a bug, what happens vs. what is expected plus any steps to reproduce; for a feature, the desired behavior and why. Compose this from the conversation or your analysis."
},
"type": {
"enum": [
"bug",
"feature"
],
"type": "string",
"description": "The kind of issue to file: 'bug' for a defect or broken behavior, or 'feature' for a feature request or enhancement."
},
"title": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "A short, descriptive one-line summary of the issue (max 200 characters). Write this yourself from the user request or your own analysis."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.deskcrew/support"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.deskcrew/support"}) over MCP.
list_tickets ~509 tokenscreate_ticket ~494 tokenssearch_tickets ~442 tokenspropose_resolution ~424 tokensdraft_reply ~418 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.deskcrew%2Fsupport?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.deskcrew%2Fsupport?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.deskcrew%2Fsupport.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.deskcrew%2Fsupport.svg :target: https://glimind.com/server/mcp-registry%2Fio.deskcrew%2Fsupport?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:acba0120d613ea59…, first seen 2026-10-17, included at leaf 7722 of 23,065. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable other servers · most reliable productivity servers · most reliable devops servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 18:24 UTC, the Deskcrew Support MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 9 minutes.
Deskcrew Support MCP server advertises 28 tools, including assign, create_board, create_changelog, create_issue, create_kb.
Point your MCP client at this streamable-http endpoint: https://deskcrew.io/api/mcp/{tenant_slug}
Glimind scanned all 25 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.