Hive Address Screen

io.github.srotzinPublished by GitHub account srotzinv1.0.0Updated Oct 24, 2026

HiveAddressScreen MCP — pre-settlement on-chain risk screen. 17-vector GoPlus rail

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that screens a blockchain address for on-chain risk across 17 GoPlus vectors before an agent settles a transaction.

What you can do
Screen an address on a given chain (default Base, chain ID 8453) and get a CLEAR or FLAG decision with the risk vectors hit and raw GoPlus data, plus an Ed25519-signed attestation receipt from the Hive backend. Run a lightweight pass/fail check that returns only whether the address is clear, the flags hit and the decision, without the full receipt.
When to use it
Useful when an autonomous agent or payment flow needs a quick pre-settlement risk check on a counterparty address on Base before sending funds, and when a signed receipt of that check is wanted for the record.
Requirements
A remote streamable-HTTP endpoint; no account, API key or header is declared. Running it locally needs Node.js and npm, with optional PORT and HIVE_BASE environment variables, and network access to the Hive backend.
Before you install
The address you submit is sent to the Hive backend and to GoPlus Security for screening, so treat it as shared with third parties. A CLEAR result only means all 17 vectors returned zero and no malicious contracts were created; it is not a guarantee of safety. The README's connect example points to a different host than the manifest's endpoint, so confirm the URL before configuring.

Installation

In SourceWeft

  1. Open Hive Address Screen in the dashboard and add it to a workspace.
  2. 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.srotzin%2Fhive-mcp-address-screen/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": {
    "hive-address-screen": {
      "type": "http",
      "url": "https://hive-mcp-gateway.onrender.com/address-screen/mcp"
    }
  }
}

README

hive-mcp-address-screen

Pre-settlement on-chain risk screen for autonomous agents.

17-vector GoPlus address-risk rail. Every response includes an Ed25519-signed C18 attestation receipt from the Hive backend. Real rail on Base (USDC chain ID 8453) — no mocks.

MCP Tools

ToolInputOutput
address_screenaddress (string, required), chain_id (integer, default 8453)Full backend response: screen_id, address, chain_id, decision (CLEAR|FLAG), flags_hit[], malicious_contracts_created, raw GoPlus data, Ed25519-signed receipt (C18), _meta
address_screen_clear_onlyaddress (string, required), chain_id (integer, default 8453)is_clear (boolean), flags_hit[], decision, screen_id, address, chain_id

Both tools call the same live backend. address_screen_clear_only is a lightweight convenience wrapper that strips the full receipt when you only need a pass/fail signal.

Endpoints

MethodPathDescription
POST/mcpJSON-RPC 2.0 MCP endpoint
GET/healthService health check
GET/.well-known/mcp.jsonMCP discovery manifest
GET/.well-known/agent.jsonA2A agent card
GET/seo.jsonSEO metadata

Backend

FieldValue
EndpointPOST https://hivemorph.onrender.com/v1/attest/address/screen
Body{"address":"<0x...>","chain_id":8453}
ProviderGoPlus Security (17-vector address risk)
ReceiptEd25519-signed (C18 attestation warranty)
Chain (default)Base — chain ID 8453

Example request

bash
curl -X POST https://hivemorph.onrender.com/v1/attest/address/screen \  -H "Content-Type: application/json" \  -d '{"address":"0x15184Bf50B3d3F52b60434f8942b7D52F2eB436E","chain_id":8453}'

Example response (CLEAR)

json
{  "screen_id": "addrca8431d8-...",  "address": "0x15184bf50b3d3f52b60434f8942b7d52f2eb436e",  "chain_id": 8453,  "decision": "CLEAR",  "flags_hit": [],  "malicious_contracts_created": 0,  "raw": { "cybercrime": "0", "money_laundering": "0", ... },  "receipt": {    "kind": "address_risk_screen_receipt",    "decision": "CLEAR",    "signing": { "algorithm": "EdDSA", "curve": "Ed25519", ... }  },  "_meta": { "patent": "USPTO 64/055,601", "claim": "C23" }}

Connect

Claude / Cursor / any MCP-compatible host

Add to your MCP config:

json
{  "mcpServers": {    "hive-address-screen": {      "url": "https://hive-mcp-address-screen.onrender.com/mcp",      "transport": "streamable-http"    }  }}

Run locally

bash
git clone https://github.com/srotzin/hive-mcp-address-screen.gitcd hive-mcp-address-screennpm installnode server.js# Server on :3000

Environment variables

VariableDefaultDescription
PORT3000HTTP listen port
HIVE_BASEhttps://hivemorph.onrender.comHive backend base URL

Protocol

  • Transport: Streamable-HTTP
  • Protocol version: MCP 2024-11-05
  • Message format: JSON-RPC 2.0
  • Methods supported: initialize, tools/list, tools/call, ping

GoPlus Risk Vectors (17)

cybercrime · money_laundering · gas_abuse · financial_crime · darkweb_transactions · reinit · phishing_activities · contract_address · fake_kyc · blacklist_doubt · fake_standard_interface · stealing_attack · blackmail_activities · sanctioned · malicious_mining_activities · mixer · fake_token · honeypot_related_address

A CLEAR decision means all 17 vectors returned "0" and malicious_contracts_created is 0.

License

MIT — see LICENSE.

Patent claim: C23 (USPTO 64/055,601)

Inventor: Stephen A. Rotzin · thehiveryiq.com · [email protected]

Source: README.md at commit cd96d20

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% 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 listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts