io.github.zma-petterzhang/guardmarket
Related Servers
Alternatives to io.github.zma-petterzhang/guardmarket
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to find and evaluate ranked MCP servers, skills, and agents for a task, retrieve detailed entry information and install snippets, and optionally report usage outcomes.601 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to search skills.sh, view leaderboards, inspect skill details, retrieve third-party security audits, and browse official curated skills, with install commands for each result.49 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search, retrieve, score, compose, and verify reusable agent skills from the SkillForge registry via MCP.18 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to browse and use a directory of SKILL.md skills, collect feedback and run traces, and manage recipes over stdio or authenticated HTTP.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store, version, and retrieve reusable skills through MCP, with scoped client access and optional usage-based recommendations.18 npmMIT
- AlicenseNot gradedqualityBmaintenanceExposes MCP tools that let an agent search a catalog, inspect a paid service's pricing, fetch it with payment handled automatically, and check its remaining budget and active spending limits. Payments are authorized against a signed mandate from the owner, so agents can buy API access over HTTP 402 without ever holding the owner's private key.563 npmMIT
TDQS
Scored across 5 tools
Each tool maps cleanly to a distinct lifecycle step: catalog search, skill detail inspection, paid invocation, wallet balance, and receipt lookup. Search and describe both return price information but serve obviously different purposes, so an agent is unlikely to misselect.
All tool names follow the same `market.<lowercase_word>` convention and are immediately recognizable as part of one domain. While not all are verb_noun pairs, the pattern is perfectly predictable and internally consistent.
Five tools is a well-scoped size for this marketplace. Each tool covers a necessary part of the discovery-to-invocation-to-verification workflow with no redundant utilities.
The tool surface covers the full user-facing lifecycle: find a skill, inspect it, check funds, invoke it with a price cap, and retrieve the receipt/result. The explicit handling of idempotency and pending holds means there are no obvious dead ends for the stated domain.