io.github.OjasKord/bizfile-mcp

Name: io.github.OjasKord/bizfile-mcp
Rating: 60 (1 reviews)
Author: io.github.OjasKord

MCPcommunity

v4.10.17io.github.OjasKordUnknownUpdated 1mo agonpm GitHub

Company intelligence and sanctions screening across 130+ jurisdictions and 328 sanctions lists.

AI-powered KYC, company verification, and sanctions screening Real-time counterparty verification across 210M+ companies in 130+ jurisdictions, with AI risk scoring and sanctions screening against 328 global lists. Built for supplier onboarding agents, payment approval workflows, and AML compliance pipelines. Every unverified counterparty is a liability. The most common failure points — shell…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

1mo agoLast update

Package

Authorio.github.OjasKord

LicenseUnknown

Version4.10.17

Sourcemcp-registry

npmbizfile-mcp

GitHubOjasKord/bizfile-mcp

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface—

Security scan✓ Cleanv4.10.36 · 20d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp