updated 2026-10-16 16:07 UTC

Smart Thinking

Repository

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 26d 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 51.2/100 (Grade C), ranked #966 of 1378 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 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Smart Thinking and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/Leghis/Smart-Thinking, MIT, last pushed 2026-09-20. 10% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.4/10 (scanned Oct 13, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies2
    All 18 Scorecard checks
    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

  3. Published packages None

    No registry package. Smart Thinking is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-29 OSSF Scorecard: 2.7/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Smart Thinking’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.

Signed credential (JSON) How to verify

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 Thinking compares in MCP Servers

  1. #541 Pagerduty MCP Server 51.3 +0.1
  2. #542 MCP Odoo 51.3 +0.1
  3. #543 Smart Thinking 51.2 this agent
  4. #544 Scriptivox MCP Server 51.1 −0.1
  5. #545 JavaLens 51.1 −0.1

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

Where the 51.2 comes from

HVTrust dimensions vs the MCP Servers average

51.2 / 100 · 100.0% confidence

Smart Thinking MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.3 / 25
3.2 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
13.1 / 17
0.8 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
16.3 / 20
4.0 above avg 12.3
AdoptionLog-scaled stars · package downloads
3.7 / 20
3.7 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-16
Rank Moved
Rank dropped 13 spots (#953 → #966)
2026-10-14
Rank Moved
Rank dropped 28 spots (#916 → #944)
2026-10-13
Rank Moved
Rank dropped 11 spots (#905 → #916)
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
54.6
Activity sub-score · out of 100
#543
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 →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed 26 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
33
Forks
11
Last Push
2026-09-20
26 days ago
Commits (4 wk)
32
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▼13
was #953

Analysis

Activity Inputs

54.6 / 100
StarsRepository reach
9.2 / 30
FreshnessLast push recency
21.4 / 25
ActivityRecent commits
18.9 / 25
CommunityFork signal
5.0 / 20

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?
Maintained. Last push was 26 days ago.
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
Rank 25HVTrust 4Listed 2MCP 2Grade 2Scorecard 1Score 1Fresh 1Surface 1Surface 1Delisted 1
2026-10-16
Rank Moved
Rank dropped 13 spots (#953 → #966)
2026-10-14
Rank Moved
Rank dropped 28 spots (#916 → #944)
2026-10-13
Rank Moved
Rank dropped 11 spots (#905 → #916)
2026-10-09
Rank Moved
Rank dropped 20 spots (#869 → #889)
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
HVTrust 51.2 Grade C
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.4 · Raw JSON