Smart Connections MCP
Give Claude semantic memory of your Obsidian vault — local semantic search over Smart Connections embeddings via MCP. Multi-vault, block-level, 100% private.
Is Smart Connections MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Smart Connections MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Smart Connections MCP scores 46.5/100 (Grade D), ranked #1089 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.1/10; recent commits are unsigned; no published advisory affects its latest release (smart-connections-mcp); last pushed 2026-08-22. Every point is earned from checkable signals — never paid placement. How scoring works →
How Smart Connections MCP could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 61.2 C · #357 of 781
- Raise the OSSF Scorecard from 3.1 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +12.3 → 58.8 C · #389 of 781
- Sign every commit0% signed today +5.0 → 51.5 C · #540 of 781
Chain of custody
Scanners check what the code says. This traces who ships Smart Connections MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Unsigned
github.com/msdanyg/smart-connections-mcp, MIT, last pushed 2026-08-22. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.1/10 (scanned Oct 15, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions9
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests -1CII-Best-Practices 0Code-Review 0Contributors 0Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 2Packaging -1Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases -1Token-Permissions 9Vulnerabilities 0 -
Published packages Linked, not attested
- npm smart-connections-mcp Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: smart-connections-mcp 2.0.1. No published advisory affects it (OSV, checked 2026-10-18).
Changes to this chain
- 2026-08-26 OSSF Scorecard: 3.8/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Smart Connections MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Smart Connections MCP compares in MCP Servers
- #620 Kronan MCP 46.7 +0.2
- #621 MTG MCP Server 46.6 +0.1
- #622 Smart Connections MCP 46.5 this agent
- #623 Danishashko Yahoo Finance 46.5 ±0
- #624 Simplenote MCP 46.3 −0.2
Bars show each HVTrust score; the tick marks Smart Connections MCP’s 46.5.
Where the 46.5 comes from
HVTrust dimensions vs the MCP Servers average
46.5 / 100 · 100.0% confidenceSmart Connections MCP MCP Servers average (781 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
33.7 / 100Common questions about Smart Connections MCP
Does Smart Connections MCP publish package provenance?
Does Smart Connections MCP have an OpenSSF Scorecard?
Is Smart Connections MCP actively maintained?
What license does Smart Connections MCP use?
Are Smart Connections MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Smart Connections MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Smart Connections MCP?
For maintainers
HVTrust scores Smart Connections MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/smart-connections-mcp)
<a href="https://hvtracker.net/agents/smart-connections-mcp"><img src="https://hvtracker.net/badge/smart-connections-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON