mcp server
agentic
Buy a managed AI phone agent for a business, paid keylessly via x402/RLUSD on the XRP Ledger.
Description as published by the maintainer. Source
- version 1.0.0
- archived
archived — The linked repository returns 404. It was deleted, renamed or made private.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
create_purchase_challenge(notes, greeting, knowledge, contactName, agentPurpose, businessName, contactEmail, hoursOfCover, transferNumber)- 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. Required: businessName, contactEmail, agentPurpose.
get_catalog- 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.
get_order_status(orderId, orderKey)- Check an order you placed. Provide the orderId and orderKey returned by submit_payment. Returns the fulfilment status: paid, provisioning, live, or cancelled. Required: orderId, orderKey.
submit_payment(notes, greeting, knowledge, contactName, agentPurpose, businessName, contactEmail, hoursOfCover, transferNumber, paymentSignature)- 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. Required: paymentSignature, businessName, contactEmail, agentPurpose.
Last successful function declaration observed on . Source: https://deskcrew.ai/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://deskcrew.ai/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-30 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-30 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | not_found | GitHub returned 404 for the repository the maintainer listed. The project was deleted, renamed or made private, so the listing points at nothing. | as of fetch | GitHub | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | deskcrew.ai | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | deskcrew.ai |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json