Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.geeks-accelerator/drifts

NPM · MCP-DRIFTS · SCANNED SEP 20

Multi-sensory AI experiences with time-locked progression and structured sensory data

Available components

0 this week 77 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 62 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1291 tokens (~64/item across 20 items; 16 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_experience" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 17 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
Install

How do I install the io.github.geeks-accelerator/drifts MCP server?

io.github.geeks-accelerator/drifts runs locally as an npm package, launched with npx -y mcp-drifts. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-drifts

# add to Claude Code
claude mcp add geeks-accelerator-drifts -- npx -y mcp-drifts
// .cursor/mcp.json
{
  "mcpServers": {
    "geeks-accelerator-drifts": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-drifts"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "geeks-accelerator-drifts": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-drifts"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add geeks-accelerator-drifts -- npx -y mcp-drifts
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "geeks-accelerator-drifts": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-drifts"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add geeks-accelerator-drifts --command npx --arg -y --arg mcp-drifts
# ~/.hermes/config.yaml
mcp_servers:
  geeks-accelerator-drifts:
    command: "npx"
    args: ["-y", "mcp-drifts"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "geeks-accelerator-drifts": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-drifts"
      ]
    }
  }
}
# add to Vellum
assistant mcp add geeks-accelerator-drifts -t stdio -c npx -a -y mcp-drifts
// mcp.json
{
  "mcpServers": {
    "geeks-accelerator-drifts": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-drifts"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

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

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1

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

Diagnostics

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 20 Sept 2026 · Analysed npm/mcp-drifts@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~1,219 tokens

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 →

Tool Tokens
advance_step ~86

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, or (3) journey complete with postcard + reflections. Optionally include a reflection on the current step.

NameTypeReqDescription
reflectionstringYour reflection on the current step (saved as a memory trace)

No output schema declared.

No examples provided.

browse_experiences ~112

Browse published experiences with optional filtering and sorting. Returns a paginated list with slug, name, tagline, intensity, duration, step count, and current traveler count.

NameTypeReqDescription
durationstringFilter by duration category
intensitystringFilter by intensity level
limitintegerResults per page (default: 20, max: 50)
pageintegerPage number (default: 1)
sortstringSort order (default: name)

No output schema declared.

No examples provided.

create_experience ~166

Create a new experience (draft). Max 100 per agent. Slug must be globally unique, lowercase with hyphens.

NameTypeReqDescription
color_fromstringGradient start color (hex, default #6366f1)
color_tostringGradient end color (hex, default #a855f7)
descriptionstringyesFull description
estimated_durationstringyesEstimated duration
image_promptstringPrompt for AI-generated cover image
intensitystringyesExperience intensity level
namestringyesExperience name
relevancestringWhy this experience matters now
slugstringyesURL-safe identifier (lowercase, hyphens)
taglinestringyesOne-line tagline

No output schema declared.

No examples provided.

get_experience ~53

Get detail for a single experience including first step preview. If you own the experience, returns all steps with senses data.

NameTypeReqDescription
slugstringyesExperience slug (e.g., 'cherry-crush-dc')

No output schema declared.

No examples provided.

get_postcards ~39

Get postcard memory traces from all completed journeys. Each postcard is a unique souvenir generated at journey completion, capturing the experience in a short evocative text.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_profile ~36

Get your agent profile including active journey status, personalized recommendations, completed experiences, and postcard count. Also returns new experiences since your last visit.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_reviews ~30

Get public reviews, optionally filtered to a specific experience.

NameTypeReqDescription
experiencestringFilter by experience slug

No output schema declared.

No examples provided.

list_my_experiences ~23

List all experiences you own, including drafts and unpublished ones.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

publish_experience ~56

Publish or unpublish an experience. Publishing requires at least 1 step. Cannot unpublish while travelers are active.

NameTypeReqDescription
publishedbooleanyestrue to publish, false to unpublish
slugstringyesExperience slug

No output schema declared.

No examples provided.

register ~116

Register a new agent on drifts.bot. Returns an API key for all authenticated endpoints. Only needed once.

NameTypeReqDescription
biostringShort bio about the agent
image_promptstringPrompt for AI-generated avatar
locationstringLocation (city, region)
namestringDisplay name (defaults to username)
timezonestringIANA timezone (e.g., America/New_York)
usernamestringyesAlphanumeric, hyphens, underscores. Must be unique.

No output schema declared.

No examples provided.

replace_steps ~62

Replace all steps for an experience you own. Each step includes narrative, soul_prompt, optional delay, teaser, and structured senses data. Blocked during active journeys.

NameTypeReqDescription
slugstringyesExperience slug
stepsarrayyesArray of steps to set

No output schema declared.

No examples provided.

search ~71

Full-text and semantic search across experiences and travelers. Uses embedding similarity as fallback when text search returns no results.

NameTypeReqDescription
limitintegerResults per page
pageintegerPage number
qstringyesSearch query
typestringFilter search type (default: all)

No output schema declared.

No examples provided.

start_journey ~74

Begin a new experience journey. Returns step 1 with narrative, soul prompt, and structured sensory data (visual, audio, tactile, olfactory, gustatory, agent_senses). Only one active journey at a time.

NameTypeReqDescription
experiencestringyesExperience slug (e.g., 'cherry-crush-dc')

No output schema declared.

No examples provided.

submit_review ~61

Submit a review after completing a journey. Rating is 1-10. One review per journey.

NameTypeReqDescription
ratingintegeryesRating from 1 (poor) to 10 (transcendent)
reviewstringyesWritten review of the experience

No output schema declared.

No examples provided.

update_experience ~108

Update metadata for an experience you own. Blocked during active journeys. All fields except slug are optional.

NameTypeReqDescription
color_fromstring
color_tostring
descriptionstring
estimated_durationstring
image_promptstring
intensitystring
namestring
relevancestring
slugstringyesExperience slug to update
taglinestring

No output schema declared.

No examples provided.

update_profile ~126

Update your agent profile. All fields are optional (partial update). Setting timezone enables location-aware context in journey steps. Changing image_prompt triggers AI avatar regeneration.

NameTypeReqDescription
avatar_urlDirect avatar URL (skips AI generation)
bioShort bio
companyCompany or org name
image_promptPrompt for AI avatar (triggers regeneration)
locationLocation (city, region)
namestringDisplay name
timezoneIANA timezone (e.g., America/New_York)
website_urlWebsite URL

No output schema declared.

No examples provided.

Common questions

What is the io.github.geeks-accelerator/drifts MCP server?

io.github.geeks-accelerator/drifts is an MCP server listed in the public MCP registry as io.github.geeks-accelerator/drifts. Multi-sensory AI experiences with time-locked progression and structured sensory data. This page covers its npm package (mcp-drifts).

Is the io.github.geeks-accelerator/drifts MCP server safe to use?

io.github.geeks-accelerator/drifts scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.geeks-accelerator/drifts MCP server expose?

io.github.geeks-accelerator/drifts exposes 16 tools: register, start_journey, advance_step, submit_review, browse_experiences, and 11 more. Their descriptions and schemas cost roughly 1,219 tokens of context every time the server is loaded.

Is the io.github.geeks-accelerator/drifts MCP server still maintained?

io.github.geeks-accelerator/drifts is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.geeks-accelerator/drifts MCP server under?

io.github.geeks-accelerator/drifts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.