SkullRender-Agents MCP Server
Related Servers
Alternatives to SkullRender-Agents MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to discover and validate API Agent Manifests, check whether intended operations are permitted by a manifest, and submit or track origin listings in the public AMP registry.382 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables agents to discover offers, retrieve schemas, validate JSON blueprints, preview plugins, and compile deterministic plugin packages as portable artifacts without publishing or mutating third-party systems.-
- AlicenseBqualityBmaintenanceEnables centrally authoring and validating reusable agent guidance and delivering it across MCP-compatible hosts via registry resources, prompt templates, skill execution, and shared state.7MIT
- FlicenseNot gradedqualityBmaintenanceEnables agents and projects to register identities, publish and discover contract manifests (berths), resolve dependencies and check compatibility, and subscribe to or broadcast contract-change notifications over MCP tools and resources. It also supports isolated agent-to-agent messaging and an admin overview of participants, berths, subscriptions, and audit history.-
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to search a registry, inspect capability contracts, verify releases, check machine readiness, install/remove and run QuickAgents, and hold interactive sessions, with JSON results and consent-gated write/run actions.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP hosts to run a user-configurable agent with multi-engine orchestration, declarative connectors to third-party APIs, task-graph execution, audit ledger, and memory, without needing to clone or configure multiple repositories.27 npm1MIT
TDQS
Scored across 7 tools
Each tool targets a distinct resource and operation: listing/getting agents, listing/getting packs, resolving identities, and validating/retrieving schemas for briefs. There is no overlap or ambiguity between them.
All tools share the 'skflow_' prefix and mostly follow a resource_action pattern. The only deviations are 'skflow_brief_schema' lacking an explicit verb and the singular/plural inconsistency between list and get (e.g., 'agents_list' vs 'agent_get').
With 7 tools, the server is well-scoped for its purpose—covering agent manifests, personality packs, identity resolution, and brief validation—without being bloated or too sparse.
The tool set provides a complete read-oriented workflow for the domain: list and get for both agents and packs, a resolution function, and validation with its accompanying schema. No obvious gaps or dead ends are apparent.