obsidian-mcp-resilient-bridge (nekko4044-lgtm/obsidian-mcp-resilient-bridge) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 11 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

obsidian-mcp-resilient-bridge

Enables Claude Code to keep a stable MCP connection to an Obsidian vault across Obsidian closures or restarts, automatically reconnecting and surfacing graceful errors when Obsidian is unavailable.

→ nekko4044-lgtm/obsidian-mcp-resilient-bridge· 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

⚡ 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

nekko4044-lgtm

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
✅
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.
// 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.
configCLAUDE_CODE_SSE_PORT
configCLAUDE_CONFIG_DIR
configENABLE_IDE_INTEGRATION
configOBSIDIAN_MCP_STARTUP_GRACE_MSSoftened, not solved. The bridge holds the session's first tools/list (and resources/list/prompts/list) request open for up to OBSIDIAN_MCP_STARTUP_GRACE_MS (10 seconds by default), retrying the Obsidian connection in the background. Open Obsidian within that window and the session picks up the real tool list with no restart. If the window runs out first, that session is stuck with no Obsidian tools until you restart it once - Claude Code has no way to be told "the list changed, please re-fetch it" mid-session.
configOBSIDIAN_MCP_URLThe upstream URL can be overridden with the environment variable if your Obsidian plugin is configured to listen somewhere other than the default http://localhost:22360/sse.
configSHELL
configVSCODE_GIT_ASKPASS_EXTRA_ARGS
configVSCODE_GIT_ASKPASS_NODE
configXDG_CONFIG_HOME
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

11/11 tools missing one or more hints — get_current_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_workspace_files (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); view (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

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 4 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/nekko4044-lgtm/obsidian-mcp-resilient-bridge)](https://m8ven.ai/mcp/nekko4044-lgtm/obsidian-mcp-resilient-bridge)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 48ac301c4e4cbd1adada216b17e4850520702b0a
code hash: 7c143e1d0fc673930374e201db3aa3c0a1654fc2ef7dc0d53c0e5bd2f7a60b19
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