helloasso-mcp
Related Servers
Alternatives to helloasso-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA read-only MCP server for accessing Mobilize public API data, including organizations, events, and enums.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to browse and read files, folders, albums, and metadata from a Microsoft cloud drive, search content, and report storage quota through a read-only stdio server that only issues GET requests.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read Sierra Chart study outputs, chart discovery, and study metadata/history via read-only tools over Streamable HTTP or stdio.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to browse and read files, folders, photo albums, and metadata in the user's cloud drive through a read-only stdio server, including folder listing, full-text search, glob-based finding, file reading, item stats, and storage quota reporting.MIT
- AlicenseAqualityCmaintenanceA read-only MySQL MCP server supporting stdio, SSE, and Streamable HTTP transports, enabling secure querying and schema inspection of MySQL databases from MCP clients.3MIT
- AlicenseCqualityDmaintenanceA local MCP server for the LimaCharlie security platform that provides investigation, administration, and content-review workflows via a broad read-only tool surface with explicit organization scoping and audit logging.100MIT
TDQS
Scored across 12 tools
Each tool targets a distinct resource+action: organizations, form types, forms, form stats, items, orders, payments each have clear list/get boundaries. The list-vs-get distinction is unambiguous, and helloasso_list_my_organizations vs helloasso_get_organization is disambiguated by the descriptions (access rights vs public details).
Every tool follows the same helloasso_<verb>_<noun> pattern in consistent snake_case, with predictable list/get pairs. No mixing of conventions or vague verbs.
12 tools is well within the ideal range and each earns its place: list/get coverage across orgs, forms, items, orders, payments, plus form-types and stats helpers. No redundancy.
Full read/list lifecycle coverage for the domain (orgs, forms, items, orders, payments, stats) with no obvious list/get dead ends. Minor gaps: no create/update/delete or refund-initiation tool, though the server appears intentionally read-only and get_payment references refund operations it cannot act on.