abliteration-mcp
Related Servers
Alternatives to abliteration-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to look up facts about notable machine-learning models — organization, release date, parameter count, training-compute (FLOP) estimate, hardware and accessibility — by name, and to search or aggregate them by organization, domain, year, or compute threshold. Supports filtering the dataset newest-first and producing per-year training-compute trends, keylessly and without authentication.489 npmMIT
- AlicenseAqualityBmaintenanceRead-only MCP server exposing AGmind Systems Lab's measured local-LLM benchmark claims (TTFT, inter-token latency, task success, etc.) on AMD Strix Halo and DGX Spark hardware via search, claim lookup, and measured-combination listing tools.34Apache 2.0
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server for the July 2026 survey of AI in open-source design systems, enabling agents to query 19 systems' affordances, coercion techniques, and platform data via 9 tools, 2 resources, and 2 prompts.14-
- AlicenseBqualityCmaintenanceMCP server exposing the Psychopathia Machinalis diagnostic framework (79 conditions) — differential diagnosis of AI dysfunctions via 11 read-only tools.11MIT
- AlicenseAqualityDmaintenanceAn MCP server that turns the Hugging Face Hub into a conversational model picker with a tool-use eval harness to prove the agent actually uses it correctly.5MIT
- AlicenseBqualityBmaintenancemnemo — an MCP server for agent memory with a first-class correction & erasure channel (revert, lineage-aware retraction, tamper-evident deletion receipts). Zero dependencies, 12 tools over stdio135747 PyPI8MIT
TDQS
Scored across 18 tools
Most tools have clearly distinct resource+action purposes (list/get/search pairings across authors, models, methods, datasets, indices). The main overlap is the deletion family (list_delisted vs list_deletions vs get_deletions_summary) and the download pair (get_download_anomalies vs get_download_history), but the descriptions differentiate them well enough for an agent to choose correctly.
Consistent verb_noun convention throughout: list_*, get_*, search_* across all 18 tools. Minor adjective-as-noun case in list_delisted, but it reads naturally and matches the pattern. No camelCase or style mixing.
18 tools is on the heavier side but each maps to a distinct route/resource of a genuinely broad data API (models, authors, methods, datasets, indices, timeline, deletions, README drifts, download anomalies). Nothing appears redundant, though it sits just above the ideal 3-15 range.
The surface covers a wide domain well: models, authors, methods, datasets, indices, timeline, delistings, deletions, README drift history, and download anomalies, with both list and detail variants. Minor gaps exist (e.g. no explicit search for authors/methods beyond list, no benchmark-only lookup), but core workflows are covered.