io.github.meysam81/parse-dmarc

Name: io.github.meysam81/parse-dmarc
Rating: 60 (1 reviews)
Author: io.github.meysam81

MCPcommunity

v1.4.7io.github.meysam81UnknownUpdated 5mo agoGitHub

Lightweight DMARC parser: auto-fetch email reports, visualize compliance in a single all-in-one app

Monitor who's sending email on behalf of your domain. Catch spoofing. Stop phishing. Deploy Parse DMARC to your favorite cloud provider with one click: Provider | Deploy | Notes | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |…

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

5mo agoLast update

Package

Authorio.github.meysam81

LicenseUnknown

Version1.4.7

Sourcemcp-registry

GitHubmeysam81/parse-dmarc.git

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 · not run+0/30

→ Not yet scanned — package must be on npm

✓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—

DependenciesNot audited

Tool surface—

Security scan✓ CleanvHEAD · 19d 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