# mcp-tenant-pair-demo

Reference MCP server demonstrating mcp-tenant-pair (12 tools, stdio): pair lifecycle + bi-temporal shared state + DSGVO Art.17 erasure

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.1.2
- **Author:** Matthias Meyer
- **License:** MIT
- **npm:** mcp-tenant-pair-demo
- **Source:** https://github.com/studiomeyer-io/mcp-tenant-pair
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 3 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-30T21:01:08.957Z
- **Version scanned:** 0.1.2
- **CVEs:** none found by OSV at scan time

## Tools

12 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `create_pair` — Create a new pair. The creator becomes owner. Returns pairId and the first invite token.
- `invite_member` — Generate an invite token. Only an active member of the pair may invite. Caps pending invites per pair.
- `accept_invite` — Redeem an invite token to join a pair. Idempotent rejection on double-accept and expired tokens.
- `list_members` — List all active members of a pair (excludes members who left or were kicked).
- `set_member_preferences` — Set a per-user preference (e.g. allergy, taste). Only readable by the same member via get_member_constraints.
- `get_member_constraints` — Read per-user state. A member can only read their own state; cross-member reads are not exposed.
- `get_shared_state` — Read shared state for the entire pair (default namespace). All members can read.
- `set_shared_state` — Write shared state. Bi-temporal: previous active row gets valid_to, new row appended.
- `resolve_conflicts` — Resolve pending conflicts using LWW (default) or manual. Idempotent: re-running on a clean state is a no-op.
- `kick_member` — Remove a member from a pair. Only the owner may kick. Owner cannot kick themselves.
- `leave_pair` — Voluntarily leave a pair. Sets left_at; shared state remains for other members.
- `forget_member` — DSGVO Art. 17 right-to-erasure: hard-delete the member's per-user state (allergies, dietary preferences, etc.) and null their display name. The membership trace

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-tenant-pair-demo\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"mcp-tenant-pair-demo\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/mcp-tenant-pair-demo
- Install plan: https://forgeregistry.com/api/v1/packages/mcp-tenant-pair-demo/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/mcp-tenant-pair-demo
- HTML page: https://forgeregistry.com/registry/mcp-tenant-pair-demo
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.