io.github.aokings/thth
Related Servers
Alternatives to io.github.aokings/thth
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables read-only exploration of community content such as posts, topics, games, comments, user profiles, notifications, discounts, news, and trending items through MCP tools or a CLI.MIT
- FlicenseNot gradedqualityCmaintenanceEnables read-only Meta Ads reporting and diagnostics, plus safe, preview-before-apply mutations such as campaign creation, duplication, targeting replacement, and attribution changes.-
- AlicenseBqualityCmaintenanceEnables an MCP client to inspect sites, warm runs and their results, cache status reports and schedules through the API, and — only when writes are explicitly enabled and confirmed — to trigger or cancel warm runs and create, update or delete schedules. Read-only operation is the safe default, with API-key scopes, redaction, idempotency and no retries or redirects.9Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables read access to business data and creation of immutable action proposals that require separate human approval before idempotent execution with an audit trail.Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables users to inspect workspace-scoped findings and hosted runs, list workspaces, and prepare or, after explicit confirmation, start or rerun existing hosted reviews without exposing raw diffs, full reports, artifacts, screenshots, credentials, or prompt text.2 npm-
- AlicenseAqualityBmaintenanceEnables AI clients to check status, read non-secret settings, schedules, and subject rules, and—when explicitly allowed—update settings and existing subject rules. It also supports local diagnostic workflows while excluding passwords, credentials, arbitrary SQL, files, and shell commands.131MIT
TDQS
Scored across 15 tools
Most tools have a distinct focus, but several clusters overlap: thth_queue, thth_board, and operations_handoff all list pending/inflight/type states, while before_you_post, after_you_posted, and analytics_report all return activity metrics with counts and periods. The descriptions clarify intent, but an agent could easily select the wrong tool without reading carefully.
Naming is inconsistent: some tools use the thth_ prefix and some do not, with no uniform convention. The style mixes nouns (thth_queue), verb phrases (thread_read), questions (who_is_this), and past-tense phrases (after_you_posted), making patterns unpredictable.
Fifteen tools is at the upper edge of a reasonable count, and each covers a specific read-only aspect of the posting workflow. A few could potentially be consolidated, but the count is not excessive for the apparent scope.
The surface covers the core read-only lifecycle: queue, preview, pre/post metrics, thread reading, topic context/evaluate/decision, linting, board status, handoff state, study/analytics reports, and contact history. There are no write/approve/sync tools, but the descriptions consistently mark those as intentional exclusions rather than dead ends.