Is MCP Server For ISO27001 safe to use?

MCP Server For ISO27001 has an HVTrust score of 62.6/100 (Grade C), ranked #628 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Server For ISO27001?

MCP Server For ISO27001 scores 62.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 35 GitHub stars and is categorized under MCP Servers.

MCP Server For ISO27001

Repository Website by Sushegaad

Model Context Protocol (MCP) server for ISO27001: A stateful Model Context Protocol (MCP) server that gives Claude a complete ISO 27001:2022 Information Security Management System (ISMS). Ask Claude to run gap assessments, manage risks, generate policies, track evidence, and run audits — all…

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 4.1 / 10

Provenance Attested

Signed commits 1%

Last push 66d ago

Advisories None known

Compare MCP Server For ISO27001

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Server For ISO27001 scores 62.6/100 (Grade C), ranked #628 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.1/10; 1% of recent commits are signed; no published advisory affects its latest release (iso27001-mcp); last pushed 2026-09-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Server For ISO27001 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.

Raise the OSSF Scorecard from 4.1 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +10.2 → 72.8 B · #184 of 778
Sign every commit1% signed today +4.9 → 67.5 B · #256 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Server For ISO27001 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 Partly signed

github.com/Sushegaad/MCP-Server-for-ISO27001, MIT, last pushed 2026-09-05. 1% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.1/10 (scanned Nov 4, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies10
All 18 Scorecard checks

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 5

Packaging 10

Pinned-Dependencies 10

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages Linked and attested
- npm iso27001-mcp Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: iso27001-mcp 0.9.83. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-09-02 OSSF Scorecard: 4.9/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 MCP Server For ISO27001’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 MCP Server For ISO27001 compares in MCP Servers

#343 Chat on Steroids 62.6 ±0
#344 World Model MCP 62.6 ±0
#345 MCP Server For ISO27001 62.6 this agent
#346 MCP Uptime Kuma 62.5 −0.1
#347 Unreal MCP 62.5 −0.1

Bars show each HVTrust score; the tick marks MCP Server For ISO27001’s 62.6.

Where the 62.6 comes from

HVTrust dimensions vs the MCP Servers average

62.6 / 100 · 100.0% confidence

MCP Server For ISO27001 MCP Servers average (778 agents)

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

12.7 / 25

1.9 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

12.0 / 17

in line with avg 12.3

Maintenance60% last-push freshness · 40% commit activity

7.6 / 20

4.6 below avg 12.2

AdoptionLog-scaled stars · package downloads

7.3 / 20

in line with avg 7.6

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-10-27

Rank Moved

Rank rose 38 spots (#617 → #579)

2026-10-26

Rank Moved

Rank dropped 10 spots (#607 → #617)

2026-10-21

Rank Moved

Rank dropped 19 spots (#591 → #610)

Maintainer Checklist

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

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

Refresh maintenance signals The repo was last pushed 66 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent View MCP Servers Report missing data

30.3

Activity sub-score · out of 100

#345

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-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-09-05

66 days ago

Commits (4 wk)

Downloads (7d)

467

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼6

was #622

Analysis

Activity Inputs

30.3 / 100

StarsRepository reach

9.3 / 30

FreshnessLast push recency

15.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.2 / 20

Common questions about MCP Server For ISO27001

MCP Server For ISO27001 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 MCP Server For ISO27001 publish package provenance?

Yes. MCP Server For ISO27001's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does MCP Server For ISO27001 have an OpenSSF Scorecard?

MCP Server For ISO27001 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 MCP Server For ISO27001 actively maintained?

Slowing down. Last push was 66 days ago — keep an eye on whether activity resumes.

What license does MCP Server For ISO27001 use?

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

Are MCP Server For ISO27001's commits signed?

1% of the last 100 commits to MCP Server For ISO27001 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 Server For ISO27001 appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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

How this surface has changed

Detected changes to MCP Server For ISO27001'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-24

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain MCP Server For ISO27001?

For maintainers

HVTrust scores MCP Server For ISO27001 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-10-27

Rank Moved

Rank rose 38 spots (#617 → #579)

2026-10-26

Rank Moved

Rank dropped 10 spots (#607 → #617)

2026-10-21

Rank Moved

Rank dropped 19 spots (#591 → #610)

2026-10-20

Rank Moved

Rank rose 15 spots (#606 → #591)

2026-10-18

Rank Moved

Rank dropped 15 spots (#589 → #604)

2026-10-13

Rank Moved

Rank dropped 29 spots (#547 → #576)

2026-10-10

Rank Moved

Rank dropped 10 spots (#522 → #532)

2026-10-05

Grade Changed

Trust grade B → C

2026-10-05

Rank Moved

Rank dropped 88 spots (#413 → #501)

2026-10-05

Activity Score Changed

Activity score down 8pts (42 → 35)

2026-10-01

Rank Moved

Rank dropped 20 spots (#385 → #405)

2026-09-30

Rank Moved

Rank dropped 43 spots (#342 → #385)

2026-09-24

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-09-24

Rank Moved

Rank rose 20 spots (#349 → #329)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 582 spots (#931 → #349)

2026-09-23

HVTrust Changed

HVTrust up 42.8pts (26.2 → 69.0)

2026-09-22

Newly Listed

First tracked at rank #931

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-13

Rank Moved

Rank rose 34 spots (#320 → #286)

2026-09-11

Rank Moved

Rank dropped 16 spots (#303 → #319)

2026-09-05

Rank Moved

Rank dropped 53 spots (#239 → #292)

2026-09-04

Rank Moved

Rank dropped 14 spots (#225 → #239)

2026-09-03

Grade Changed

Trust grade D → B

2026-09-03

Rank Moved

Rank rose 572 spots (#797 → #225)

2026-09-03

HVTrust Changed

HVTrust up 22.4pts (46.8 → 69.2)

2026-09-02

Scorecard Added

OSSF Scorecard: 4.9/10

2026-09-02

Rank Moved

Rank rose 130 spots (#927 → #797)

2026-09-02

HVTrust Changed

HVTrust up 6.8pts (40.0 → 46.8)

2026-09-01

Rank Moved

Rank dropped 18 spots (#909 → #927)

2026-08-31

Rank Moved

Rank dropped 33 spots (#876 → #909)

2026-08-30

Rank Moved

Rank rose 17 spots (#893 → #876)

2026-08-30

HVTrust Changed

HVTrust up 3.1pts (36.3 → 39.4)

2026-08-30

Activity Score Changed

Activity score up 12pts (33 → 45)

2026-08-29

Rank Moved

Rank dropped 49 spots (#844 → #893)

2026-08-28

Rank Moved

Rank dropped 28 spots (#816 → #844)

2026-08-27

Rank Moved

Rank dropped 21 spots (#795 → #816)

2026-08-26

Rank Moved

Rank dropped 101 spots (#694 → #795)

2026-08-19

Rank Moved

Rank dropped 20 spots (#669 → #689)

2026-08-19

Activity Score Changed

Activity score down 6pts (40 → 34)

2026-08-16

Rank Moved

Rank dropped 14 spots (#653 → #667)

GitHub → Website → npm: iso27001-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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

MCP Server For ISO27001

How MCP Server For ISO27001 could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How MCP Server For ISO27001 compares in MCP Servers

Where the 62.6 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about MCP Server For ISO27001

AI agent surface

Maintain MCP Server For ISO27001?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers