Is Smart Thinking safe to use?

Smart Thinking has an HVTrust score of 53.7/100 (Grade C), ranked #834 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Smart Thinking?

Smart Thinking scores 53.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 34 GitHub stars and is categorized under MCP Servers.

Smart Thinking

Leghis/Smart-Thinking

Smart-Thinking is a Model Context Protocol (MCP) server that delivers graph-based, multi-step reasoning without relying on external AI APIs. Everything happens locally: similarity search, heuristic-based scoring, verification tracking, memory, and visualization all run in a deterministic pipeline…

MCP Servers JavaScript Listed MIT

Is Smart Thinking safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 5.4 / 10

Provenance None

Signed commits 10%

Last push 6d ago

Compare Smart Thinking

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Smart Thinking scores 53.7/100 (Grade C), ranked #834 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.4/10; 10% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

How Smart Thinking compares in MCP Servers

Bars show each HVTrust score; the tick marks Smart Thinking’s 53.7.

Where the 53.7 comes from

HVTrust dimensions vs the MCP Servers average

53.7 / 100 · 100.0% confidence

Smart Thinking MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.3 / 25

3.0 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.1 / 17

0.9 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

18.8 / 20

6.7 above avg 12.1

AdoptionLog-scaled stars · package downloads

3.7 / 20

3.5 below avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-25

Rank Moved

Rank dropped 11 spots (#824 → #835)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.4/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Smart Thinking View MCP Servers Report missing data

61.2

Activity sub-score · out of 100

#470

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-20

6 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #835

Analysis

Activity Inputs

61.2 / 100

StarsRepository reach

9.3 / 30

FreshnessLast push recency

24.2 / 25

ActivityRecent commits

22.4 / 25

CommunityFork signal

5.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.4 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

10%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 2

SAST 0

Security-Policy 4

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 10

Common questions about Smart Thinking

Public trust evidence for Smart Thinking is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Smart Thinking publish package provenance?

No published build provenance is currently detected for Smart Thinking. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Smart Thinking have an OpenSSF Scorecard?

Smart Thinking has an OpenSSF Scorecard score of 5.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Smart Thinking actively maintained?

Actively maintained. The repository was pushed to within the last 6 day(s).

What license does Smart Thinking use?

Smart Thinking ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Smart Thinking's commits signed?

10% of the last 100 commits to Smart Thinking are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

Scored in HVTrust

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 Server Support

low confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Smart Thinking'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.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-17

Provider Removed

Runtime surface shrank — no longer detected: Tavily

2026-09-16

Provider Added

Runtime surface grew — new detected provider dependency: Tavily

2026-09-16

Mcp Status Changed

Detected MCP server support changed: implemented → declared

2026-09-14

Activity Resumed

Activity resumed

Maintain Smart Thinking?

For maintainers

HVTrust scores Smart Thinking 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-25

Rank Moved

Rank dropped 11 spots (#824 → #835)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 383 spots (#436 → #819)

2026-09-23

HVTrust Changed

HVTrust up 9.0pts (44.9 → 53.9)

2026-09-22

Newly Listed

First tracked at rank #436

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank rose 21 spots (#825 → #804)

2026-09-18

Grade Changed

Trust grade D → C

2026-09-18

Rank Moved

Rank rose 163 spots (#988 → #825)

2026-09-18

HVTrust Changed

HVTrust up 5.8pts (47.9 → 53.7)

2026-09-17

Provider Removed

Runtime surface shrank — no longer detected: Tavily

2026-09-17

Rank Moved

Rank rose 23 spots (#1011 → #988)

2026-09-16

Provider Added

Runtime surface grew — new detected provider dependency: Tavily

2026-09-16

Mcp Status Changed

Detected MCP server support changed: implemented → declared

2026-09-16

Rank Moved

Rank dropped 40 spots (#971 → #1011)

2026-09-14

Activity Resumed

Activity resumed

2026-09-14

Rank Moved

Rank rose 303 spots (#1276 → #973)

2026-09-14

HVTrust Changed

HVTrust up 17.4pts (31.0 → 48.4)

2026-09-14

Activity Score Changed

Activity score up 42pts (14 → 56)

2026-09-08

Rank Moved

Rank dropped 12 spots (#1255 → #1267)

2026-09-07

Rank Moved

Rank dropped 11 spots (#1244 → #1255)

2026-09-06

Rank Moved

Rank dropped 15 spots (#1229 → #1244)

2026-09-05

Rank Moved

Rank dropped 20 spots (#1209 → #1229)

2026-09-04

Rank Moved

Rank dropped 18 spots (#1191 → #1209)

2026-09-03

Rank Moved

Rank dropped 43 spots (#1148 → #1191)

2026-09-02

Rank Moved

Rank dropped 39 spots (#1109 → #1148)

2026-09-01

Rank Moved

Rank dropped 42 spots (#1067 → #1109)

2026-08-31

Rank Moved

Rank dropped 29 spots (#1038 → #1067)

2026-08-30

Rank Moved

Rank dropped 56 spots (#982 → #1038)

2026-08-29

Scorecard Added

OSSF Scorecard: 2.7/10

2026-08-29

Rank Moved

Rank rose 319 spots (#1301 → #982)

2026-08-29

HVTrust Changed

HVTrust up 17.3pts (13.7 → 31.0)

2026-08-26

Rank Moved

Rank dropped 11 spots (#1287 → #1298)

2026-08-16

Rank Moved

Rank dropped 25 spots (#1263 → #1288)

2026-08-10

Rank Moved

Rank dropped 79 spots (#1184 → #1263)

2026-08-08

Newly Listed

First tracked at rank #1184

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/smart-thinking.svg)](https://hvtracker.net/agents/smart-thinking)
            
HTML:
            <a href="https://hvtracker.net/agents/smart-thinking"><img src="https://hvtracker.net/badge/smart-thinking.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON