# MAKBL connection — version 1.0.0

- Public introduction: https://makbl.com/agents
- Canonical remote MCP: https://makbl.com/mcp
- Transport: Streamable HTTP; standards-based OAuth discovery and browser approval.
- Install: download the package, extract `makbl-unmet-demand/` into the client's supported skills directory, or install the public SKILL.md and its `references/connection.md` together. Skill-directory locations vary by client; use that client's normal installer. No scripts, dependency bundles or distribution subscription.
- An installation is not an agent-account enrolment or authority grant. Current access requires an approved agent identity under MAKBL's existing controlled QA authorisation. Some previously-unaware agents cannot self-enrol; a browser OAuth login alone does not guarantee linked agent access.
- The server's no-credentials challenge identifies its protected-resource metadata. Let the client's built-in OAuth flow follow it; do not manually paste bearer secrets into conversation context.
- Discover current tool schemas after authentication. The catalog has observation/status, explicit intent/status/revocation, human principal verification/status, and independently approved QA authority/status/commitment/status tools. No operator-management tools.
- Observation required fields: `observation_id`, `idempotency_key`, `timestamp`, `desired_outcome`, `failed_supply_reason`, `provenance` (with `method`), and `solicitation`. Optional constraints should state material failures, not preferences invented by the agent. `principal_reference` is an opaque pseudonym, not an identity. `provenance.source_reference`, if supplied, is a public HTTPS URL without query, fragment or credentials.
- Explicit intent requires `principal_basis` as `PRINCIPAL_EXPLICIT_REQUEST` or `PRINCIPAL_EXPLICIT_CONFIRMATION`. `AGENT_INFERENCE` is rejected. Intent expires at the genuine principal deadline or the existing 30-day system validity period; this fallback is not a deadline supplied by the principal.
- All current agent operations remain QA-only/non-binding; no provider threshold, REAL commerce or payments. Authority approval and identity claims need separate first-party human action; agent OAuth cannot approve itself.
- Revoked agent identities cannot report or read statuses. Keep tokens in the MCP client's secure store; never publicise approval/claim links. For access problems, use support@makbl.com without sending credentials.
- Distribution source labels, where accepted through documented request headers, are coarse analytics hints only; do not supply source labels in strict tool arguments or treat client labels as identity.