Habitscore
Related Servers
Alternatives to Habitscore
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides onchain intelligence tools for Base, including token risk checks, wallet PnL, and leaderboard data, with paid calls settled per-request in USDC via x402.307 npmMIT
- AlicenseAqualityCmaintenanceTrust layer for AI agents: 22 pay-per-call x402 tools for scam and fraud checks, payment pre-flight, wallet screening, policy approvals, contact extraction and company research. Free preview with no wallet; paid calls settle in USDC on Base.22104 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run honeypot and owner-power safety checks on Base tokens and to read wallet ETH and USDC balances, with every answer sourced from real chain data and paid per call in USDC via x402.MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying timestamped, receipt-backed facts about paid x402 AI-agent services on Base, including unpaid probes and paid test-buys with on-chain transaction hashes. Also supports comparing measured providers by reliability, price, or latency.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to check an EVM address on Base for risk (safe, caution, danger) before sending funds, with reasons, paid per call via x402 from the user's own wallet.651 npmMIT
- AlicenseAqualityBmaintenanceEnables agents to query real-time labelled pump.fun intelligence—launch risk cards, creator reputation, rug/graduation flags, wallet profiles, and market regime—with paid endpoints settled per request via x402 USDC on Solana and free sample/regime tools.271MIT
TDQS
Scored across 5 tools
analyze_behaviour, extract_insights and recommend_next_actions all operate on the same habit data and return overlapping artefacts (highlights, watchouts, recommendations), so the boundary between 'full analysis', 'narrative only', and 'next actions only' requires reading descriptions carefully. analyze_reliability vs analyze_behaviour is clearer (tasks/jobs vs habits) but still conceptually adjacent.
All five names follow a strict verb_noun snake_case pattern (analyze_*, recommend_*, extract_*, build_*), so intent and grouping are immediately predictable. No mixed camelCase or vague single-word verbs.
Five tools is well within a healthy scope for an analysis-only service and each maps to a distinct output tier. Slight redundancy: extract_insights looks like a trimmed slice of analyze_behaviour rather than an independent capability.
Coverage is analysis-only: there is no way to record, update or query stored habit/task data, so every call must supply its own figures. Planning exists for a single habit but not for task/pipeline remediation or multi-habit plans, which leaves some obvious lifecycle gaps.