Obsidian MCP Server (eddmann/obsidian-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 18 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
2 months ago

Obsidian MCP Server

Enables LLMs like Claude and ChatGPT to access and manage git-backed Obsidian vaults through tools for file operations, search, tags, and journal logging.

→ eddmann/obsidian-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

eddmann

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
18 tools verified — handlers match their declared behaviour
5 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: GIT_TOKEN, OAUTH_CLIENT_SECRET, PERSONAL_AUTH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

lowaws-cdk@2.172.0GHSA-v63m-x9r9-8gqp

AWS CDK CLI prints AWS credentials retrieved by custom credential plugins

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAWS_ACCOUNT_ID
configAWS_REGION
configBASE_URLOAuth variables: OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, PERSONAL_AUTH_TOKEN,
configCDK_DEFAULT_ACCOUNT
configCDK_DEFAULT_REGION
🔐 secretGIT_TOKEN=your_token_here
configGIT_USERNAME
configJOURNAL_ACTIVITY_SECTION
configJOURNAL_FILE_TEMPLATE
configJOURNAL_PATH_TEMPLATE
configLOCAL_VAULT_PATH
configLOG_LEVEL
configOAUTH_CLIENT_IDOAuth variables: , OAUTH_CLIENT_SECRET, PERSONAL_AUTH_TOKEN, BASE_URL
🔐 secretOAUTH_CLIENT_SECRETOAuth variables: OAUTH_CLIENT_ID, , PERSONAL_AUTH_TOKEN, BASE_URL
🔐 secretPERSONAL_AUTH_TOKENOAuth variables: OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, , BASE_URL
configSESSION_DYNAMODB_REGION
configSESSION_DYNAMODB_TABLE
configSESSION_DYNAMODB_TTL_ATTRIBUTE
configSESSION_EXPIRY_MS
configVAULT_BRANCH
configVAULT_REPO=https://github.com/username/vault-repo.git
configVAULT_REPO_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool inputs are validated

Only 0/18 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/18 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/eddmann/obsidian-mcp)](https://m8ven.ai/mcp/eddmann/obsidian-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 8af012f80bb13eb86110620387003ccb421973a3
code hash: e8f860b268e2b361323fdc0f8b633313f1ee6d88465c4b6247659363b91290c4
verified: 6/17/2026, 11:33:25 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client