xytara 3.9.11 → 3.9.13

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/RELEASE_NOTES.md +5 -5
  2. package/package.json +1 -1
package/RELEASE_NOTES.md CHANGED
@@ -1,6 +1,6 @@
1
- `xytara` 3.9.11 adds the stateless MCP protocol (2026-07-28) to the pay-per-call MCP server and makes provider-tool payments catalogable by the CDP Bazaar.
1
+ `xytara` 3.9.13 makes each MCP tool's discovery listing point at the always-paid form of the endpoint. It also gives clearer directions to callers that leave out `task_ref`, and makes the daily buyer-journey report more exact.
2
2
 
3
- - **MCP 2026-07-28 (stateless, SEP-2575)** at `https://mcp.naxytra.com/mcp`: `server/discover` answers with the supported versions (`2026-07-28` first, then the handshake versions back to `2024-11-05`), the server capabilities, instructions and `serverInfo` (in result `_meta`, and top-level for SDKs built against the SEP as accepted). Requests that carry `io.modelcontextprotocol/protocolVersion` in `_meta` work without `initialize`, and the client is identified from `_meta` clientInfo. An unsupported version declared that way gets `-32022` with `supported` / `requested` and HTTP 400; an unknown method on a stateless request gets HTTP 404. Handshake clients (`initialize`) behave exactly as before, and the `MCP-Protocol-Version` header alone never changes that. CORS allows the `Mcp-Method` and `Mcp-Name` headers.
4
- - **Bazaar for provider tools:** a paid call to an independent provider's tool now reaches the payment facilitator with the server's resource (priced at the offer the buyer paid) and discovery extension when the buyer's client leaves them out, as own tools already did. The signed authorization is unchanged.
5
- - The daily buyer-journey report names the method and route for failures that carry no other detail, such as a runtime route that does not exist.
6
- - No change to pricing, payment, routing, the provider ledger or the client package.
3
+ - **Listed URL answers with the price:** the payment resource catalogued by x402 discovery (the CDP Bazaar) is now `https://mcp.naxytra.com/mcp/http402?allowance=off#<tool>` (and `…/mcp?allowance=off#<tool>` for MCP-native calls). Calling the listed URL with its published example answers with the payment challenge (HTTP 402 on the HTTP-402 variant), as other listed sellers' URLs do, never with a free-allowance result. The free allowance on the plain `/mcp` URL is unchanged.
4
+ - **`task_ref` missing:** `POST /x402/commands/execute` without `task_ref` now also returns a request body example (`adapter.mcp.invoke` with `tool_name` and `arguments`), where to find provider tools and prices, and the MCP server as the easier path. Nothing is charged.
5
+ - **Report:** MCP methods such as `tools/call` are no longer clipped to 8 characters in the buyer-event log. Failure details in the daily report name the tool or task they came from.
6
+ - No change to pricing, payment, settlement, routing, the provider ledger or the client package.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "xytara",
3
- "version": "3.9.11",
3
+ "version": "3.9.13",
4
4
  "description": "Client for the hosted naxytra runtime: discover a capability, pay per call with x402 (gasless USDC on Base) or credits, get the deliverable and a signed delivery receipt you can verify offline. The runtime is a hosted service; this package is the client.",
5
5
  "main": "client.js",
6
6
  "exports": {