BLOCKTRUST TrustScan

io.github.brnbtech770Published by GitHub account brnbtech770v1.0.0Updated Oct 27, 2026

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

The publisher's own server: scan.mx Email Diagnostics

VerifiedStreamable HTTPWeb executableSecurity & MonitoringAI & ML

Overview

AI-generated overview

Remote MCP endpoint that gives an AI assistant trust verification for agents, domains, phishing checks, contacts, Trust Circle and Vault.

What you can do
  • Verify identities and domains for trust signals
  • Check links or senders for phishing indicators
  • Look up and manage contacts
  • Work with Trust Circle relationships
  • Access Vault-related trust data
When to use it
Useful when an assistant needs to vet an agent, domain or contact before acting on it, or when you want phishing and trust checks built into an agent workflow.
Requirements
A remote streamable HTTP endpoint at blocktrust.tech; no local package. A bearer API key is required, sent in the Authorization header, obtained from the provider's dashboard extension page.
Before you install
Requires a bearer API key in the Authorization header, so the credential is shared with the provider's service. The tool list is not published, so what the server can read or change is unclear; confirm whether Vault and contact operations write data before connecting.

Installation

In SourceWeft

  1. Open BLOCKTRUST TrustScan in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.brnbtech770%2Fblocktrust-trustscan/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "blocktrust-trustscan": {
      "type": "http",
      "url": "https://blocktrust.tech/mcp/sse",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Scan integrations