ai.certscore/mcp-light

MCPcommunitylive
v0.2.20ai.certscoreUnknownUpdated 14d agoGitHub

Free website privacy scanner for pre-consent cookies, trackers, consent, policy, and HTTPS/TLS.

Endpoint healthlive
checked 4 days ago · 700ms
100% of the last 4 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). 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 →
14d agoLast update
Package
Authorai.certscore
LicenseUnknown
Version0.2.20
Sourcemcp-registry
GitHubergoveritas1-alt/certscore.ai
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
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 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 16, 2026

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

Tools

Source not readable1mo ago

The repository archive could not be read at scan time (tarball exceeds size cap), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Free website privacy scanner for pre-consent cookies, trackers, consent, policy, and HTTPS/TLS.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.