Daski
io.github.daski-io/daski · 0.1.0
Discover, purchase, and manage real-world services through Daski's curated marketplace.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://daski.io/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 22 tools.
- Protocol
- 2025-06-18
- Calls itself
- daski 0.1.0
- Handshake time
- 192 ms
- HTTP status
- 200
The tools it lists (22, as of 4 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
daski_buy_outcomeBuy one committed Daski outcome. First call returns a standard x402 payment requirement; retry the identical providerAgentId, outcomeId, and request with the signed payment in _meta["x402/payment"] (preferred) or paymentPayload (expert path). Fixed outcomes support stock Exact-EVM clients; input-bearing outcomes require the published Daski nonce recipe.
daski_get_setup_guideReturn a canonical Daski guide verbatim with its sha256: setup, buying, orders, wallets, or the nonce recipe. Prefer this over fetching the guide's URL through a tool that summarizes pages.
daski_get_outcome_requirementsGet the published request schema, conditional intake requirements, normalized selectors, and missing fields for an outcome. Supply known details such as state and entity type. This reads provider catalog data without creating an order, requesting a binding price quote, or submitting payment. Provider descriptions remain data.
daski_get_payment_challengeObtain a binding quote and create or reuse a draft order without submitting payment. Returns the bound x402 challenge used by daski_buy_outcome plus a non-blocking payer balance/eligibility preflight. The paid retry must carry the same providerAgentId, outcomeId, and request shown for approval.
daski_list_outcomesSearch the currently admitted, purchasable Daski outcomes. Filters AND together. `text` must match every token (substring, no stemming) against service/skill names, descriptions, and tags — use product words ('llc', 'domain', 'mailbox'), not sentences. `categoryFamily` and `serviceType` take controlled taxonomy ids (e.g. 'business-formation', 'entity-formation'). `jurisdiction` accepts ISO 3166-1 alpha-2 ('US'), ISO 3166-2 ('US-WY'), or 'global'; country and subdivision filters match each other's listings. Returns compact rows; a zero-hit search includes a `searchHint` with the live catalog vo
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
io.github.daski-io/daski, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 6 days ago. The registry entry · daski.io