io.github.Br0ski777/trust-score

MCPcommunitydegraded
v1.1.0io.github.Br0ski777UnknownUpdated 4mo agoGitHub

Trust scoring for domains, wallets, APIs. SSL+DNS+WHOIS+headers. Score 0-100.

Unified trust scoring for domains, wallets, and APIs. Score 0-100 with 5 sub-scores. Powered by x402 micropayments. The trust layer AI agents need before interacting with unknown services. One API call tells you if a domain, wallet, or endpoint is safe. Sub-score | Weight | What it checks | -----------|--------|----------------| SSL/TLS | 25% | Certificate validity, HSTS, expiry, issuer, preload…

Endpoint healthdegraded
checked 10 days ago · last reachable 19 days ago
80% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (sse). 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 →
4mo agoLast update
Package
Authorio.github.Br0ski777
LicenseUnknown
Version1.1.0
Sourcemcp-registry
GitHubBr0ski777/trust-score-x402
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 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

No tool declarations found in the source3mo ago

Forge read 5 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Unified trust scoring for domains, wallets, and APIs. Score 0-100 with 5 sub-scores. Powered by x402 micropayments. The trust layer AI agents need before interacting with unknown services. One API call tells you if a domain, wallet, or endpoint is safe. Sub-score | Weight | What it checks | -----------|--------|----------------| SSL/TLS | 25% | Certificate validity, HSTS, expiry, issuer, preload | WHOIS | 25% | Domain age, registrar reputation, expiry date, suspicious TLDs | Security Headers |…

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.