Okam
REMOTE · API.OKAM.NO
Build a Norwegian restaurant's own ordering site on Okam. Call kit_learn first. No sign-in to build.
Available components
Last scanned (23 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 4 Nov 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2519 tokens (~69/item across 36 items; 19 tools + 17 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (63% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +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.
- 1 Nov 26 0
- 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 security
- 31 Oct 26 +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.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 80
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://api.okam.no/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=okam.no | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 609d17bb23a72c401373f266a5af755b |
| SANs: okam.no, *.okam.no | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.okam.no. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| no. | present | 38032 | 13 | Verified |
| okam.no. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.okam.no/.well-known/oauth-protected-resource", scope="okam:mcp.read okam:mcp.cart okam:mcp.checkout"
Bearer resource_metadata="https://api.okam.no/.well-known/oauth-protected-resource", scope="okam:mcp.read okam:mcp.cart okam:mcp.checkout"Protected resource metadata
| Document | https://api.okam.no/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.okam.no/mcp |
| Authorisation server | https://api.okam.no/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.okam.no/mcp | Verified | 200 | |
| http (plaintext) | http://api.okam.no/mcp | HTTPS enforced | 301 | https://api.okam.no/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cart_add_item Add to cart ~90
Add a configured product to the cart. Use product_configure first for required variant option ids.
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | – | Optional line item notes. |
| productId | string | yes | Product id from menu_list. |
| quantity | integer | – | Quantity to add. |
| selectedOptionIds | array | – | Selected product option ids as GUID strings. |
| storeId | integer | yes | Okam store id. |
| Name | Type | Req | Description |
|---|---|---|---|
| cart | object|null | – | – |
No examples provided.
cart_get Get cart ~28
Get the current cart for a store.
| Name | Type | Req | Description |
|---|---|---|---|
| storeId | integer | yes | Okam store id. |
| Name | Type | Req | Description |
|---|---|---|---|
| cart | object|null | – | – |
No examples provided.
cart_remove_item Remove cart line ~42
Remove a cart line item.
| Name | Type | Req | Description |
|---|---|---|---|
| lineItemId | string | yes | Line item id from cart_get. |
| storeId | integer | yes | Okam store id. |
| Name | Type | Req | Description |
|---|---|---|---|
| cart | object|null | – | – |
No examples provided.
cart_set_delivery Set delivery ~168
Set cart delivery type and delivery details. This must be called before listing product prices or adding products to cart.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Required for home delivery. |
| comment | string | – | Optional order comment. |
| deliveryInstructions | string | – | Optional delivery instructions. |
| deliveryType | string | yes | Selected delivery type. |
| fullAddress | string | – | Required for home delivery. |
| storeId | integer | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| cart | object|null | – | – |
No examples provided.
cart_update_item Update cart line ~102
Update quantity, notes, or selected options on an existing cart line item. Quantity <= 0 removes the item.
| Name | Type | Req | Description |
|---|---|---|---|
| lineItemId | string | yes | Line item id from cart_get. |
| notes | string | – | Optional replacement notes. |
| quantity | integer | yes | New quantity. Use 0 to remove. |
| selectedOptionIds | array | – | Optional replacement selected product option ids as GUID strings. |
| storeId | integer | yes | Okam store id. |
| Name | Type | Req | Description |
|---|---|---|---|
| cart | object|null | – | – |
No examples provided.
cart_validate Validate cart ~27
Validate the current cart before checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| storeId | integer | yes | Okam store id. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No examples provided.
checkout_start Start checkout ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentType | string | yes | Dintero or DinteroVipps. |
| storeId | integer | yes | Okam store id. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No examples provided.
checkout_verify Verify payment ~71
Verify an external payment after the user has completed the returned payment URL. Provider is vipps or dintero.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentReference | string | yes | Vipps orderId or Dintero session/payment transaction id returned by checkout_start. |
| provider | string | yes | Payment provider: vipps or dintero. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string|null | – | – |
| order | object|null | – | – |
| paymentReference | string|null | – | – |
| provider | string|null | – | – |
| status | string|null | – | – |
No examples provided.
delivery_availability_check Check delivery address ~68
Check whether Wolt delivery can deliver to an address and return the delivery price if available.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City. |
| fullAddress | string | yes | Street address. |
| storeId | integer | yes | Okam store id. |
| zipCode | string | yes | Postal code. |
| Name | Type | Req | Description |
|---|---|---|---|
| canDeliver | boolean | – | – |
| error | string|null | – | – |
| price | object|null | – | – |
No examples provided.
kit_docs_get Read one Storefront Kit topic or reference block ~140
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"}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
kit_learn Start here: learn the Okam Storefront Kit ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
menu_list List menu ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deliveryType | string | yes | Selected delivery type. Use values from store_get/store_list. |
| page | integer | – | Page number from nextPage; omit for the first page. |
| storeId | integer | yes | Okam store id. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array|null | – | – |
| deliveryType | string | – | – |
| nextPage | integer|null | – | – |
| page | integer | – | – |
| storeId | integer | – | – |
No examples provided.
payment_methods_list List payment methods ~49
List payment methods available for the current cart/user. Saved Stripe cards have ids; Dintero and Vipps are returned as payment types.
| Name | Type | Req | Description |
|---|---|---|---|
| storeId | integer | yes | Okam store id. |
No output schema declared.
No examples provided.
product_configure Configure product ~57
Get all variants, option ids and allergens for configuring a product before adding it to cart.
| Name | Type | Req | Description |
|---|---|---|---|
| deliveryType | string | yes | Selected delivery type. Delivery type affects product price. |
| productId | string | yes | Product id from menu_list. |
| Name | Type | Req | Description |
|---|---|---|---|
| deliveryType | string | – | – |
| product | object|null | – | – |
| storeId | integer|null | – | – |
No examples provided.
server_info Server info ~19
Public: basic information about the Okam MCP server.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
store_get Get store ~38
Get store details, including supported delivery types. Choose a delivery type before listing menu prices.
| Name | Type | Req | Description |
|---|---|---|---|
| storeId | integer | yes | Okam store id. |
| Name | Type | Req | Description |
|---|---|---|---|
| store | object|null | – | – |
No examples provided.
store_list List stores ~48
List stores available to the current user. Optional longitude and latitude improve distance sorting.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | string | – | Optional latitude for distance sorting. |
| longitude | string | – | Optional longitude for distance sorting. |
No output schema declared.
No examples provided.
storefront_connect Connect a running site and get its verify command ~248
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"}.
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | – | The site's origin or full URL, for example http://localhost:4321 or https://test.okam.no/sandbox/. 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_…). |
No output schema declared.
No examples provided.
storefront_verify_result Read a verify run: what passed, what to fix ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · api.okam.no
claude mcp add --transport http okam-as-okam 'https://api.okam.no/mcp'
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 82 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,775 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.