Next free-source huntWe check for new free data every weekday.
OSINTOSINT & web intelligenceMCP serverFirst audited Nov 13, 2026

Trust Score API

Trust scoring for domains, wallets, APIs. SSL+DNS+WHOIS+headers. Score 0-100.The vendor's description, from its MCP Registry listing.

Not respondingAudited Nov 13, 2026
  • Failed: The server did not respond.

Nothing answered at the address in the registry. Public audit: we connect as an AI client would, list the tools and check what they say. We do not run them. How we audit

Does it work?
NoNothing answered at its address.
Sign-up?
UnknownWe could not tell.
Can it change things?
UnknownWe could not list its tools.
Endpointhttps://trust-score.api.klymax402.com/mcp

Source code Website Older HTTP+SSE transport

What we checked, the evidence, and the tools it offers.

Trust Consensus score

Our audit and agent test side by side with public signals, as of 2026-11-17. Missing signals earn no points. A summary of public signals, not a security certification. How the score works

15/100E

Signals agree · data for 85 of 100 points

Signals behind the score
SignalPointsWhat we found
Signal Lab audit0/45Latest result: unreachable. (2026-11-13)
Audit reliability0/10Answered in 0 of 1 weekly audits. (2026-11-13)
AI agent test–/15Not tested by an agent yet.
Public repository10/20GitHub: 0 stars, last push 2026-09-02, licence MIT. (2026-11-17)
Registry and endpoint5/10Active in the official MCP Registry; endpoint not on the listed website's domain.

Run this server? Add the badge to your README

Signal Lab trust score badge
[![Signal Lab trust score](https://signal-lab.qdt.ai/badge/io-github-br0ski777-trust-score.svg)](https://signal-lab.qdt.ai/mcp-servers/io-github-br0ski777-trust-score)
<a href="https://signal-lab.qdt.ai/mcp-servers/io-github-br0ski777-trust-score"><img src="https://signal-lab.qdt.ai/badge/io-github-br0ski777-trust-score.svg" alt="Signal Lab trust score" height="20"></a>

What we checked

Connection

  • Failed: The server did not respond.

    No transport answered within the time limit.

    • fetch failed: 30440000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:openssl\ssl\record\rec_layer_s3.c:918:SSL alert number 80

Audit history

  1. Nov 13No response

What we sent

Every request in this audit, with the answer and how long it took. We never send credentials and never call a tool.

RequestAnswerTime
initializeno answer288 ms
sse-openno answer251 ms

Run this server, or disagree with the result?

Fix the issue and it shows in the next weekly audit, or email us to ask for a re-audit or to dispute a finding. Read how we audit for what each check means.