ai.deskcrew/agentic
REMOTE · DESKCREW.AI · SCANNED AUG 3
Buy a managed AI phone agent for a business, paid keylessly via x402/RLUSD on the XRP Ledger.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 501 tokens (~125/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 5% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · deskcrew.ai
claude mcp add --transport http ai-deskcrew-agentic https://deskcrew.ai/api/mcp
[mcp_servers.ai-deskcrew-agentic] url = "https://deskcrew.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-deskcrew-agentic": {
"type": "remote",
"url": "https://deskcrew.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-deskcrew-agentic --url https://deskcrew.ai/api/mcp --transport streamable-http
mcp_servers:
ai-deskcrew-agentic:
url: "https://deskcrew.ai/api/mcp" {
"mcpServers": {
"ai-deskcrew-agentic": {
"type": "http",
"url": "https://deskcrew.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 57
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://deskcrew.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=deskcrew.ai | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 9 Jul 2026 | 9 Jan 2027 | RSA 2048 | SHA256-RSA | c0db843952603d945a19347d9c52950 |
| SANs: deskcrew.ai | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
DNSSEC insecure
Validation of deskcrew.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| deskcrew.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://deskcrew.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://deskcrew.ai/api/mcp | HTTPS enforced | 301 | https://deskcrew.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
create_purchase_challenge ~128
Begin a purchase. Provide the setup spec (see get_catalog for the schema; businessName, contactEmail and agentPurpose are required). Returns the x402 payment requirements to sign. No money moves and no order is created at this step.
| Name | Type | Req | Description |
|---|---|---|---|
| agentPurpose | string | yes | — |
| businessName | string | yes | — |
| contactEmail | string | yes | — |
| contactName | string | — | — |
| greeting | string | — | — |
| hoursOfCover | string | — | — |
| knowledge | string | — | — |
| notes | string | — | — |
| transferNumber | string | — | — |
No output schema declared.
No examples provided.
get_catalog ~57
Get the DeskCrew.ai agentic catalog: what is for sale (a managed AI phone agent for a business), the exact price and payment rails, the spec schema, and why an agent operating for a call-missing business would buy it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_order_status ~58
Check an order you placed. Provide the orderId and orderKey returned by submit_payment. Returns the fulfilment status: paid, provisioning, live, or cancelled.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | — |
| orderKey | string | yes | — |
No output schema declared.
No examples provided.
submit_payment ~161
Complete a purchase. Provide the same spec plus paymentSignature: the base64 PAYMENT-SIGNATURE header you produced by signing one of the payment requirements with your XRPL wallet (the x402-xrpl package does this). Settlement happens on-ledger before any order is created. Returns your orderId, orderKey and the transaction receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| agentPurpose | string | yes | — |
| businessName | string | yes | — |
| contactEmail | string | yes | — |
| contactName | string | — | — |
| greeting | string | — | — |
| hoursOfCover | string | — | — |
| knowledge | string | — | — |
| notes | string | — | — |
| paymentSignature | string | yes | base64 PAYMENT-SIGNATURE header |
| transferNumber | string | — | — |
No output schema declared.
No examples provided.