# Okam (remote · api.okam.no)

Build a Norwegian restaurant's own ordering site on Okam. Call kit_learn first. No sign-in to build.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.okam.no`: 83/100 (this document), [markdown](https://verifymcp.io/servers/okam-as-okam/api.md), [page](https://verifymcp.io/servers/okam-as-okam/api)

## Channel facts

- Endpoint: `https://api.okam.no/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 92/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2516 tokens (~69/item across 36 items; 19 tools + 17 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (63% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Okam MCP server?

Okam is a hosted endpoint at https://api.okam.no/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http okam-as-okam 'https://api.okam.no/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "okam-as-okam": {
      "url": "https://api.okam.no/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "okam-as-okam": {
      "type": "http",
      "url": "https://api.okam.no/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.okam-as-okam]
url = "https://api.okam.no/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "okam-as-okam": {
      "type": "remote",
      "url": "https://api.okam.no/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add okam-as-okam --url 'https://api.okam.no/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  okam-as-okam:
    url: "https://api.okam.no/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "okam-as-okam": {
      "Transport": "http",
      "Url": "https://api.okam.no/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add okam-as-okam -t streamable-http -u 'https://api.okam.no/mcp'
```

### Other

```json
{
  "mcpServers": {
    "okam-as-okam": {
      "type": "http",
      "url": "https://api.okam.no/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +1)

- [cosmetic] “storefront_connect” reworded the description of “origin”

### 2026-11-03 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “kit_learn” rewrote its description, which is the text the model reads

### 2026-10-31 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 80, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (19)

### `cart_update_item` (~102 tokens)

Update cart line

Update quantity, notes, or selected options on an existing cart line item. Quantity <= 0 removes the item.

Input parameters:

- `lineItemId` (string, required): Line item id from cart_get.
- `notes` (string): Optional replacement notes.
- `quantity` (integer, required): New quantity. Use 0 to remove.
- `selectedOptionIds` (array): Optional replacement selected product option ids as GUID strings.
- `storeId` (integer, required): Okam store id.

Output parameters:

- `cart` (object|null)

### `store_list` (~48 tokens)

List stores

List stores available to the current user. Optional longitude and latitude improve distance sorting.

Input parameters:

- `latitude` (string): Optional latitude for distance sorting.
- `longitude` (string): Optional longitude for distance sorting.

### `storefront_verify_result` (~204 tokens)

Read a verify run: what passed, what to fix

Store key: call after running the verify command, with the runId of that latest run. Pass or fail per check, and whether the server saw the run's sandbox order paid; when green, the go-live list. The CLI's PASS/WAIT/FAIL lines are authoritative: checks that only WAITed (sandbox guest sign-in) are missing here, so a run with no FAIL in the CLI has nothing to fix. While the store is closed the payment checks FAIL; rerun while it is open. If every check FAILed with locator.waitFor: Timeout, no menu item appeared: the server stopped or the origin differs from storefront_connect's; fix it and rerun. The record changes only when verify runs again.

Input parameters:

- `runId` (string): The runId of the latest verify run, as storefront_connect returned and the CLI printed it.
- `storefrontKey` (string): The site's publishable storefront key, the same one given to storefront_connect.

### `storefront_connect` (~245 tokens)

Connect a running site and get its verify command

Store key: call when the site is served from a process that keeps running (background, fixed port) and menu items show at that origin. Use http://localhost:<port>, not 127.0.0.1: the sandbox key allows only localhost. Returns whether the origin is allowed, a runId and the exact verify command; run it as returned while the site runs. Sign-in and every check after it WAIT until the sandbox guest exists: report them, never stub sign-in. If originAllowed is false, read kit_docs_get topic onboarding. Each call starts a new run; use the latest runId. Example: {"storefrontKey":"pk_test_…","origin":"http://localhost:5173"}.

Input parameters:

- `origin` (string): The site's origin or full URL, for example http://localhost:4321 or https://example.no/shop/. A path in it goes into the verify command's --url.
- `path` (string): Optional path the site is served under, for example /sandbox/, when origin has none.
- `storefrontKey` (string): The site's publishable storefront key (pk_test_… or pk_live_…).

### `menu_list` (~108 tokens)

List menu

List categories and products, with each product's allergens, for a store after delivery type has been selected. Delivery type affects product availability and prices. Results come in pages of whole categories; when nextPage is set, call again with that page for more.

Input parameters:

- `deliveryType` (string, required): Selected delivery type. Use values from store_get/store_list.
- `page` (integer): Page number from nextPage; omit for the first page.
- `storeId` (integer, required): Okam store id.

Output parameters:

- `categories` (array|null)
- `deliveryType` (string)
- `nextPage` (integer|null)
- `page` (integer)
- `storeId` (integer)

### `cart_add_item` (~90 tokens)

Add to cart

Add a configured product to the cart. Use product_configure first for required variant option ids.

Input parameters:

- `notes` (string): Optional line item notes.
- `productId` (string, required): Product id from menu_list.
- `quantity` (integer): Quantity to add.
- `selectedOptionIds` (array): Selected product option ids as GUID strings.
- `storeId` (integer, required): Okam store id.

Output parameters:

- `cart` (object|null)

### `checkout_verify` (~71 tokens)

Verify payment

Verify an external payment after the user has completed the returned payment URL. Provider is vipps or dintero.

Input parameters:

- `paymentReference` (string, required): Vipps orderId or Dintero session/payment transaction id returned by checkout_start.
- `provider` (string, required): Payment provider: vipps or dintero.

Output parameters:

- `message` (string|null)
- `order` (object|null)
- `paymentReference` (string|null)
- `provider` (string|null)
- `status` (string|null)

### `kit_docs_get` (~140 tokens)

Read one Storefront Kit topic or reference block

Public: with topic, that topic as Markdown; read assemble-a-shop, world-class-ordering-ux, verify-contract and the-return-page before building, the others when the steps name them. With block: where to read that reference block's source; read it, never install it. Without arguments: the topic and block lists. Read each topic once. Example: {"topic":"world-class-ordering-ux"}.

Input parameters:

- `block` (string): Optional reference block name from kit_learn's blocks, for example menu.
- `topic` (string): Optional topic slug from kit_learn's topics, for example assemble-a-shop or verify-contract.

### `server_info` (~19 tokens)

Server info

Public: basic information about the Okam MCP server.

### `kit_learn` (~178 tokens)

Start here: learn the Okam Storefront Kit

Public: call first whenever you build or change a restaurant's own ordering website or table booking on Okam. Returns the must-nots (the server owns every price, payment is the guest's own act), the build steps, the sandbox key, the topics and, with framework, the scaffold plan. The kit gives logic and outcomes, never a look: design the site from the restaurant's brief. Not for ordering food as a guest or for restaurant admin. Example: {"framework":"vite-react"}. Next: kit_docs_get for the topics the steps name.

Input parameters:

- `framework` (string): Framework for the scaffold plan: next, astro, vite-react or html (read package.json). Pass it on the first call.
- `kitVersion` (string): Optional kit version you were told to use; the current kit is always served.

### `payment_methods_list` (~49 tokens)

List payment methods

List payment methods available for the current cart/user. Saved Stripe cards have ids; Dintero and Vipps are returned as payment types.

Input parameters:

- `storeId` (integer, required): Okam store id.

### `cart_validate` (~27 tokens)

Validate cart

Validate the current cart before checkout.

Input parameters:

- `storeId` (integer, required): Okam store id.

Output parameters:

- `cartIsEmpty` (boolean)
- `deliveryAddressError` (boolean)
- `deliveryMethodError` (boolean)
- `giftcardBalanceTooLow` (boolean)
- `hasErrors` (boolean)
- `itemsOutOfStock` (array|null)
- `minimumPrice` (object|null)
- `paymentTypeError` (boolean)
- `priceDifferError` (boolean)
- `priceTooLowError` (boolean)
- `sameDayAfterHoursOrderNotAllowed` (boolean)
- `storeId` (integer|null)
- `storeIsClosed` (boolean)

### `store_get` (~38 tokens)

Get store

Get store details, including supported delivery types. Choose a delivery type before listing menu prices.

Input parameters:

- `storeId` (integer, required): Okam store id.

Output parameters:

- `store` (object|null)

### `cart_get` (~28 tokens)

Get cart

Get the current cart for a store.

Input parameters:

- `storeId` (integer, required): Okam store id.

Output parameters:

- `cart` (object|null)

### `cart_set_delivery` (~168 tokens)

Set delivery

Set cart delivery type and delivery details. This must be called before listing product prices or adding products to cart.

Input parameters:

- `city` (string): Required for home delivery.
- `comment` (string): Optional order comment.
- `deliveryInstructions` (string): Optional delivery instructions.
- `deliveryType` (string, required): Selected delivery type.
- `fullAddress` (string): Required for home delivery.
- `storeId` (integer, required): Okam store id.
- `tableName` (string): Required for table delivery.
- `tipAmount` (integer|null): Optional tip amount in ore.
- `tipPercent` (integer|null): Optional tip percent, 0-100.
- `useReward` (boolean|null): Whether to use available reward balance.
- `zipCode` (string): Required for home delivery.

Output parameters:

- `cart` (object|null)

### `delivery_availability_check` (~68 tokens)

Check delivery address

Check whether Wolt delivery can deliver to an address and return the delivery price if available.

Input parameters:

- `city` (string, required): City.
- `fullAddress` (string, required): Street address.
- `storeId` (integer, required): Okam store id.
- `zipCode` (string, required): Postal code.

Output parameters:

- `canDeliver` (boolean)
- `error` (string|null)
- `price` (object|null)

### `product_configure` (~57 tokens)

Configure product

Get all variants, option ids and allergens for configuring a product before adding it to cart.

Input parameters:

- `deliveryType` (string, required): Selected delivery type. Delivery type affects product price.
- `productId` (string, required): Product id from menu_list.

Output parameters:

- `deliveryType` (string)
- `product` (object|null)
- `storeId` (integer|null)

### `checkout_start` (~90 tokens)

Start checkout

Start checkout with Dintero or DinteroVipps. Returns a Dintero payment URL and reference; the guest approves the payment on Dintero's page. A zero-amount cart completes immediately. An unchanged cart gets the same payment link back.

Input parameters:

- `paymentType` (string, required): Dintero or DinteroVipps.
- `storeId` (integer, required): Okam store id.

Output parameters:

- `cart` (object|null)
- `clientSecret` (string|null)
- `message` (string|null)
- `order` (object|null)
- `paymentReference` (string|null)
- `paymentType` (string)
- `paymentUrl` (string|null)
- `provider` (string|null)
- `status` (string|null)
- `validation` (object|null)

### `cart_remove_item` (~42 tokens)

Remove cart line

Remove a cart line item.

Input parameters:

- `lineItemId` (string, required): Line item id from cart_get.
- `storeId` (integer, required): Okam store id.

Output parameters:

- `cart` (object|null)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/okam-as-okam/api#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Okam MCP server?

Okam is an MCP server listed in the public MCP registry as io.github.Okam-AS/okam. Build a Norwegian restaurant's own ordering site on Okam. Call kit_learn first. No sign-in to build. This page covers its hosted endpoint (https://api.okam.no/mcp).

### Is the Okam MCP server safe to use?

Okam scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Okam MCP server expose?

Okam exposes 19 tools: cart_update_item, store_list, storefront_verify_result, storefront_connect, menu_list, and 14 more. Their descriptions and schemas cost roughly 1,772 tokens of context every time the server is loaded.

### Does the Okam MCP server require authentication?

Yes. Okam asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Okam MCP server still maintained?

Okam is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.okam.no/mcp
- Website: https://okam.no/en/for-developers
- Changelog RSS feed: https://verifymcp.io/servers/okam-as-okam/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/okam-as-okam/api.json
- HTML version of this page: https://verifymcp.io/servers/okam-as-okam/api