# io.github.zachhannum/obelisk (npm · obelisk-mcp)

Comment on a passage of an Obsidian note, and propose suggested edits.

- Trust score: 89/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `obelisk-mcp`: 89/100 (this document), [markdown](https://verifymcp.io/servers/zachhannum-obelisk/obelisk-mcp.md), [page](https://verifymcp.io/servers/zachhannum-obelisk/obelisk-mcp)

## Channel facts

- Registry: `npm`
- Package: `obelisk-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to zachhannum/obelisk).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 886 tokens (~221/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.zachhannum/obelisk MCP server?

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

### Claude

```bash
claude mcp add zachhannum-obelisk -- npx -y obelisk-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "zachhannum-obelisk": {
      "command": "npx",
      "args": [
        "-y",
        "obelisk-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "zachhannum-obelisk": {
      "command": "npx",
      "args": [
        "-y",
        "obelisk-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add zachhannum-obelisk -- npx -y obelisk-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zachhannum-obelisk": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "obelisk-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add zachhannum-obelisk --command npx --arg -y --arg obelisk-mcp
```

### Hermes

```yaml
mcp_servers:
  zachhannum-obelisk:
    command: "npx"
    args: ["-y", "obelisk-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "zachhannum-obelisk": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "obelisk-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add zachhannum-obelisk -t stdio -c npx -a -y obelisk-mcp
```

### Other

```json
{
  "mcpServers": {
    "zachhannum-obelisk": {
      "command": "npx",
      "args": [
        "-y",
        "obelisk-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 89, +1)

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

### 2026-09-19 (score 88, +1)

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

### 2026-09-17 (score 87, +1)

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

### 2026-09-14 (score 86, +1)

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

### 2026-09-12 (score 85, +1)

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

### 2026-09-10 (score 84, +1)

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

### 2026-09-08 (score 83, +1)

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

### 2026-09-06 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

## MCP tools (4)

### `obelisk_list` (~197 tokens)

List a note's comments

Every Obelisk comment on a note, with the passage each one is anchored to, plus the note body with line numbers.

Read this before commenting: the `quote` you pass to obelisk_comment has to be copied out of this body character for character, and the line numbers here are what `nearLine` refers to.

It is also the first half of the other flow — a person leaves a comment asking for something, you read it here, make the edit yourself, and call obelisk_resolve.

Input parameters:

- `includeBody` (boolean): Include the line-numbered note body. Defaults to true; turn it off only if you already have the text.
- `note` (string, required): Path to the note, relative to the vault root or to the working directory. Absolute paths reach a note in another vault. `.md` optional.
- `openOnly` (boolean): Only unresolved comments. Defaults to false.

### `obelisk_comment` (~362 tokens)

Comment on a passage

Leave a comment on one passage of a note. It appears in the reader's Obsidian sidebar, badged as coming from an agent.

\`quote` is the anchor and must appear in the note verbatim — the same characters, punctuation, capitalization and spacing. Copy it from obelisk_list; do not retype it or tidy it up. There is no way to pass a line or column, and you should not try to count them: the quote is the anchor and the tool does the arithmetic. If the quote is not found, or is found more than once, nothing is written and you are told which.

\`body` is markdown. To propose a specific rewrite, put it in a ```suggestion fenced block inside the body — its contents replace exactly the quoted passage when the reader clicks Apply, so a comment can explain itself and propose the change at once.

Input parameters:

- `body` (string, required): The comment, as markdown. A ```suggestion block inside it proposes a replacement for the quoted passage.
- `model` (string): Recorded on the comment as the model that wrote it.
- `nearLine` (integer): Only when the quote appears more than once: the body line number, as printed by obelisk_list, of the occurrence you mean.
- `note` (string, required): Path to the note, relative to the vault root or to the working directory. Absolute paths reach a note in another vault. `.md` optional.
- `quote` (string, required): The passage to anchor to, copied verbatim out of the note.
- `run` (string): Groups the comments from one review pass so the reader can dismiss them together. Defaults to this session's id; pass the same value for every comment in a pass.

### `obelisk_reply` (~165 tokens)

Reply to a comment

Add a reply to an existing comment thread. A reply is markdown too, so a counter-proposal is a ```suggestion block in one.

Use this to answer a question a person asked in a comment. To say that you have done what a comment asked, edit the note and call obelisk_resolve instead — a reply saying "done" leaves the thread open.

Input parameters:

- `body` (string, required): The reply, as markdown.
- `id` (string, required): The comment's id, from obelisk_list.
- `model` (string): Written into the reply's author field.
- `note` (string, required): Path to the note, relative to the vault root or to the working directory. Absolute paths reach a note in another vault. `.md` optional.

### `obelisk_resolve` (~162 tokens)

Resolve or reopen a comment

Mark a comment settled — the reader's sidebar grays it out and drops it from the open count.

This is what closes the loop on a comment a person left for you: read it, make the edit in the note yourself, then resolve it. Resolving a comment you did not write is allowed, but it records that what the comment asked for has been done, so resolve only once it has.

Input parameters:

- `id` (string, required): The comment's id, from obelisk_list.
- `note` (string, required): Path to the note, relative to the vault root or to the working directory. Absolute paths reach a note in another vault. `.md` optional.
- `reopen` (boolean): Mark it open again instead. Defaults to false.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/zachhannum-obelisk/obelisk-mcp#diagnostics

## Score history

- 2026-09-21: 89
- 2026-09-20: 88
- 2026-09-19: 88
- 2026-09-18: 87
- 2026-09-17: 87
- 2026-09-16: 86
- 2026-09-15: 86
- 2026-09-14: 86
- 2026-09-13: 85
- 2026-09-12: 85
- 2026-09-11: 84
- 2026-09-10: 84
- 2026-09-09: 83
- 2026-09-08: 83
- 2026-09-07: 82
- 2026-09-06: 82
- 2026-09-05: 66
- 2026-09-04: 80
- 2026-09-03: 65

## Common questions

### What is the io.github.zachhannum/obelisk MCP server?

io.github.zachhannum/obelisk is an MCP server listed in the public MCP registry as io.github.zachhannum/obelisk. Comment on a passage of an Obsidian note, and propose suggested edits. This page covers its npm package (obelisk-mcp).

### Is the io.github.zachhannum/obelisk MCP server safe to use?

io.github.zachhannum/obelisk scores 89 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.

### What tools does the io.github.zachhannum/obelisk MCP server expose?

io.github.zachhannum/obelisk exposes 4 tools: obelisk_list, obelisk_comment, obelisk_reply, obelisk_resolve. Their descriptions and schemas cost roughly 886 tokens of context every time the server is loaded.

### Is the io.github.zachhannum/obelisk MCP server still maintained?

io.github.zachhannum/obelisk 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 io.github.zachhannum/obelisk MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/obelisk-mcp
- Socket report: https://socket.dev/npm/package/obelisk-mcp
- Repository: https://github.com/zachhannum/obelisk
- Website: https://obelisk.typeworks.dev/
- Changelog RSS feed: https://verifymcp.io/servers/zachhannum-obelisk/obelisk-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/zachhannum-obelisk/obelisk-mcp.json
- HTML version of this page: https://verifymcp.io/servers/zachhannum-obelisk/obelisk-mcp