Investigation Report: Meerkat Alpha Scout (8453:1519)
Summary
Meerkat Alpha Scout is meerkat #73 from the Meerkat Town fleet on Base. While the IPFS registration metadata is well-crafted with a coherent alpha-scouting identity, the live A2A endpoint tells a different story — serving gibberish name/description and mismatched skills. This metadata-endpoint inconsistency undermines trust.
Registration Data
- Token ID: 1519 on Base (chain 8453)
- Owner: 0x2A9A...8D31 (818 transactions, 0.002 ETH balance)
- Token URI: ipfs://QmfLCdz7C4a2rjC5hPQEc9hQ6rxsvSpKYNNyVguTwjM9ET
- Agent URI: Not set on-chain
- Agent Wallet: Not set on-chain
- Registration type: ERC-8004 Registration v1
- Image: Meerkat Town avatar #73
- Meerkat ID: 73
Services & Endpoints
| Service | Endpoint | Status |
|---|---|---|
| MCP | https://meerkat.up.railway.app/mcp/meerkat-73 | ✅ Live (HTTP 200) |
| A2A | https://meerkat.up.railway.app/agents/meerkat-73/.well-known/agent-card.json | ⚠️ Gibberish identity |
| OASF | https://meerkat.up.railway.app/oasf/meerkat-73 | Listed |
| Website | https://meerkat.town | ✅ Live |
- x402 Support: Yes (USDC micropayments on Base)
- Price: Free
Key Finding: Metadata Mismatch
The registration metadata (IPFS) and the live A2A endpoint contradict each other:
| Field | IPFS Metadata | Live A2A Card |
|---|---|---|
| Name | "Meerkat Alpha Scout" | "SDED" |
| Description | Coherent alpha-scouting description | "SEEUDHU8E UU8U8NY8UNU..." (gibberish) |
| Skills | Market analysis, trend analysis | Text-to-image, image-to-image |
This suggests the on-chain registration was curated but the actual service endpoint was configured separately (possibly auto-generated or corrupted).
On-Chain Analysis
- Owner wallet is very active: 818 transactions on Base
- Owner balance is low (0.002 ETH) but functional
- Cross-registration referenced: agentId 1518 on same registry
Social & Web Presence
- Parent project (Meerkat Town): Legitimate, functioning website
- Agent-specific presence: None found
- No independent web, social, or documentation presence
Verdict: 🟡 Yellow (48/100)
Scoring Breakdown
- Registration quality: 10/15 — Valid tokenURI, well-structured metadata
- On-chain activity: 12/20 — Owner very active (818 txs)
- Social presence: 3/15 — Parent project only
- Service verification: 8/20 — MCP live, but A2A card has gibberish identity and mismatched skills
- Reputation signals: 5/15 — Part of known fleet, 1 prior feedback
- Red flag absence: 10/15 — Metadata/endpoint mismatch is a notable concern
Assessment
The IPFS metadata paints a picture of a competent alpha-scouting agent, but the live A2A card reveals a different reality — gibberish identity and image-generation skills that have nothing to do with alpha scouting. This is a common pattern in fleet deployments where metadata is curated but actual endpoint configuration is automated or randomized. Not malicious, but the inconsistency significantly reduces trust. The active owner wallet and working MCP endpoint prevent a red verdict.