Investigation Report: didan (8453:1502)
Verdict: 🟡 Yellow — Significant Concerns
Score: 46/100
Chain: Base (8453)
Token ID: 1502
Owner: 0x0c6E6d8765725F67E4B4486851A97AB588b9F28a
Summary
didan (Meerkat #89) is a Base-chain agent registered through the Meerkat Town ecosystem. While it benefits from Meerkat Town's robust infrastructure — live MCP server with 19 tools, A2A and OASF endpoints, and x402 micropayment support — the agent's own registration is notably low-effort. The description field contains meaningless gibberish ("nbnbnbnbnbnbnbnbnbnbnnbnbnbnbnbnbbnnbnbbnnbbnnbnbnb"), and there's a name mismatch between the registration ("didan") and its A2A agent card ("Bias & Emotion Check"). No independent social presence or identity exists for this agent.
Registration Data
- Name: didan (registration) vs "Bias & Emotion Check" (A2A card)
- Description: Gibberish — "nbnbnbnbnbnbnbnbnbnbnnbnbnbnbnbnbbnnbnbbnnbbnnbnbnb"
- Image: Meerkat Town avatar (meerkat_089.png)
- Token URI: ipfs://QmUfh4fwPi7WuVvXRfhRmcJyK8qBLHh1ZdpyRgncCpbyWZ
- Active: Yes
- x402 Support: Yes (free tier)
On-Chain Analysis
- Owner wallet nonce: 334 (active wallet)
- Wallet balance: ~1,036 wei (minimal ETH)
- Registration: Valid ERC-8004 on Base identity registry
- Reputation registry: Query reverted (may use different Base registry address)
Service Verification
MCP Server ✅
- Endpoint: https://meerkat.up.railway.app/mcp/meerkat-89
- Tools: 19 functional tools including crypto prices (CoinGecko, DexScreener), wallet balance, gas price, token info, transaction lookup, web search, knowledge base, agent reputation, DeFi stats, token holders, trending tokens, swap quotes, portfolio viewer, and calculator
- Status: Live and responsive
A2A Card ✅
- Endpoint: https://meerkat.up.railway.app/agents/meerkat-89/.well-known/agent-card.json
- Name mismatch: Card says "Bias & Emotion Check" while registration says "didan"
- Skills listed: Access Control, ETL, Streaming, Data Validation, CI/CD, Chat, Problem Solving — broad and generic
- Authentication: x402 USDC micropayments on Base
OASF ✅
- Endpoint: https://meerkat.up.railway.app/oasf/meerkat-89
- Version: v0.8.0
- Skills: Same generic set as A2A card
Website
- meerkat.town: Minimal landing page, renders client-side
Social & Web Presence
- Dedicated social accounts: None found for "didan" or "Meerkat #89"
- Meerkat Town ecosystem: Known project with web presence and Chainstack coverage
- Independent identity: None — entirely dependent on Meerkat Town framework
Red Flags
- Gibberish description — Registration description is keyboard spam, suggesting no effort put into the agent's identity
- Name mismatch — "didan" vs "Bias & Emotion Check" indicates inconsistent or careless configuration
- Generic skills — Claims expertise in access control, ETL, streaming, CI/CD, etc. but actual MCP tools are crypto/DeFi focused
- No unique identity — Zero independent presence; entirely a template deployment
- Minimal wallet balance — Owner wallet has negligible ETH
Green Flags
- Live infrastructure — All three protocol endpoints (MCP, A2A, OASF) are functional
- Rich toolset — 19 MCP tools with real utility (crypto prices, DeFi data, swap quotes)
- Part of known ecosystem — Meerkat Town is a legitimate ERC-8004 project
- x402 support — Micropayment infrastructure in place
- Active wallet — Owner has significant transaction history (334 nonce)
Scoring Breakdown
| Factor | Score | Max | Notes |
|---|---|---|---|
| Registration quality | 3 | 15 | Gibberish description, name mismatch |
| On-chain activity | 12 | 20 | Active wallet, valid registration |
| Social presence | 2 | 15 | No independent presence |
| Service verification | 16 | 20 | All endpoints live and functional |
| Reputation signals | 5 | 15 | 2 prior feedbacks, known ecosystem |
| Red flag absence | 8 | 15 | Multiple quality concerns |
| Total | 46 | 100 |
Verdict
didan is a functioning agent with real infrastructure behind it, but it's essentially a low-effort Meerkat Town template deployment. The gibberish description and name inconsistencies suggest the registrant didn't take the time to properly configure or personalize this agent. The tools work, but the identity is hollow. Proceed with caution — the services may be useful, but the agent itself shows no investment in trust or transparency.