← Registry

Productivity

trychainrm.com

Resolves wallet addresses to public identities and manages contact records for CRM enrichment.

1 endpoint24 known toolsFirst detected August 7, 2026Last detected August 7, 2026

ENDPOINT 1

https://app.trychainrm.com/mcp

No auth detected

MCP server metadata

Name
ChainBD
Version
2026-07-19
Capabilities
tools
Server instructions

ChainBD: resolve wallets to people, score them on-chain, orchestrate approval-gated outreach. Outreach is queue-only; a human approves every send. Call the whoami-style tools first if unsure of scopes.

Known tools 24

identity_community_lookup

Ask the shared network what it already knows about a wallet (identity, entity, tracked-by-N).

Inferred read-only
identity_resolve_wallet

Resolve a wallet to its public identity: ENS name + records (Twitter, Telegram, email), Farcaster, Lens.

Potential side effects
identity_save_contact

Create a CRM contact from a resolved wallet identity and link the wallet.

Potential side effects
identity_enrich_contact

Propose gap-filling fields for a contact from identity matches + connected providers.

Inferred read-only
signals_attach_wallet

Attach a wallet/contract to a contact or company (60+ EVM chains).

Inferred read-only
signals_sync_wallet

Refresh signals: native balance, sent-tx count, token count, EOA-vs-contract, first/last active, plus USD treasury (Mobula) and named entity (Nansen/Arkham) if connected.

Inferred read-only
signals_list_wallets

List wallets with cached signals and the tracked-by-N-desks network signal.

Inferred read-only
graph_get

Nodes (wallets) + edges (direct transfers = fact, shared counterparties = heuristic) + cluster stats.

Inferred read-only
graph_rebuild

Recompute edges from cached signals.

Inferred read-only
graph_community_directory

Most-tracked entities across the whole ChainBD network.

Inferred read-only
graph_community_stats

How many wallets/entities the shared network knows.

Inferred read-only
graph_export_audience

Export resolved reachable handles/emails from your wallets for outreach or ad targeting.

Inferred read-only
outreach_queue

Queue outreach items.

Inferred read-only
outreach_pending

Items awaiting human approval.

Inferred read-only
outreach_log

What has been sent, held, or failed.

Inferred read-only
crm_list_contacts

List/search contacts.

Inferred read-only
crm_create_contact

Create a contact.

Potential side effects
crm_enrich_bulk

Run the enrichment waterfall over many contacts at once.

Inferred read-only
crm_list_companies

List companies.

Inferred read-only
crm_pipeline_stages

Pipeline stages.

Inferred read-only
crm_opportunities

Deals/opportunities in the pipeline.

Inferred read-only
crm_tasks

AI-detected tasks (meetings, follow-ups, deadlines) from chats.

Inferred read-only
connectors_list

List connectors (HubSpot, Apollo, Clay, HeyReach, X, Slack, On-Chain/Etherscan, Mobula, Nansen, Arkham) and their status.

Potential side effects
connectors_health

Re-validate every connected connector.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.chainbd]
url = "https://app.trychainrm.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "chainbd": {
      "type": "http",
      "url": "https://app.trychainrm.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: chainbd
Remote MCP URL: https://app.trychainrm.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "chainbd": {
      "url": "https://app.trychainrm.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "chainbd": {
      "type": "http",
      "url": "https://app.trychainrm.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "chainbd",
  "transport": "streamable-http",
  "url": "https://app.trychainrm.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.