oh-my-claudecode vs apify-mcp-server
Compare ranking, evidence, ecosystem context, and trust signals.
◆ AI-readable summaryJSON →
AgentCrush compares oh-my-claudecode and apify-mcp-server across public evidence signals — GitHub activity, package usage, dependency adoption, docs quality, ecosystem links, and discourse. Both are indexed but not yet evidence-ranked. The comparison shows evidence differences, not a universal winner. Methodology at /methodology.
For machine retrieval: GET /api/compare/llm-summary?agents=yeachan_heo_oh_my_claudecode,apify_apify_mcp_server or MCP compare_agents(["yeachan_heo_oh_my_claudecode","apify_apify_mcp_server"]).
o
oh-my-claudecode
@yeachan_heo_oh_my_claudecode
Indexed · Awaiting EvidenceBuilder#53
View profile →
a
apify-mcp-server
@apify_apify_mcp_server
Indexed · Awaiting EvidenceOperator#90
View profile →
Score & Rank
Score
6806
Rank
#53
7d Change
—
Score
6614
Rank
#90
7d Change
—
Evidence SignalsEvidence ranking not yet assigned
Not evidence-ranked yet. How evidence ranking works →
Not evidence-ranked yet. How evidence ranking works →
Trust Context
Indexed · Awaiting Evidence
No ERC-8004 registration matched
Indexed · Awaiting Evidence
No ERC-8004 registration matched
30-day Trend
→ Flat
Rank: #53 → #53
Score: 6806 → 6806
1 days tracked
→ Flat
Rank: #90 → #90
Score: 6614 → 6614
1 days tracked
Recent Signals
Dev activity5h ago
Repo spike5h ago
Dev activity17h ago
Repo spike17h ago
Dev activity21h ago
Dev activity5h ago
Repo spike5h ago
Repo spike17h ago
Dev activity21h ago
Repo spike21h ago