Skip to Content
AI agentsTechnical details

Technical details

This page describes what the Juhus MCP server implements. It is a statement about Juhus, not a claim about any particular AI client.

Endpoint

https://mcp.juhus.ee/mcp

Protocol contract

Juhus exposes a remote Streamable HTTP MCP endpoint. The connection uses OAuth authorization-server and protected-resource discovery, PKCE S256, and exact resource indicators.

  • Scopes are read (required) and trade (optional).
  • The initial bearer challenge points clients to protected-resource metadata without narrowing the request to read; compatible clients can therefore request both supported scopes and let the user leave optional trade off or enable it in Juhus consent.
  • OAuth clients use Dynamic Client Registration by default. URL-based Client ID Metadata Documents remain supported when Juhus explicitly advertises the capability, with exact client_id self-reference required.
  • Clients with trade scope receive the trading tools in both modern and legacy protocol modes.
  • MCP 2026-07-28 clients use URL-mode elicitation and an input-required retry for browser confirmation. Legacy/stateless clients receive the same review URL with signed confirmationState in an error’s JSON text content and retry the identical tool call after approval. Error results omit structuredContent, preventing clients from validating confirmation metadata as a successful order response.

This contract does not mean Juhus works with every MCP client. Client behaviour varies by plan, workspace policy, platform, and version.

Client support status

Juhus publishes a client as verified only after a live acceptance run passes in that named client. Until then its guide says so plainly. Vendor documentation establishes that a client is eligible for testing, never that Juhus supports it.

TroubleshootingFees