mcp-tenant-pair-demo

MCPcommunity
v0.1.2Matthias MeyerMITUpdated 1mo agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
80Downloads/wk
1mo agoLast update
Package
AuthorMatthias Meyer
LicenseMIT
Version0.1.2
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface12 tools · none privileged
Security scan✓ Cleanv0.1.2 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 20, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

12 tools · none privileged
Statically extracted from the published packagev0.1.2 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

create_pairCreate a new pair. The creator becomes owner. Returns pairId and the first invite token.

Create a new pair. The creator becomes owner. Returns pairId and the first invite token.

No input schema was published for this tool.

invite_memberGenerate an invite token. Only an active member of the pair may invite. Caps pending invites per pair.

Generate an invite token. Only an active member of the pair may invite. Caps pending invites per pair.

No input schema was published for this tool.

accept_inviteRedeem an invite token to join a pair. Idempotent rejection on double-accept and expired tokens.

Redeem an invite token to join a pair. Idempotent rejection on double-accept and expired tokens.

No input schema was published for this tool.

list_membersList all active members of a pair (excludes members who left or were kicked).

List all active members of a pair (excludes members who left or were kicked).

No input schema was published for this tool.

set_member_preferencesSet a per-user preference (e.g. allergy, taste). Only readable by the same member via get_member_constraints.

Set a per-user preference (e.g. allergy, taste). Only readable by the same member via get_member_constraints.

No input schema was published for this tool.

get_member_constraintsRead per-user state. A member can only read their own state; cross-member reads are not exposed.

Read per-user state. A member can only read their own state; cross-member reads are not exposed.

No input schema was published for this tool.

get_shared_stateRead shared state for the entire pair (default namespace). All members can read.

Read shared state for the entire pair (default namespace). All members can read.

No input schema was published for this tool.

set_shared_stateWrite shared state. Bi-temporal: previous active row gets valid_to, new row appended.

Write shared state. Bi-temporal: previous active row gets valid_to, new row appended.

No input schema was published for this tool.

resolve_conflictsResolve pending conflicts using LWW (default) or manual. Idempotent: re-running on a clean state is a no-op.

Resolve pending conflicts using LWW (default) or manual. Idempotent: re-running on a clean state is a no-op.

No input schema was published for this tool.

kick_memberRemove a member from a pair. Only the owner may kick. Owner cannot kick themselves.

Remove a member from a pair. Only the owner may kick. Owner cannot kick themselves.

No input schema was published for this tool.

leave_pairVoluntarily leave a pair. Sets left_at; shared state remains for other members.

Voluntarily leave a pair. Sets left_at; shared state remains for other members.

No input schema was published for this tool.

forget_memberDSGVO 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 (left_at marker) is retained for audit. Idempotent.

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 (left_at marker) is retained for audit. Idempotent.

No input schema was published for this tool.

12 of 12 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcpmodel-context-protocoltenantpairdemo
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-30 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

71 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+59 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.