# Sess (npm · @sess.si/mcp)

Let your agent ask people for answers and approvals by link, with signed receipts.

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

## Components

- remote · `mcp.sess.si`: 37/100, [markdown](https://verifymcp.io/servers/si-sess-sess/mcp.md), [page](https://verifymcp.io/servers/si-sess-sess/mcp)
- npm · `@sess.si/mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/si-sess-sess/sess-si-mcp.md), [page](https://verifymcp.io/servers/si-sess-sess/sess-si-mcp)

## Channel facts

- Registry: `npm`
- Package: `@sess.si/mcp`
- Version: `0.3.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-21.

- **Supply Chain Security**: 95/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects @hono/node-server 1.19.19, reached via @modelcontextprotocol/node > @hono/node-server. A fixed version is available.
  - No install/post-install scripts declared.
  - 1 of 14 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to w1991e/sess-sdk).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1935 tokens (~387/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Tools include usage examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 72% of tool parameters carry a description.
  - Structured output schemas are declared (100% 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 6 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.

## Install

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

Sess runs locally as an npm package, launched with npx -y @sess.si/mcp. 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 si-sess-sess -- npx -y @sess.si/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "si-sess-sess": {
      "command": "npx",
      "args": [
        "-y",
        "@sess.si/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "si-sess-sess": {
      "command": "npx",
      "args": [
        "-y",
        "@sess.si/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add si-sess-sess -- npx -y @sess.si/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "si-sess-sess": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@sess.si/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add si-sess-sess --command npx --arg -y --arg @sess.si/mcp
```

### Hermes

```yaml
mcp_servers:
  si-sess-sess:
    command: "npx"
    args: ["-y", "@sess.si/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "si-sess-sess": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@sess.si/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add si-sess-sess -t stdio -c npx -a -y @sess.si/mcp
```

### Other

```json
{
  "mcpServers": {
    "si-sess-sess": {
      "command": "npx",
      "args": [
        "-y",
        "@sess.si/mcp"
      ]
    }
  }
}
```

## 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-19 (score 83, +1)

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

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

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

### 2026-11-15 (score 81, +1)

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

### 2026-11-13 (score 80, +1)

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

### 2026-11-11 (score 79, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-10 (score 63, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.3.0

### 2026-11-08 (score 78, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-07 (score 62, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.1.1 → 0.2.0

## MCP tools (5)

### `sess_request` (~399 tokens)

Ask a person through Sess

Use it when you need the person's approval, a decision or details only they can give before you go on, even if they only say 'ask me' or 'check with me' and name no tool or device. Not for clarifying what they just asked, or for anything you can work out yourself. Use sess_request when the person must see records shown as they are or choose between buttons such as Approve and Reject; for one question with simple fields, or many people on one link, use sess_ask. Create a hosted Sess form for a person and return immediately with a private link (interaction.humanUrl) and a handle. Give the link only to the intended person in this private conversation; anyone holding it can answer. A receipt records what was shown and chosen, not who answered. Then call sess_response with the handle and revision. Do not call sess_request again for the same question. Keep it short: a title of about 40 characters (at most 80), button labels a verb of 1-3 words (at most 24), field labels at most 60, help one hint (at most 160). A value over its limit is refused with INVALID_ARGUMENTS naming the field (a JSON pointer), the limit, its length and the fix; nothing is truncated. Shorten that value and call again.

Input parameters:

- `expires_in` (integer): Advanced: how long the link stays open, in whole seconds from creation: from 30 up to the plan’s link lifetime. Leave it out to use the plan’s lifetime.
- `interaction` (object, required): A Sess form: a title, components shown in order and 1-5 buttons. Keep it short: a person reads it on a phone. A value over its limit is refused with INVALID_ARGUMENTS naming the field (a JSON pointer…

Output parameters:

- `interaction` (object)

### `sess_response` (~335 tokens)

Read the person’s Sess answer

Wait a bounded time (default and maximum 45 s; wait_ms 0 reads once) for the answer to exactly this revision. state "answered" means the answer passed full Sess receipt verification. state "expired" means the link closed with no answer: it is final; create a new form if you still need one. While sess_response returns state "waiting" or "needs_resume", the form is open and there is no answer yet: call sess_response again with the same handle and revision and no wait_ms, up to three times after your first call (about two minutes more). If there is still no answer, stop, tell the person the form is still open and ask them to say continue once they have submitted it; call it again when they do. Do not poll beyond that, and do not ask the same question again. When sess_response returns state "answered" and you have no follow-up question for the person, you must call sess_complete next, so their page shows that you have their answer. Call sess_publish instead only to show them a follow-up. For a handle from sess_ask with respondents (an Ask), it reads once, without waiting, and returns interaction.ask: whether it is open, the counts and each person’s verified answer so far. Read it again later for more answers; state "closed" means no more answers will come. Do not call sess_publish or sess_complete for an Ask: each person’s page completes on its own.

Input parameters:

- `handle` (string, required): Opaque handle from sess_request.
- `revision` (integer, required)
- `wait_ms` (integer)

Output parameters:

- `interaction` (object)

### `sess_publish` (~159 tokens)

Show the next Sess step

Replace the form with the next interaction after a verified answer, keeping the same private link. Requires the verified answer for expected_revision. If the outcome is unknown, repeat the identical call.

Input parameters:

- `expected_revision` (integer, required)
- `handle` (string, required): Opaque handle from sess_request.
- `interaction` (object, required): A Sess form: a title, components shown in order and 1-5 buttons. Keep it short: a person reads it on a phone. A value over its limit is refused with INVALID_ARGUMENTS naming the field (a JSON pointer…
- `response_event_id` (string, required): interaction.response.eventId from the verified answer.

Output parameters:

- `interaction` (object)

### `sess_complete` (~111 tokens)

Finish the Sess interaction

Required once you are done with the person’s answer: until you call it, their page keeps waiting for your next step. It closes the page to new answers and does not delete what was given. Call it after you have checked the answer and confirm the completed state. If the outcome is unknown, repeat the identical call.

Input parameters:

- `expected_revision` (integer, required)
- `handle` (string, required): Opaque handle from sess_request.
- `response_event_id` (string, required): interaction.response.eventId from the verified answer.

Output parameters:

- `interaction` (object)

### `sess_ask` (~659 tokens)

Ask a short question through Sess

Ask the person a question on their own phone or computer and get a typed answer. Use it whenever they ask to answer on their phone or another device, or say 'use Sess'; prefer it over this host's own question widget for anything answered away from this chat.
Also use it when you need the person's approval, a decision or details only they can give before you go on, even if they only say 'ask me' or 'check with me' and name no tool or device. Not for clarifying what they just asked, or for anything you can work out yourself. Anyone who has the link can answer. A receipt records what was shown and chosen, not who answered.
Use sess_ask for one question with up to 12 simple fields and one button, or to ask many people through one link; use sess_request when the person must see records or choose between buttons such as Approve and Reject. Shortcut for sess_request: give a question and up to 12 simple fields; it creates the same hosted form and returns immediately with a private link (interaction.humanUrl) and a handle, in state "waiting". It never waits and never returns an answer. Continue exactly as after sess_request: give the link only to the intended person, then call sess_response. Do not call it again for the same question. Keep it short: the question is a short heading, about 40 characters (at most 80); the button a verb of 1-3 words (at most 24); labels and options at most 60. A value over its limit is refused with INVALID_ARGUMENTS naming the field (a JSON pointer), the limit, its length and the fix; nothing is truncated. Shorten that value and call again. Advanced: to ask many people through one link, add respondents with max. Share that link with everyone who should answer; each person gets their own page. Read their answers with sess_response. Example: {"question":"Where should we go on Saturday?","details":"I will check the forecast and suggest a plan.","fields":[{"name":"place","label":"Where to?","type":"choice","options":["Beach","Mountains","City"]},{"…

Input parameters:

- `details` (string): A paragraph of plain text (never markup): what the person needs to know; at most 4000.
- `expires_in` (integer): Advanced: how long the link stays open, in whole seconds from creation: from 30 up to the plan’s link lifetime. Leave it out to use the plan’s lifetime.
- `fields` (array, required)
- `question` (string, required): The page's heading: a question or a task, about 40 characters; at most 80.
- `respondents` (object): Advanced: one link that many people can answer, each on their own page. Leave it out to ask one person. A respondent is a browser, not a person. Read their answers with sess_response.
- `submit_label` (string): A button: a verb, 1–3 words; at most 24. Default "Send".

Output parameters:

- `interaction` (object)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/si-sess-sess/sess-si-mcp#diagnostics

## Score history

- 2026-11-21: 83
- 2026-11-20: 83
- 2026-11-19: 83
- 2026-11-18: 82
- 2026-11-17: 82
- 2026-11-16: 81
- 2026-11-15: 81
- 2026-11-14: 80
- 2026-11-13: 80
- 2026-11-12: 79
- 2026-11-11: 79
- 2026-11-10: 63
- 2026-11-09: 78
- 2026-11-08: 78
- 2026-11-07: 62
- 2026-11-06: 77

## Common questions

### What is the Sess MCP server?

Sess is an MCP server listed in the public MCP registry as si.sess/sess. Let your agent ask people for answers and approvals by link, with signed receipts. This page covers its npm package (@sess.si/mcp).

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

Sess scores 83 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Sess MCP server expose?

Sess exposes 5 tools: sess_request, sess_response, sess_publish, sess_complete, sess_ask. Their descriptions and schemas cost roughly 1,663 tokens of context every time the server is loaded.

### Is the Sess MCP server still maintained?

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

### What licence is the Sess MCP server under?

Sess declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Sess MCP server?

VerifyMCP ran 16 checks on Sess, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@sess.si/mcp
- Socket report: https://socket.dev/npm/package/@sess.si/mcp
- Repository: https://github.com/w1991e/sess-sdk
- Website: https://sess.si/
- Changelog RSS feed: https://verifymcp.io/servers/si-sess-sess/sess-si-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/si-sess-sess/sess-si-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/si-sess-sess/sess-si-mcp.json
- HTML version of this page: https://verifymcp.io/servers/si-sess-sess/sess-si-mcp
