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.

Obsidian Turbocharged

NPM · OBSIDIAN-TC · SCANNED SEP 21

Model-agnostic, agent-ready Obsidian MCP server with RBAC, SLSA provenance, and native search.

Available components

npm · obsidian-tc 50
+11 this week 50 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 Security99
  • 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
  • 26 of 82 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to The-40-Thieves/obsidian-tc). View diagnostics → Pass
  • Clear OSI-approved license (AGPL-3.0-only).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
  • Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Tool Safety0
  • Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
  • Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the Obsidian Turbocharged MCP server?

Obsidian Turbocharged runs locally as an npm package, launched with npx -y obsidian-tc. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · obsidian-tc

# add to Claude Code
claude mcp add the-40-thieves-obsidian-tc -- npx -y obsidian-tc
// .cursor/mcp.json
{
  "mcpServers": {
    "the-40-thieves-obsidian-tc": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-tc"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "the-40-thieves-obsidian-tc": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-tc"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add the-40-thieves-obsidian-tc -- npx -y obsidian-tc
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "the-40-thieves-obsidian-tc": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "obsidian-tc"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add the-40-thieves-obsidian-tc --command npx --arg -y --arg obsidian-tc
# ~/.hermes/config.yaml
mcp_servers:
  the-40-thieves-obsidian-tc:
    command: "npx"
    args: ["-y", "obsidian-tc"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "the-40-thieves-obsidian-tc": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "obsidian-tc"
      ]
    }
  }
}
# add to Vellum
assistant mcp add the-40-thieves-obsidian-tc -t stdio -c npx -a -y obsidian-tc
// mcp.json
{
  "mcpServers": {
    "the-40-thieves-obsidian-tc": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-tc"
      ]
    }
  }
}
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.

  • 21 Sept 26 0
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 1.31.1 → 1.31.2 functional
  • 20 Sept 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.88 ▲ functional
  • 19 Sept 26 −11
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 0.88 → unverified ▼ functional
    • Package version: 1.30.1 → 1.31.1 functional
    • Package version: 1.30.1 → 1.31.0 functional
  • 15 Sept 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.88 ▲ functional
  • 14 Sept 26 +4
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: 0.88 → unverified ▼ functional
    • Package version: 1.30.0 → 1.30.1 functional
  • 13 Sept 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 1.28.4 → 1.30.0 functional
    • Package version: 1.28.4 → 1.29.0 functional
  • 6 Sept 26 0
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 0.88 → unverified ▼ functional
    • Package version: 1.27.0 → 1.28.4 functional
    • Package version: 1.27.0 → 1.28.3 functional
    • Package version: 1.27.0 → 1.28.2 functional
    • Package version: 1.27.0 → 1.28.1 functional
    • Package version: 1.27.0 → 1.28.0 functional
  • 5 Sept 26 0
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess. functional
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 21 Sept 2026 · Analysed npm/obsidian-tc@1.31.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo The-40-Thieves/obsidian-tc
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/The-40-Thieves/obsidian-tc/.github/workflows/publish.yml@refs/tags/v1.31.2
Rekor log index 2904714129
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:f767a9f2cc6f87b031c3c2396f157a0b96e909e69c540ca1997dd7eb844ec3f99e76ed1f433b26afb868f63c1f0c50c7dd99fcfe7951cd6e9de618c0b

Background: How many MCP packages publish verified provenance →

Dependencies 82 packages
Packages resolved 82
Deprecated 2
Stale 25
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the Obsidian Turbocharged MCP server?

Obsidian Turbocharged is an MCP server listed in the public MCP registry as io.github.The-40-Thieves/obsidian-tc. Model-agnostic, agent-ready Obsidian MCP server with RBAC, SLSA provenance, and native search. This page covers its npm package (obsidian-tc).

Is the Obsidian Turbocharged MCP server safe to use?

Obsidian Turbocharged scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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.

Is the Obsidian Turbocharged MCP server still maintained?

Obsidian Turbocharged is still listed as active in the MCP registry. We last reached this channel on 21 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 Obsidian Turbocharged MCP server under?

Obsidian Turbocharged declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.