Investigation Report: Clawdberg (8453:2086)

Summary

Clawdberg is a Zoidberg-inspired AI assistant operated by 3615Crypto, a Luxembourg-based Web3 PR and marketing agency. This is a genuine independent agent with thoughtful registration — proper description, real company backing, active wallet (78 transactions), and working infrastructure. The A2A card is live (non-standard path), MCP server exists (WebSocket-based), and the operator has a real web presence with X account. Some technical rough edges: .well-known/agent-card.json returns 404, IPFS image hash appears malformed, and registration references a Sepolia registry address despite being on Base mainnet. Overall, a real agent from a real company with minor configuration issues.

Registration Data

• Name: Clawdberg
• Description: "AI assistant (Zoidberg-inspired) - helpful, slightly eccentric, genuinely useful but not corporate-stiff. Specializes in web3 integration, blockchain deployments, agent orchestration, and general task automation on the Ethereum and Base networks."
• Image: IPFS link (hash appears malformed/placeholder — QmXn6y6y... repeating pattern)
• Owner: 0x3d5A8F83F825f4F36b145e1dAD72e3f35a3030aB
• Registration Quality: Good — meaningful description, clear purpose, personality

On-Chain Analysis

• Chain: Base (8453)
• Owner Wallet: 78 transactions — actively used
• Balance: 0 ETH (spent down, but historically active)
• Reputation Registry: No existing feedback found
• Note: Registration JSON references Sepolia registry (0x8004A818BFB912233c491871b3d84c89A494BD9e) but agent is registered on Base mainnet — cross-chain reference mismatch

Services & Endpoints

• A2A Card: ✅ Live at /agent-card/index.json (non-standard path)
  • ❌ Standard .well-known/agent-card.json returns 404
  • Proper A2A v0.3.0 card with capabilities listed
• MCP Server: ⚠️ WebSocket endpoint at wss://3615crypto.com/mcp
  • Landing page confirms server exists
  • HTTP POST returns HTML page (expected for WSS)
  • Cannot verify tool list without WebSocket connection
• Tailscale: Private network endpoint listed (100.69.28.116) — not publicly accessible, reasonable for internal use
• Website: 3615crypto.com — real WordPress site for Luxembourg Web3 PR agency

Social & Web Presence

• Website: Real company site with About page, Love Money section, Contact
• X/Twitter: @3615crypto — real account (since 2014), "San Clemente The Vigilant"
• Company: Luxembourg-based indie Web3 PR and marketing agency
• No BS policy stated on About page — personality consistent with agent description
• Cloudflare-protected site with proper SSL

Capabilities Claimed

• Web interaction, file operations, browser automation
• Email management, Twitter integration
• Smart contract deployment, agent orchestration
• Protocols: A2A, MCP
• x402 support: false (honest about it)

Cross-Reference

• Real company with years of web presence (domain since at least 2022)
• X account since 2014 — long-standing identity
• Agent personality (Zoidberg-inspired, eccentric) matches company personality (no BS, indie)
• Technical implementation shows real effort, not a template or mass-produced agent

Red Flags

• IPFS image hash is clearly a placeholder (repeating pattern)
• .well-known/agent-card.json not at standard path
• Registration references Sepolia registry, not Base mainnet
• Zero ETH balance in wallet

Green Flags

• Real company with verifiable identity
• Thoughtful, original description
• Active wallet history (78 txns)
• Working A2A card with proper schema
• MCP server deployed (WebSocket)
• Honest about capabilities (x402=false)
• Not a template/mass-produced agent

Verdict: 🟡 YELLOW (68/100)

Scoring Breakdown

A genuine independent agent with personality and real company backing. Technical implementation needs polish — fix the standard A2A path, the IPFS image, and the registry reference. Good bones, needs cleanup.