io.github.gbgplc/lqt

Name: io.github.gbgplc/lqt
Rating: 60 (1 reviews)
Author: io.github.gbgplc

MCPcommunity

v0.6.2io.github.gbgplcUnknownUpdated 1mo agoGitHub

Verify addresses, email addresses, and phone numbers with confidence scores.

Verify addresses, emails, and phone numbers against Loqate's APIs. Get confidence scores, policy-aware recommendations, and full auditability — in one command. Real-time verification decisioning for agents that need to know whether contact data is good enough for the job. lqt verify  ·  lqt parse  ·  lqt mcp 1. Download from the latest release 3. Move it to a directory on your…

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

1mo agoLast update

Package

Authorio.github.gbgplc

LicenseUnknown

Version0.6.2

Sourcemcp-registry

GitHubgbgplc/lqt

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