screenverity-mcp

Name: screenverity-mcp
Author: io.github.williamblakecunningham-max

MCPcommunity

v0.2.1io.github.williamblakecunningham-maxUnknownUpdated 1mo agonpm GitHub

Free U.S. exclusion, debarment and licence screening with a signed receipt of the lists checked.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

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

1mo agoLast update

Package

Authorio.github.williamblakecunningham-max

LicenseUnknown

Version0.2.1

Sourcenpm+mcp-registry

npmscreenverity-mcp

GitHubwilliamblakecunningham-max/screenverity-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

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

—Ed25519 publish signature+0/5

→ 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>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

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

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 0 resolved · none vulnerable

Tool surface3 tools · none privileged

Security scan✓ Cleanv0.2.1 · 22d agoHow well does this scan work?

EvalsNone

IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

3 tools · none privileged

Statically extracted from the published packagev0.2.1 · 22d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

screenScreen a person or organization against maintained U.S. exclusion/debarment and selected license lists.

Screen a person or organization against maintained U.S. exclusion/debarment and selected license lists.

No input schema was published for this tool.

sourcesList exclusion/license sources currently loaded by ScreenVerity: id, jurisdiction, coverage (full|partial),

List exclusion/license sources currently loaded by ScreenVerity: id, jurisdiction, coverage (full|partial),

No input schema was published for this tool.

verify_receiptVerify an Ed25519 ScreenVerity receipt against the server public key. Pass the receipt plus the original

Verify an Ed25519 ScreenVerity receipt against the server public key. Pass the receipt plus the original

No input schema was published for this tool.

3 of 3 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Free U.S. exclusion, debarment and licence screening with a signed receipt of the lists checked.

Keywords

mcp

Alternatives

Comparing tool surfaces…

screenverity-mcp

Tools

Tools exposed

Dependency tree