Is Norman MCP Server safe to use?

Norman MCP Server has an HVTrust score of 61.2/100 (Grade C), ranked #601 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Norman MCP Server?

Norman MCP Server scores 61.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 58 GitHub stars and is categorized under MCP Servers.

Norman MCP Server

norman-finance/norman-mcp-server

AI-powered bookkeeping and tax filing automation for entrepreneurs at the heart of the European economy

MCP Servers Python Listed MIT

Is Norman MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.1 / 10

Provenance None

Signed commits 46%

Last push today

Compare Norman MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Norman MCP Server scores 61.2/100 (Grade C), ranked #601 of 1325 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.1/10; 46% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How Norman MCP Server compares in MCP Servers

#336 Desktop Commander MCP 61.3 +0.1
#337 Replicant MCP 61.3 +0.1
#338 Norman MCP Server 61.2 this agent
#339 Atlassian Rovo MCP Server 61.1 −0.1
#340 Xdebug MCP 61.1 −0.1

Bars show each HVTrust score; the tick marks Norman MCP Server’s 61.2.

Where the 61.2 comes from

HVTrust dimensions vs the MCP Servers average

61.2 / 100 · 100.0% confidence

Norman MCP Server MCP Servers average (775 agents)

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

7.4 / 25

2.9 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

12.0 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.7 / 20

7.6 above avg 12.1

AdoptionLog-scaled stars · package downloads

6.1 / 20

1.1 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 21 spots (#583 → #604)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.1/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 Norman MCP Server View MCP Servers Report missing data

64.9

Activity sub-score · out of 100

#338

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

Activity & Reach

Stars

Forks

Last Push

2026-09-26

today

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲3

was #604

Analysis

Activity Inputs

64.9 / 100

StarsRepository reach

10.6 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

24.0 / 25

CommunityFork signal

5.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.1 / 10

OpenSSF Scorecard · scanned Sep 18, 2026

Signed Commits

46%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Norman MCP Server

Norman MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Norman MCP Server publish package provenance?

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

Does Norman MCP Server have an OpenSSF Scorecard?

Norman MCP Server has an OpenSSF Scorecard score of 4.1/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 Norman MCP Server actively maintained?

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

What license does Norman MCP Server use?

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

Are Norman MCP Server's commits signed?

46% of the last 100 commits to Norman MCP Server 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

Norman MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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

How this surface has changed

Detected changes to Norman MCP Server'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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-04

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

Maintain Norman MCP Server?

For maintainers

HVTrust scores Norman MCP Server 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 21 spots (#583 → #604)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 223 spots (#801 → #578)

2026-09-23

HVTrust Changed

HVTrust up 33.0pts (28.8 → 61.8)

2026-09-22

Newly Listed

First tracked at rank #801

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 12 spots (#565 → #577)

2026-09-14

Rank Moved

Rank dropped 10 spots (#569 → #579)

2026-09-13

Rank Moved

Rank rose 13 spots (#582 → #569)

2026-09-11

Rank Moved

Rank dropped 12 spots (#565 → #577)

2026-09-07

Rank Moved

Rank dropped 43 spots (#515 → #558)

2026-09-06

Rank Moved

Rank dropped 11 spots (#504 → #515)

2026-09-05

Rank Moved

Rank dropped 78 spots (#426 → #504)

2026-09-04

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-04

Rank Moved

Rank dropped 22 spots (#404 → #426)

2026-09-03

Rank Moved

Rank dropped 15 spots (#389 → #404)

2026-09-02

Rank Moved

Rank rose 19 spots (#408 → #389)

2026-08-31

Rank Moved

Rank dropped 21 spots (#380 → #401)

2026-08-29

Rank Moved

Rank dropped 10 spots (#377 → #387)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.0/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 323 spots (#691 → #368)

2026-08-26

HVTrust Changed

HVTrust up 23.4pts (36.6 → 60.0)

2026-08-16

Rank Moved

Rank dropped 13 spots (#674 → #687)

2026-08-10

Rank Moved

Rank dropped 27 spots (#647 → #674)

2026-08-08

Newly Listed

First tracked at rank #645

GitHub → PyPI: norman-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/norman-mcp-server.svg)](https://hvtracker.net/agents/norman-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/norman-mcp-server"><img src="https://hvtracker.net/badge/norman-mcp-server.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