Is MCP Fns Check safe to use?

MCP Fns Check has an HVTrust score of 53.2/100 (Grade C), ranked #670 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Fns Check?

MCP Fns Check scores 53.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 15 GitHub stars and is categorized under MCP Servers.

MCP Fns Check

atomno-mcp/mcp-fns-check

MCP-сервер проверки контрагентов РФ: ЕГРЮЛ, банкротство, налоговые долги, приставы и арбитражные дела. Для разведки комп

MCP Servers Python Grade C Listed MIT

53.2/100

Rank #670 of 1320

Compare MCP Fns Check

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-02 · 2d ago

Recent change

Rank +10

Is MCP Fns Check safe? MCP Fns Check scores 53.2/100 (Grade C), ranked #670 of 1320 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 4.6/10; recent commits are unsigned; last pushed 2026-09-02. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#329 Elasticsearch MCP Server — 53.3 (C) → #330 Awkoy Notion MCP Server — 53.3 (C) → #332 JADX MCP Server — 53.2 (C) → #333 Comfyui MCP — 53.2 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-04

Rank Moved

Rank dropped 13 spots (#657 → #670)

2026-09-03

Rank Moved

Rank dropped 35 spots (#622 → #657)

2026-09-02

Rank Moved

Rank dropped 21 spots (#601 → #622)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.6/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 MCP Fns Check View MCP Servers Report missing data

41.6

Activity sub-score · out of 100

#331

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

2026-08-11 2026-09-04

Activity & Reach

Stars

Forks

Last Push

2026-09-02

2 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼13

was #657

Analysis

HVTrust Dimensions vs MCP Servers

53.2 / 100 · 100.0% confidence

MCP Fns Check MCP Servers average (778 agents)

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

5.8 / 25

3.7 below avg 9.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.4 / 17

0.6 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

13.1 / 20

0.9 above avg 12.2

AdoptionLog-scaled stars · package downloads

5.1 / 20

1.1 below avg 6.2

Activity Inputs

41.6 / 100

StarsRepository reach

7.2 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

7.5 / 25

CommunityFork signal

2.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.6 / 10

OpenSSF Scorecard · scanned Aug 26, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 9

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 10

Is MCP Fns Check safe?

Public trust evidence for MCP Fns Check 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 MCP Fns Check publish package provenance?

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

Does MCP Fns Check have an OpenSSF Scorecard?

MCP Fns Check has an OpenSSF Scorecard score of 4.6/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 MCP Fns Check actively maintained?

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

What license does MCP Fns Check use?

MCP Fns Check ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Fns Check's commits signed?

0% of the last 100 commits to MCP Fns Check 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

high confidence

Implemented

MCP Fns Check appears to expose MCP server capabilities.

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

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

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

Maintain MCP Fns Check?

For maintainers

HVTrust scores MCP Fns Check 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-04

Rank Moved

Rank dropped 13 spots (#657 → #670)

2026-09-03

Rank Moved

Rank dropped 35 spots (#622 → #657)

2026-09-02

Rank Moved

Rank dropped 21 spots (#601 → #622)

2026-09-01

Rank Moved

Rank dropped 19 spots (#582 → #601)

2026-08-31

Grade Changed

Trust grade D → C

2026-08-31

Rank Moved

Rank rose 47 spots (#629 → #582)

2026-08-31

HVTrust Changed

HVTrust up 3.7pts (49.3 → 53.0)

2026-08-31

Activity Score Changed

Activity score up 10pts (28 → 38)

2026-08-30

Rank Moved

Rank dropped 14 spots (#615 → #629)

2026-08-29

Rank Moved

Rank dropped 40 spots (#575 → #615)

2026-08-28

Rank Moved

Rank dropped 21 spots (#554 → #575)

2026-08-27

Rank Moved

Rank dropped 15 spots (#539 → #554)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.6/10

2026-08-26

Rank Moved

Rank rose 257 spots (#796 → #539)

2026-08-26

HVTrust Changed

HVTrust up 20.9pts (28.9 → 49.8)

2026-08-16

Rank Moved

Rank dropped 15 spots (#774 → #789)

2026-08-13

Rank Moved

Rank dropped 27 spots (#745 → #772)

2026-08-13

Activity Score Changed

Activity score down 10pts (40 → 30)

2026-08-10

Rank Moved

Rank dropped 37 spots (#710 → #747)

2026-08-08

Newly Listed

First tracked at rank #994

GitHub → PyPI: atomno-mcp-fns-check

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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