M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionSSE MCP Server ExampleAn SSE MCP configuration example for hosted cloud servicesObsidian Web MCPSecure remote access to your Obsidian vault over HTTPS with OAuth 2.0 authentication.
FMRS26 / 100 · D68 / 100 · C
Reliability3 / 209 / 20
Security and permissions6 / 2016 / 20
Maintenance8 / 2014 / 20
Documentation3 / 2017 / 20
Setup experience6 / 2012 / 20
Best for
  • Claude Code plugin developers looking for an SSE MCP configuration example
  • Users who know and trust the configured cloud-service endpoints
  • Users who want secure remote access to their Obsidian vault from any device.
  • Integrating Claude.ai (web) or mobile with Obsidian.
  • Those needing concurrent writes with Obsidian Sync without file conflicts.
Not for
  • Users who require a documented tool inventory
  • Users who require verified permission scopes or client compatibility
  • Users who do not trust the configured external endpoints
  • Users who only need local stdio MCP access without remote capabilities.
  • Those unwilling to set up an OAuth password or use a Cloudflare Tunnel.
  • Users with extremely high security requirements who distrust network exposure (though encrypted).
Required permissions
  • The configuration indicates access to the listed SSE endpoints, but specifies no account permissions or authorization scopes
  • custom-service includes the X-API-Version: v1 header and an X-Client-ID header using ${CLIENT_ID}
  • Read and write files in the directory specified by VAULT_PATH.
  • Perform file operations (move, delete with soft delete to .trash).
  • Create daily notes, write binary files.
  • Maintain an in-memory frontmatter index, potentially modifying index files.
  • Access the network (for Cloudflare Tunnel, heartbeat URLs).
Risks and side effects
  • The README warns that MCP servers, files, or software included in plugins are not controlled or verified by Anthropic
  • The source does not verify endpoint behavior, availability, or permission requirements
  • Sending header values to an untrusted service may expose information
  • Credential leakage: exposed OAuth password or MCP token could allow unauthorized access.
  • Path traversal mitigation is not infallible; keep updated.
  • Extension system is not sandboxed; loading untrusted extensions could be risky.
  • Audit log is best-effort and not tamper-evident; records may be dropped at runtime.
  • Misconfiguration may cause the server to fail to start or expose vulnerabilities.
Supported clientsClaude Desktop, Claude Mobile, Claude Web
Tools020