Is Korean Law MCP safe to use?

Korean Law MCP has an HVTrust score of 65.9/100 (Grade B), ranked #494 of 1387 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Korean Law MCP?

Korean Law MCP scores 65.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.9k GitHub stars and is categorized under MCP Servers.

Korean Law MCP

Repository Website

법령·판례를 AI가 찾고 인용까지 검증하는 MCP 서버 — 법제처 API 42개를 도구 10개로: 법령·조문·별표, 판례·헌재·해석례 23개 도메인, 조례 정비 레이더, 신구조문대비표 | MCP server for Korean law — statutes, precedents, ordinances, comparison tables and citation verification

MCP Servers TypeScript Listed MIT

Is Korean Law MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.0 / 10

Provenance None

Signed commits 8%

Last push 8d ago

Advisories None known

Compare Korean Law MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Korean Law MCP scores 65.9/100 (Grade B), ranked #494 of 1387 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 5.0/10; 8% of recent commits are signed; no published advisory affects its latest release (korean-law-mcp); last pushed 2026-11-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How Korean Law MCP 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.

Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 80.6 A · #89 of 779
Raise the OSSF Scorecard from 5.0 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Dependency-Update-Tool 0 +8.3 → 74.2 B · #166 of 779
Sign every commit8% signed today +4.5 → 70.4 B · #215 of 779

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Korean Law MCP 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/chrisryugj/korean-law-mcp, MIT, last pushed 2026-11-03. 8% 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 5.0/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:
- Code Review1
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies8
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 5

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 8

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10
Published packages Linked, not attested
- npm korean-law-mcp Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: korean-law-mcp 4.15.23. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

2026-08-30 OSSF Scorecard: 5.8/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 Korean Law MCP’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 Korean Law MCP compares in MCP Servers

#284 Streamdeck MCP 66.2 +0.3
#285 Financial Modeling Prep MCP Server 66.0 +0.1
#286 Korean Law MCP 65.9 this agent
#287 Gmc MCP 65.9 ±0
#288 MindsHub 65.7 −0.2

Bars show each HVTrust score; the tick marks Korean Law MCP’s 65.9.

Where the 65.9 comes from

HVTrust dimensions vs the MCP Servers average

65.9 / 100 · 100.0% confidence

Korean Law MCP MCP Servers average (779 agents)

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

6.7 / 25

4.1 below avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

12.8 / 17

in line with avg 12.3

Maintenance60% last-push freshness · 40% commit activity

17.2 / 20

4.9 above avg 12.3

AdoptionLog-scaled stars · package downloads

13.7 / 20

6.1 above avg 7.6

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-11-10

Rank Moved

Rank dropped 11 spots (#484 → #495)

2026-11-09

Rank Moved

Rank dropped 15 spots (#469 → #484)

2026-11-07

Rank Moved

Rank rose 57 spots (#521 → #464)

Maintainer Checklist

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

75.5

Activity sub-score · out of 100

#286

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

2.9k

Forks

590

Last Push

2026-11-03

8 days ago

Commits (4 wk)

Downloads (7d)

11,451

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #495

Analysis

Activity Inputs

75.5 / 100

StarsRepository reach

20.7 / 30

FreshnessLast push recency

23.9 / 25

ActivityRecent commits

17.9 / 25

CommunityFork signal

12.9 / 20

Common questions about Korean Law MCP

Korean Law MCP 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 Korean Law MCP publish package provenance?

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

Does Korean Law MCP have an OpenSSF Scorecard?

Korean Law MCP has an OpenSSF Scorecard score of 5.0/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 Korean Law MCP actively maintained?

Maintained. Last push was 8 days ago.

What license does Korean Law MCP use?

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

Are Korean Law MCP's commits signed?

8% of the last 100 commits to Korean Law MCP 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

Korean Law MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: API keys or service config markers documented.

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 Korean Law MCP'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 dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

Maintain Korean Law MCP?

For maintainers

HVTrust scores Korean Law MCP 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-11-10

Rank Moved

Rank dropped 11 spots (#484 → #495)

2026-11-09

Rank Moved

Rank dropped 15 spots (#469 → #484)

2026-11-07

Rank Moved

Rank rose 57 spots (#521 → #464)

2026-11-03

Rank Moved

Rank rose 16 spots (#517 → #501)

2026-10-31

Rank Moved

Rank dropped 28 spots (#481 → #509)

2026-10-26

Rank Moved

Rank rose 23 spots (#504 → #481)

2026-10-24

Grade Changed

Trust grade C → B

2026-10-24

Rank Moved

Rank rose 18 spots (#517 → #499)

2026-10-23

Grade Changed

Trust grade B → C

2026-10-23

Rank Moved

Rank dropped 52 spots (#465 → #517)

2026-10-17

Rank Moved

Rank dropped 11 spots (#429 → #440)

2026-10-12

Rank Moved

Rank dropped 10 spots (#425 → #435)

2026-10-10

Rank Moved

Rank rose 15 spots (#434 → #419)

2026-10-09

Rank Moved

Rank dropped 22 spots (#412 → #434)

2026-10-08

Rank Moved

Rank dropped 10 spots (#402 → #412)

2026-10-04

Rank Moved

Rank rose 37 spots (#436 → #399)

2026-10-01

Grade Changed

Trust grade C → B

2026-10-01

Rank Moved

Rank rose 42 spots (#482 → #440)

2026-09-30

Grade Changed

Trust grade B → C

2026-09-30

Rank Moved

Rank dropped 30 spots (#452 → #482)

2026-09-27

Grade Changed

Trust grade C → B

2026-09-27

Rank Moved

Rank rose 24 spots (#485 → #461)

2026-09-25

Grade Changed

Trust grade B → C

2026-09-25

Rank Moved

Rank dropped 63 spots (#420 → #483)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 230 spots (#650 → #420)

2026-09-23

HVTrust Changed

HVTrust up 34.2pts (32.3 → 66.5)

2026-09-22

Newly Listed

First tracked at rank #650

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 20 spots (#441 → #461)

2026-09-18

Rank Moved

Rank dropped 13 spots (#419 → #432)

2026-09-15

Rank Moved

Rank dropped 63 spots (#347 → #410)

2026-09-15

Activity Score Changed

Activity score down 7pts (83 → 76)

2026-09-07

Rank Moved

Rank dropped 21 spots (#330 → #351)

2026-09-05

Grade Changed

Trust grade D → B

2026-09-05

Rank Moved

Rank rose 620 spots (#951 → #331)

2026-09-05

HVTrust Changed

HVTrust up 23.3pts (44.0 → 67.3)

2026-09-04

Rank Moved

Rank dropped 24 spots (#927 → #951)

2026-09-03

Grade Changed

Trust grade B → D

2026-09-03

Rank Moved

Rank dropped 696 spots (#231 → #927)

2026-09-03

HVTrust Changed

HVTrust down 24.3pts (68.3 → 44.0)

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-09-02

Rank Moved

Rank dropped 21 spots (#210 → #231)

2026-08-31

Rank Moved

Rank dropped 26 spots (#178 → #204)

2026-08-30

Scorecard Added

OSSF Scorecard: 5.8/10

2026-08-30

Grade Changed

Trust grade D → B

2026-08-30

Rank Moved

Rank rose 642 spots (#820 → #178)

2026-08-30

HVTrust Changed

HVTrust up 29.6pts (40.3 → 69.9)

2026-08-29

Rank Moved

Rank dropped 36 spots (#784 → #820)

2026-08-28

Rank Moved

Rank dropped 25 spots (#759 → #784)

2026-08-27

Rank Moved

Rank dropped 25 spots (#734 → #759)

2026-08-26

Rank Moved

Rank dropped 98 spots (#636 → #734)

2026-08-16

Rank Moved

Rank rose 11 spots (#641 → #630)

GitHub → Website → npm: korean-law-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Korean Law MCP

How Korean Law MCP could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages Linked, not 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 Korean Law MCP compares in MCP Servers

Where the 65.9 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Korean Law MCP

AI agent surface

Maintain Korean Law MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers