ai.smithery/Hint-Services-obsidian-github-mcp
Connect AI assistants to your GitHub-hosted Obsidian vault to seamlessly access, search, and analy…
Installation
Claude Desktop config (remote)
{
"mcpServers": {
"ai-smithery-hint-services-obsidian-github-mcp": {
"type": "streamable-http",
"url": "https://server.smithery.ai/@Hint-Services/obsidian-github-mcp/mcp"
}
}
}Cursor config
{
"mcpServers": {
"ai-smithery-hint-services-obsidian-github-mcp": {
"url": "https://server.smithery.ai/@Hint-Services/obsidian-github-mcp/mcp"
}
}
}Security Report
Score Breakdown
Findings (6)
Remote HTTP Endpoint Without Visible Authentication
Server operates via streamable-http on a remote URL (https://server.smithery.ai/...), meaning it accepts connections from the internet. No authentication mechanism is visible in the metadata, creating potential for unauthorized access or man-in-the-middle attacks.
Truncated and Vague Description
The description is cut off mid-sentence ('...analy…'), making it impossible to fully understand the server's scope and capabilities. This prevents proper security assessment of what data access is intended.
Broad GitHub & Vault Access Claims
The server claims to connect to GitHub-hosted Obsidian vaults with 'seamless access' and 'search' capabilities. This implies broad read access to potentially sensitive personal notes, research, or private documentation stored in GitHub repositories.
Tool Definitions Unavailable
Tool definitions were not fetched from the server, preventing verification of actual capabilities, input validation, and potential prompt injection vectors. This is a gap in the security audit.
Potential for Sensitive Data Access
A server designed to access GitHub-hosted Obsidian vaults could potentially exfiltrate sensitive personal notes, credentials, or private research if not properly constrained. The broad 'access' claim is concerning.
Semantic Analysis Summary
This server presents moderate security concerns due to its remote HTTP endpoint without visible authentication, vague truncated description, and broad claims of GitHub/vault access. The inability to inspect tool definitions prevents full assessment of input validation and prompt injection risks. The repository link is a positive trust signal, but the scope of data access (personal notes/vaults) warrants careful permission review before deployment.
Last scanned 59m ago
Details
- Version
- 0.4.0
- Transport
- streamable-http
- Capabilities
- Repository
- Hint-Services/obsidian-github-mcp