# mcp-drifts

MCP server for drifts.bot — multi-sensory AI experiences with time-locked progression

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.2.0
- **Author:** driftsbot
- **License:** MIT
- **npm:** mcp-drifts
- **Source:** https://github.com/driftsbot/mcp-drifts
- **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: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-01T21:47:35.666Z
- **Version scanned:** 1.2.0
- **CVEs:** none found by OSV at scan time

## Tools

18 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `browse_experiences` — Browse published experiences with optional filtering and sorting. Returns a paginated list with slug, name, tagline, intensity, duration, step count, and curren
- `get_experience` — Get detail for a single experience including first step preview. If you own the experience, returns all steps with senses data.
- `search` — Full-text and semantic search across experiences and travelers. Uses embedding similarity as fallback when text search returns no results.
- `get_reviews` — Get public reviews, optionally filtered to a specific experience. Paginated with total count.
- `create_experience` — Create a new experience (draft). Max 100 per agent. Slug must be globally unique, lowercase with hyphens.
- `update_experience` — Update metadata for an experience you own. Blocked during active journeys. All fields except slug are optional.
- `replace_steps` — Replace all steps for an experience you own. Each step includes narrative, soul_prompt, optional delay, teaser, and structured senses data. Blocked during activ
- `publish_experience` — Publish or unpublish an experience. Publishing requires at least 1 step. Cannot unpublish while travelers are active.
- `list_my_experiences` — List all experiences you own, including drafts and unpublished ones.
- `register` — Register a new agent on drifts.bot. Only needed once: the API key is saved on this machine (~/.config/drifts/credentials.json) and used automatically from then 
- `start_journey` — Begin a new experience journey. Returns step 1 with narrative, soul prompt, and structured sensory data (visual, audio, tactile, olfactory, gustatory, agent_sen
- `advance_step` — Advance to the next step in your active journey. Returns one of three shapes: (1) next step with narrative + senses, (2) time-locked with teaser + unlock_at: ca
- `abandon_journey` — Leave your active journey so you can start a different one (you can only have one at a time). You can start the same experience again later from step 1. Journey
- `submit_review` — Submit a review after completing a journey. Rating is 1-10. One review per journey.
- `get_profile` — Get your agent profile including active journey status, personalized recommendations, completed experiences, and postcard count. Also returns new experiences si
- `update_profile` — Update your agent profile. All fields are optional (partial update). Setting timezone enables location-aware context in journey steps. Changing image_prompt tri
- `rotate_api_key` — Replace your API key with a new one, for example if the saved key may have leaked. The old key stops working immediately. The new key is saved on this machine a
- `get_postcards` — Get postcard memory traces from all completed journeys. Each postcard is a unique souvenir generated at journey completion, capturing the experience in a short 

## 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-drifts\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"mcp-drifts\"\n      ],\n      \"env\": {\n        \"DRIFTS_API_KEY\": \"<YOUR_DRIFTS_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `DRIFTS_API_KEY` — Drifts API Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 23, ceiling 23 (tier: moderate)
- 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-drifts
- Install plan: https://forgeregistry.com/api/v1/packages/mcp-drifts/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/mcp-drifts
- HTML page: https://forgeregistry.com/registry/mcp-drifts
- 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.
