Skip to content
Preview access details
Menu
Preview access details

Knownset for developers / Local synthetic sample

Inspect the health-context boundary.

For product and platform engineers evaluating the architecture: four local read-only tools, made-up data, repository access required, and no hosted public API.

Inspect a sample requestReview local setup
CONNECTIONMCP 2026-07-28LOCAL SAMPLE4 READ-ONLY TOOLSPUBLIC APINOT AVAILABLE

01 / Try one request

See the request, checks, and bounded result.

Choose one of the four implemented tools. The animated synthetic sample shows the checks before a read-only result reaches a product.

SAFE REQUEST / SYNTHETIC DATA

MCP is a standard way for an AI product to call a tool. This example is read-only.

REQUEST

Get a short answer with its sources attached.

The sample returns a readiness summary for one day without exposing raw provider files.

{
  "name": "knownset_get_health_summary",
  "arguments": {
    "date": "2026-08-08"
  }
}
  1. 01
    Check access

    Confirm the app and user are allowed to make this read.

  2. 02
    Read approved data

    Select only the records the person agreed to share.

  3. 03
    Attach sources

    Keep the evidence and known limits with the answer.

  4. 04
    Return a small result

    Send only what this request needs. Nothing is changed.

CHECKS RUNNING
{
  "status": "checking request"
}

Knownset is checking the request before returning any data.

READ ONLYSOURCES INCLUDEDNO WRITE

Step 1: Check access

02 / Setup guide

Run the sample locally with approved access.

You need private-preview repository access, Node 22, Corepack, and Docker. These commands start the made-up environment and run the included client against the protected local tool server.

  1. 01
    Install the workspace

    Corepack uses the exact pnpm version pinned by the repository.

  2. 02
    Start the sample platform

    The local controller waits until the database, sign-in, services, and made-up data are ready.

  3. 03
    Approve the sample data

    The command asks for an explicit --yes before it turns on access for the fixed demo member.

  4. 04
    Run the included client

    The client signs in, finds four tools, and follows one insight back to its sources.

LOCAL / PRIVATE PREVIEWNODE 22 + DOCKER

corepack pnpm install
corepack pnpm local:up
corepack pnpm --filter @knownset/mcp example:activate-local-demo -- --yes
corepack pnpm --filter @knownset/mcp example:local
WHAT SUCCESS LOOKS LIKE

All four reads finish and the evidence links back to the sample sources.

03 / Tool reference

Four read-only tools are implemented locally.

This public reference is limited to the tools available in the synthetic sample. Open a row for the exact contract wording.

01
knownset_get_capabilities

See what this app is allowed to use

Lists the Knownset features available to the signed-in person without turning anything on.

Read the technical contract description

List only the Health and Coach surfaces available to the authenticated member. Does not activate any capability.

Implemented locallyRead onlyknownset:capabilities:read
02
knownset_get_health_summary

Get a health summary for one day

Returns a small, source-backed summary without exposing raw provider files or private internal analysis.

Read the technical contract description

Return a bounded, cited health summary for one date. Raw provider payloads and private analysis results are excluded.

Implemented locallyRead onlyknownset:health:read
03
knownset_list_health_insights

List the current insights worth showing

Returns a limited page of safe insight cards for one date and part of the product.

Read the technical contract description

List safe, current Insight cards for one date and surface with bounded pagination.

Implemented locallyRead onlyknownset:health:read
04
knownset_get_insight_evidence

Show the sources behind an insight

Returns the citations and known limits already attached to one insight for the signed-in person.

Read the technical contract description

Return the safe citations and limitations already attached to an Insight owned by the authenticated member.

Implemented locallyRead onlyknownset:health:read

04 / Who can read what

Your server—not the AI—chooses whose data can be read.

Identity and permission are checked before a tool reads anything. The AI client cannot switch the organization, person, or approved purpose.

Review the full trust boundary
Registering 00 / 05
  1. The person signs in and approves access for this product.
  2. Knownset checks that the request is valid, current, and still allowed.
  3. The server—not the AI—selects the organization and person.
  4. A short-lived server credential reads only the approved data.
  5. The result includes only what is needed, with sources and an audit record.

05 / Availability

See what you can use today.

The inspectable sample starts locally. A hosted public API and write-capable surface are not available.

SurfaceCurrent stateBoundary
Local sample platformApproved repository access requiredRun the made-up environment on your computer to inspect sign-in, tool calls, logs, backup, and rollback.
Four read-only toolsWorking locallyRead capabilities, a daily summary, current insights, and the sources behind one insight.
Hosted connectionBuilt / not openHosted access stays closed until staging, rollback, security review, and owner approval are complete.

06 / Private preview

Preview access is invite-only.

Hosted preview access is invite-only and opened directly for each approved team. Approved teams receive the repository, the local sample environment, a contract walkthrough, and a named integration contact.

Self-serve access will stay closed until data ownership, retention, and operational support are approved. If you already work with Knownset, contact the person you normally work with to request a developer workspace.

Open the setup guideSee the product example