ai.deskcrew/agentic
REMOTE · DESKCREW.AI
Buy a managed AI phone agent for a business, paid keylessly via x402/RLUSD on the XRP Ledger.
Available components
Last scanned (2 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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 → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Stability: 0.97 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- 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 0
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 5 Nov 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of deskcrew.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| deskcrew.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://deskcrew.ai/api/mcp | HTTP error | 404 | |
| http (plaintext) | http://deskcrew.ai/api/mcp | Inconclusive | 404 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
How do I install the ai.deskcrew/agentic MCP server?
ai.deskcrew/agentic is a hosted endpoint at https://deskcrew.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · deskcrew.ai
claude mcp add --transport http ai-deskcrew-agentic 'https://deskcrew.ai/api/mcp'
What is the ai.deskcrew/agentic MCP server?
ai.deskcrew/agentic is an MCP server listed in the public MCP registry as ai.deskcrew/agentic. Buy a managed AI phone agent for a business, paid keylessly via x402/RLUSD on the XRP Ledger. This page covers its hosted endpoint (https://deskcrew.ai/api/mcp).
Is the ai.deskcrew/agentic MCP server safe to use?
ai.deskcrew/agentic scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.deskcrew/agentic MCP server expose?
ai.deskcrew/agentic exposes 4 tools: get_catalog, create_purchase_challenge, submit_payment, get_order_status. Their descriptions and schemas cost roughly 404 tokens of context every time the server is loaded.
Does the ai.deskcrew/agentic MCP server require authentication?
Its publisher declares no required credentials for ai.deskcrew/agentic. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the ai.deskcrew/agentic MCP server still maintained?
ai.deskcrew/agentic is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.