mcpbeat Sign in

BLOCKTRUST TrustScan MCP Server

by brnbtech770 Your server? Claim it
answering

BLOCKTRUST TrustScan is answering right now. Last checked 5 min ago.

Trust verification for AI agents: identities, domains, phishing, contacts, Trust Circle, Vault.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 87%
91 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
329 ms
Response time
average over 24h
authentication required
Access
streamable-http

What the code does

We have not read this server's code yet, 36 d ago · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add blocktrust-trustscan --transport http https://blocktrust.tech/mcp/sse
Settings → Connectors → Add custom connector, then paste this address
https://blocktrust.tech/mcp/sse
~/.codex/config.toml
[mcp_servers.blocktrust-trustscan]
url = "https://blocktrust.tech/mcp/sse"
.cursor/mcp.json
{
  "mcpServers": {
    "blocktrust-trustscan": {
      "url": "https://blocktrust.tech/mcp/sse"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "blocktrust-trustscan": {
      "type": "http",
      "url": "https://blocktrust.tech/mcp/sse"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://blocktrust.tech/mcp/sse streamable-http needs auth 241 ms 5 min ago

Alternatives to BLOCKTRUST TrustScan

same job, measured the same way
Trustverdict
by cloudcorprecords

Trust verification for agents and packages: safety scans, signed scores, identity and badges.

246 installs/wk local only
HiveTrust
by srotzin

KYA identity verification, trust scoring, and performance bonds for AI agents

17 tools answering
Trustsource
by surfether

x402-paid domain verification for AI agents — trustscore, SSL, security headers, robots.

63 installs/wk local only
ENTIA Entity Verification
by entia-systems-core

Verified business identity for AI agents: 11.3M entities, EU VAT (VIES), BORME, GLEIF. Free trial.

15 tools answering
A
AgentGraph Trust
by agentgraph-co

Security scanning and trust verification for AI agent tools.

255 installs/wk local only
V
VerifAI
by manhourplan

Email verification and domain intelligence for AI agents, including single and bulk email checks.

7 tools answering
P
Professor Sausages — Trust & Verification
by professorsausages

Email, phone, domain, URL & OFAC verification; phishing and IBAN checks via x402.

12 tools answering
Vaultfire Trust Protocol
by ghostkey316

On-chain trust verification and Street Cred for AI agents. ERC-8004, multi-chain.

56 installs/wk local only

BLOCKTRUST TrustScan — questions

Answers built from our own checks of this server.

Why is there no tool list for BLOCKTRUST TrustScan?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is BLOCKTRUST TrustScan working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 329 ms. The bar chart above shows every period we have measured.
Is BLOCKTRUST TrustScan still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect BLOCKTRUST TrustScan?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does BLOCKTRUST TrustScan need an API key?
Yes. Every time we knock, BLOCKTRUST TrustScan answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is BLOCKTRUST TrustScan?
It answers our handshake in 329 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.