Finance Toolkit
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Computer or cloud
Seekstone
Overview
Description from the maker (original English)
Filesystem-direct Obsidian MCP server — search and edit your vault with low context-tax.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiEarly↓ 644/wk · ★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Accounting, finance & tax
- You need to fill in: SEEKSTONE_VAULT
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
SEEKSTONE_VAULT
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"seekstone": {
"command": "npx",
"args": [
"-y",
"seekstone"
],
"env": {
"SEEKSTONE_VAULT": "your-value"
}
}
}
}Run this in your terminal
claude mcp add seekstone --env SEEKSTONE_VAULT=your-value -- npx -y seekstoneFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"seekstone": {
"command": "npx",
"args": [
"-y",
"seekstone"
],
"env": {
"SEEKSTONE_VAULT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"seekstone": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"seekstone"
],
"env": {
"SEEKSTONE_VAULT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Absolute path to your Obsidian vault.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account shaqmughal, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Accounting, finance & taxi
- More stars than 0% of the other 2944 servers in this category
- Published to the registry more recently than 92% of the other 2944 servers in this category
- Basic checks equal to or better than 100% of the other 2944 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Seekstone safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: SEEKSTONE_VAULT
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.23.0) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Finance Toolkit, SolidInvoice, Korea Tax Calculator
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
SolidInvoice
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Runs in the cloud✓ solidinvoice.co
Korea Tax Calculator
Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.
Runs on your computer
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The Obsidian MCP server that needs no plugin, no running Obsidian app — and doesn't blow your context window. Filesystem-direct · single-digit-ms keyword search · ~26 ms semantic · ~2 KB payloads · 25 tools · macOS · Linux · Windows
seekstone.dev →
| Seekstone | obsidian-mcp-server (#1 by downloads) | REST-proxy servers | |
|---|---|---|---|
| Local REST API plugin | Not needed | Required | Required |
| Obsidian app running | Not needed — works with Obsidian closed | Required | Required |
| Search payload @ 10k notes | 2.0 KB | 47 KB | up to 95 MB |
| Warm search latency @ 10k notes | 5.6 ms | 732 ms (~131× slower) | up to 1,550 ms |
| Structured frontmatter queries | Built-in (`query_notes`) — property/date/size predicates, answers in a few hundred bytes | JSONLogic via REST | Varies |
Same queries, same committed vaults, 20 runs each, one machine. In-process adapters were re-run on the fixture-v2 vault in September 2026; the REST-proxy rows (rest, obsidian-mcp-server, mcp-obsidian) plus obsidian-mcp and obsidian-mcp-pro are June 2026 captures on fixture v1 — per-row provenance in benchmarks.json, the generated source of truth every number here is checked against in CI — full results across eight servers and three vault sizes below, fully reproducible from the harness.
What is Seekstone?
Seekstone is an Obsidian MCP server — it gives Claude (and any Model Context Protocol client) direct read and write access to your Obsidian vault. No Obsidian app needs to be open, no plugins are required, and nothing leaves your machine.
It reads your vault directly from disk rather than routing through the Obsidian Local REST API plugin, and holds a warm full-text index in-process. The practical difference is twofold:
- Speed. Keyword searches return in single-digit milliseconds warm and semantic searches in ~26 ms — up to ~508× faster than every other Obsidian MCP server we benchmarked, because there's no subprocess to spawn and no HTTP round-trip per query.
- Context. A broad search that returns tens of megabytes and millions of tokens via a REST-proxy server returns ~2 KB via Seekstone — up to a ~47,000× reduction that only widens as your vault grows.
Search comes in three modes: ranked full-text search (fuzzy and prefix matching), optional local semantic search (meaning-based, via a small on-device embedding model — opt-in, offline at runtime after a one-time ~30 MB model download), and structured metadata queries — query_notes filters by frontmatter properties (status, due, type, …), tags, folder, modified time, and size, answering questions like *"which draft notes changed this week?"* in a few hundred bytes instead of a search-and-read loop.
Claude can search and read your entire note library, in milliseconds, without burning most of its context window on a single tool call.
Published on npm as seekstone — install with npx -y seekstone. (Previously also published as obsidian-mcp-seekstone; that alias is deprecated but existing installs keep working.)
Why Seekstone? The numbers.
Most Obsidian MCP servers return full note content for every search hit. On a broad query that's megabytes of text your LLM has to process — most of it irrelevant, all of it burning context window.
Seekstone returns short ranked excerpts instead (~120 characters by default, tunable per query). We benchmarked Seekstone against 7 other Obsidian MCP servers — 8 servers total — across three vault sizes — 1,000 / 5,000 / 10,000 notes (20 runs each). Every number below is fully reproducible: the vaults are committed to this repo (generated from the public-domain 1911 Encyclopædia Britannica), so you can clone it and run the exact same benchmark yourself.
The point of testing three sizes is that this is where the architectures diverge — a real vault only grows.
Search payload — bytes returned per query (context tax; lower is better)
| Server | Architecture | 1k notes | 5k notes | 10k notes |
|---|---|---|---|---|
| 🥇 Seekstone | in-process index | 1.6 KB | 1.8 KB | 2.0 KB |
| mcpvault | fs-direct subprocess | 1.7 KB | 1.9 KB | 2.2 KB |
| obsidian-mcp-rs | fs-direct, per-query scan | 5.4 KB | 5.8 KB | 6.2 KB |
| obsidian-tc | SQLite platform | 4.6 KB | 6.8 KB | 7.3 KB |
| obsidian-mcp-server | REST API | 55 KB | 47 KB | 47 KB |
| obsidian-mcp-pro | fs-direct subprocess | 25 KB | 84 KB | 114 KB |
| obsidian-mcp | fs-direct subprocess | 18 KB | 105 KB | 203 KB |
| mcp-obsidian | REST API | 9.8 MB | 45 MB | 95 MB |
Seekstone stays flat (~2 KB) no matter how big your vault gets, because it always returns ranked excerpts — and it's now the smallest payload of every server tested, edging out mcpvault at all three sizes. The REST-proxy servers return full note content for every match, so they grow with the vault — mcp-obsidian hits 95 MB at 10k notes, and a single broad query (the capital of) averaged 370.9 MB / 97.8 million tokens per call across 20 runs. At 10k notes that's a ~47,000× context-tax difference.
Search latency — warm mean, ms (lower is better)
| Server | 1k notes | 5k notes | 10k notes | vs Seekstone @10k |
|---|---|---|---|---|
| 🥇 Seekstone | 1.0 | 2.8 | 5.6 | — |
| obsidian-mcp-rs | 6.0 | 19 | 36 | ~6× slower |
| obsidian-mcp-pro | 41 | 200 | 407 | ~73× slower |
| obsidian-mcp-server | 82 | 356 | 732 | ~131× slower |
| obsidian-mcp | 78 | 380 | 772 | ~138× slower |
| mcpvault | 90 | 431 | 893 | ~159× slower |
| mcp-obsidian | 164 | 740 | 1,550 | ~277× slower |
| obsidian-tc | 273 | 1,380 | 2,849 | ~508× slower |
Every competitor spawns a subprocess or makes HTTP round-trips per query, and most do work that scales with vault size. Seekstone holds a warm in-process index — no IPC, no network — so keyword search stays in single-digit milliseconds even at 10,000 notes (the shipped semantic pipeline — embed, scan, MaxSim rerank — lands at ~26 ms). And the gap widens with scale: from 1k → 10k notes the competitors slow down 5–10×, while Seekstone barely moves. Even the *fastest* alternative — obsidian-mcp-rs, which re-scans the vault on every query — is ~6× slower warm at 10k notes with 3× the payload, and the REST-proxy generation runs ~100–280× slower.
Tool list — tokens loaded before the first call (lower is better)
When a session starts, most MCP clients load the server's tool list (each tool's name, description, and input schema) into the model's context, before any tool is called. Some, such as Claude Code with tool search, load only the names until a tool is needed. Loaded in full, Seekstone's 25 tools cost ~5,742 tokens (26 KB). With SEEKSTONE_READ_ONLY=1 the 11 write tools drop out of the list and it falls to ~3,261 tokens, 43% less. The harness measures this from the built server over MCP (npm run harness -- schema-tax), and CI re-me
Only the beginning is shown; read the rest in the repo