generated: '2026-09-23' method: probed source: https://docs.asaas.com/mcp status: published server: name: asaas transport: http url: https://docs.asaas.com/mcp deployment: mode: remote endpoint: https://docs.asaas.com/mcp verified: probed probe: live checked: '2026-09-23' source: docs-check 2026-09-23 (MCP server named in the provider's own llms.txt/docs, then probed; roadmap#590) tools_note: No tool list captured. This manifest records a PROBED, reachable endpoint only; anonymous tools/list was auth-gated or the server requires an initialize handshake this reachability probe does not perform. Run signals/audit_mcp_authorship.py --probe to enumerate tools and settle platform-vs-provider authorship. Do NOT derive a tool list from the OpenAPI and store it here -- that is a candidate manifest, and it belongs under an X-MCPServerCandidate pointer. tool_quality: tool_count: 7 tokens_total: 1190 tokens_per_tool_median: 128 heavy_tools: [] heavy_tool_count: 0 params_total: 9 params_undescribed: 0 params_described_pct: 100.0 tools_with_undescribed_params: 0 tools_annotated: 7 annotated_pct: 100.0 state_changing_unhinted: [] tools_missing_schema: 0 short_descriptions: 0 duplicate_descriptions: 0 duplicate_names: 0 nonportable_names: [] output_schema_count: 0 token_estimate: chars/3.6 of each compact tool definition source: mcp/asaas-mcp-tools.json measured: '2026-10-20' scored: false note: Facts from the saved tools/list capture (mcp_tool_quality.py); recorded, not scored. Checks learned from Glimind's agent-readiness audit. tools: - name: list-endpoints description: Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'. - name: get-endpoint description: Gets detailed information about a specific API endpoint, including security schemes and servers - name: search-endpoints description: Performs a deep search through paths, operations, and parameters to discover relevant API endpoints. Use this tool to find specific API capabilities, required parameters, or data models based on search keywords. Results can be passed directly into 'get-endpoint'. - name: list-specs description: Lists all available OpenAPI specs. Use the title to select a spec. - name: execute-request description: Executes an API request with a given HAR request object. - name: search description: Searches through documentation with the given search query, returning a list of results with ID, title, and URL. - name: fetch description: Gets detailed content for documentation by ID returned from the `search` tool. tools_count: 7