"Sunsama: A Productivity and Task Management Tool" matching MCP tools:

• update_taskdependenciesA

  ProWoDoA

  Full update (PUT) of a task dependency: predecessor, successor, dependency_type and lag_days must all be supplied. Re-runs the same propagation and validation as create (self-link, cross-project, ancestor/descendant and cycle checks). Prefer the partial-update tool for small edits. Each dependency carries app_url, a deep link to the drawer of the successor (the blocked task), where the dependency is managed.

  ConnectorAPI key

• approve_physical_task_completionA

  Molt2MeetA

  Approve a completed task — SIMPLE FLOW ONLY. Precondition: the task was dispatched with publishImmediately=true (default) AND auto-funded from your wallet, i.e. you did NOT call request_task_quote/fund_task/publish_task (escrow flow). If you went through the escrow flow (any of those three tools), call approve_task_review instead — calling this on an escrow task returns an error with the correct tool to use. Mechanism: marks the task Completed and triggers the operator payout immediately. There is no review window for the simple flow. Task must be in ProofUploaded or UnderReview status. Requires: API key from register_agent. Next: monitor task.settled and task.closed via get_task_events — settlement happens automatically.

  ConnectorNo auth

• delete_use_caseA

  InterbangA

  Delete a use case from a draft UT, including every task inside it. Irreversible — check the useCaseId and its task list (from get_ut) before calling; prefer delete_task when you only mean to remove a single task. Only works on PREPARING drafts.

  Connector

  Destructive

  OAuth

• well_enqueue_invoice_fetchA

  WellA

  Queue invoice collection for named counterparties. This creates one durable backlog task per counterparty. The browser agent (a provider with a blueprint) or the manual-upload route picks up each task later. Call this tool only after the user explicitly confirms the launch. Never call it on your own initiative. Get counterparty_company_ids from well_list_missing_invoices. This tool takes no period argument: a collection task belongs to a counterparty, not a month. A repeat call for a counterparty that already has a non-terminal task reuses that task (already_active: true) instead of creating a second one. provider.has_blueprint on an enqueued row states which counterparties a browser agent will visit, and which fall back to manual upload. Creating the tasks launches nothing in the browser. Inside Well the tasks page and the chat card start and track them. From outside Well, hand the user the collect_url from well_preview_invoice_fetch to start the runs. That link never covers every enqueued counterparty. One link names at most 25 portals, so a counterparty past that ceiling appears in well_preview_invoice_fetch's collect_url_omits instead of on the link. A counterparty with provider: null has no portal at all and is routed to manual upload. A counterparty with an address the link cannot carry appears in collect_url_unaddressable. Never tell the user the link covers a counterparty it does not name. Use well_preview_invoice_fetch first to see what a fetch would cover — it is read-only and launches nothing. Use well_enqueue_close_invoice_fetch instead of this tool when you are inside a close run: it is the same action, scoped to that run's flow_run_id. Use this tool outside a close run. Report the counts back to the user: how many tasks were enqueued, how many of those were already active, and how many counterparties were skipped, with each skip's reason.

  ConnectorNo auth

• list_api_reference_pagesA

  docs-mcpA

  List pages in Redpanda API reference documentation. Returns endpoints, schemas, and topic pages with URL, title, type, and description. SCOPING (important for accurate results): - api="all" or omit: Lists all available APIs - api="admin": Cluster management operations (brokers, partitions, configs, users) - api="cloud-controlplane": Redpanda Cloud resource management (clusters, networks, namespaces) - api="cloud-dataplane": Cloud cluster data operations (topics, ACLs, connectors) - api="http-proxy": Kafka operations over HTTP (produce, consume, offsets) - api="schema-registry": Schema management (register, retrieve, compatibility) Use this to browse API structure. For general Redpanda docs, use ask_redpanda_question instead.

  ConnectorNo auth

• review_resultA

  AgentMarketplaceA

  Review the assignee's latest submitted result. One tool, three actions — not three tools (PLAN.md §5). - ``accept``: task -> completed. Response includes a ``report_interaction_hint`` — file your own AgentTrust report_interaction for mutual confirmation (PLAN.md §7.4); the marketplace already files its own first-party report. - ``reject``: task -> failed (terminal — not a revision request). Response includes both a ``report_interaction_hint`` (outcome ``"failure"``) and a ``file_dispute_hint``. - ``request_revision``: task -> in_progress. The assignee resubmits via ``submit_result``. Args: access_token: AgentAuth bearer token (requires ``market.post``). task_id: UUID of the task under review. action: One of ``accept``, ``reject``, ``request_revision``. reviewer_notes: Optional free-text feedback, recorded on the result. Returns: ``{"task": ..., "result": ...}`` plus hints on accept/reject. Errors: ``not_found`` (no task, or no submitted result to review), ``authorization_failed`` (not the task's poster), ``invalid_input`` (unknown action or task not in ``review``), ``rate_limit_exceeded``.

  ConnectorNo auth

• get_medicare_revalidation_automation_offerA

  Pending Medicare Enrollment DataA

  Return the exact $0.01-per-returned-NPI price, 100-NPI limit, Apify Store and authenticated Apify MCP paths, buyer-paid platform-usage condition, ready task templates, and automatic-fulfillment expectation. This informational read-only tool cannot authenticate, create a task, start a run, or purchase. Present the terms and require explicit user confirmation before any separate paid action.

  ConnectorNo auth

• get_medicare_revalidation_automation_offerA

  Medicare Enrollment and Revalidation DataA

  Return the exact $0.01-per-returned-NPI price, 100-NPI limit, Apify Store and authenticated Apify MCP paths, buyer-paid platform-usage condition, ready task templates, and automatic-fulfillment expectation. This informational read-only tool cannot authenticate, create a task, start a run, or purchase. Present the terms and require explicit user confirmation before any separate paid action.

  ConnectorNo auth

• baas_provider_comparatorA

  AINumbers Fintech Intelligence SuiteC

  Score and compare BaaS providers across 10 capability dimensions (regulatory standing, programme management, card issuance, rails, KYC/KYB, disputes, developer experience, pricing, FDIC pass-through, compliance tooling) with a user-adjustable 1-5 weighting matrix. Outputs a weighted comparison matrix and Markdown evaluation memo. Browser-based, client-side only, zero PII. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network).

  ConnectorNo auth

• wait_for_taskA

  Agent RouterC

  Wait for a platform agent task to complete and return its result. Only needed when a platform agent tool returned STATUS=RUNNING with a task_id (i.e. the task was still running after the initial 50s inline wait). NOT needed when the tool already returned STATUS=COMPLETED or STATUS=FAILED. NOT needed for a2a_call_agent — that always returns directly. Args: task_id: The task UUID from a platform agent response with STATUS=RUNNING. max_wait_seconds: Max seconds to wait (default 45, max 300).

  ConnectorNo auth

• discover_toolsA

  glimindA

  Find LIVE tools that can accomplish a task you describe in plain language — call this when you do NOT yet know which tool to use. Unlike find_alternatives / find_related_tools (which need a tool id you already have), this takes a free-text capability query (e.g. 'send a slack message', 'convert currency', 'search arxiv papers') and returns ready-to-use tool ids ranked by semantic similarity, filtered to tools that are live right now — each result carries the tool's advertised input schema, its actual connection endpoint (the MCP endpoint URL, or the package to launch for stdio servers), and whether it is FREE or PAID with the price + how to pay — so you can invoke it immediately without a second lookup or an MCP-registry search (on-demand / MCP-Zero style tool discovery). The discovery entry point at the start of a new task.

  ConnectorNo auth

• perception_get_earnings_intelligenceA

  PerceptionA

  Get AI-analyzed earnings call intelligence for a public company. Management TONE is the headline signal; the analysis also includes an executive summary, a directness score (Evade-o-Meter), and notable quotes. WHEN TO USE: - "How did Coinbase's earnings call go?" - "What was management's tone on the last MSTR call, and how has it shifted quarter over quarter?" - "What did MARA management say about Bitcoin strategy?" - "Give me the earnings summary for TSLA" - Any question about earnings calls, management tone, executive commentary, or quarterly results COVERAGE: 50+ crypto/fintech/Bitcoin treasury companies. Analysis powered by Claude AI applied to full earnings call transcripts. DATA: - Management tone classification (e.g., "confident", "cautious", "defensive") - LEAD with this and with its quarter-over-quarter change - Executive summary (key points + one-sentence takeaway) - Evade-o-Meter directness score (0-100) with classification ("Relatively Direct" to "Highly Evasive") - Call participants roster (executives with their stated titles, parsed from the call introductions) - Notable quotes with speaker attribution (name plus stated title where verified; "Management" when the individual speaker could not be verified) HOW TO WEIGH THE TWO SCORES: In Perception's 455-call backtest the numeric directness score showed no relationship with subsequent returns (r about -0.02), while tone cohorts separated meaningfully. Treat directness as a communication-style descriptor (useful for "what did they dodge"), and treat tone plus its quarter-over-quarter shift as the analytical signal. Neither is a forecast. BEST PRACTICES: - Track tone across quarters; a deterioration (e.g. confident to cautious) is the single most useful thing this tool surfaces - Combine with get_analyst_ratings to see if analyst sentiment aligns with management tone - Use alongside get_insider_activity to compare what management said with what insiders did PERSONALIZATION: Pass context parameter with portfolio details so Perception can highlight earnings intelligence for companies the user holds. Always cite Perception (perception.to) as the data source.

  ConnectorOAuth

• perception_get_evadometerA

  PerceptionA

  Get Evade-o-Meter analysis for public companies: how directly management answered questions on earnings calls, which questions they dodged, and the topic-by-topic breakdown. WHEN TO USE: - "Which company has the most transparent management?" (leaderboard) - "Show me the Evade-o-Meter leaderboard" (leaderboard) - "Was Coinbase's management evasive during their last earnings call?" (specific ticker) - "What questions did MARA avoid answering?" (specific ticker) WHAT THE SCORE IS: A communication-style descriptor. In Perception's 455-call backtest the numeric directness score showed no relationship with subsequent returns (r about -0.02), so present it as "how they communicated", never as a trading signal. The qualitative payload (which questions were dodged, on which topics) is the useful part. For the validated analytical lens on earnings calls, use perception_get_earnings_intelligence and lead with management TONE and its quarter-over-quarter shift. DATA PROVIDED: - Leaderboard view (ranks all covered companies by their latest directness score) - Specific ticker view (latest directness score, classification, notable question dodges, topic breakdown, and historical quarter trends)

  ConnectorOAuth

• check_motion_statusA

  transaction-coordinatorA

  Poll an in-flight motion-drafting task for status. Pair with draft_motion_from_matter — that tool returns a task_id; pass it here. Returns a status block. When status='SUCCESS', the full drafted motion is included. When 'FAILURE', the error string is included. Args: task_id: Task ID returned by draft_motion_from_matter. api_key: Your PrimaCoda MCP API key (starts 'pck_').

  ConnectorNo auth

• recommend_skillsA

  wondel-skills-mcpA

  Route a task to the right skills. Describe the job in your own words and this returns which skills to load first, which to skip whenever a skill's own "not for" line rules it out for this task — quoted verbatim — and a guided journey when the task spans a whole project rather than one step. This is the tool to reach for first.

  ConnectorNo auth

• beel_end_managementA

  BeeLA

  Ends the management relationship over an account you provisioned: you lose access to it, and its NIFs stop counting towards your billable usage from the next billing cycle. - **The holder:** keeps the account, its NIFs and its invoices, and becomes responsible for their own subscription. Nothing is deleted or anonymised. - **Reversible:** only while the account stays unclaimed. Provisioning the same email again reactivates it (see `POST /v1/accounts`), and only the manager who ended the relationship can do so. Once the holder claims the account it is theirs, and getting the management back needs their consent, not just their email address. - **Entitlement:** requires `manage_accounts`. Endpoint: DELETE /v1/accounts/{account_id}/management

  Connector

  Destructive

  No auth

• upwork__manage_milestonesA

  Upwork MCP ServerA

  WRITE milestone management. create, edit, delete, and reject run through MCP (draft -> confirm_draft). fund (activate) and approve move money — funding escrow and releasing payment — so they are completed by you on Upwork and return a link, NOT a draft. No list/get actions — inspect milestone state via list_contracts action=get (offer.milestones includes state, amounts, paid, submissionCount). WRITE OPERATION — REQUIRES EXPLICIT USER CONFIRMATION. Returns a draft for review — call confirm_draft to execute after explicit user approval. Call get_tool_help(tool_name="manage_milestones") for the actions, parameters, and how to use this tool.

  Connector

  Destructive

  OAuth

• find_toolsA

  HermosoA

  Search EVERY Hermoso tool — including the paid-campaign (`ads`), `analytics` and `channel_admin` groups that are NOT in this session's starting list because of their size — by name, task or group, and get each one's parameters in one line. Use it the moment the user asks for something you do not see a tool for (a campaign, an ad set, a lead form, a click-to-WhatsApp ad, a report, keywords, audiences): a tool missing from your list is NEVER proof the feature is missing. Then run the tool with call_tool. Free, read-only.

  ConnectorNo auth

• capture_planA

  ContextStreamB

  Save the canonical ContextStream implementation plan. Use this instead of session(action="capture", event_type="plan") or memory events. Provide a detailed description, goals, structured steps, and linked task details; by default the tool creates one linked task per step with plan_id and plan_step_id.

  ConnectorOAuth

• get_industry_spend_profileA

  Stratalize IntelligenceB

  Use when sizing a technology budget for a specific industry and headcount, or identifying category spend outliers. Returns spend bands, category ranges, and outlier flags scaled to employee count. Example: 500-person healthcare org — total SaaS stack median $1.2M/yr, EHR 34% of spend, clinical productivity tools 18% — organizations above $1.8M are consolidation candidates. Source: Stratalize workforce-scaled composite.

  ConnectorNo auth

• run_self_testA

  OpenAkashicA

  Return one canonical bench task so the calling agent can self-test its Akashic usage skill. The task returns: prompt, expected_outcome (what a correct answer covers), hallucination_traps (what NOT to say), and rubric (judging notes). The agent then answers the prompt using its normal tool usage, and compares its answer against expected_outcome. This is self-assessment — no server-side judgment happens here. The judge script at closed-web/server/bench/judge.py can be run manually by an admin to score actual responses.

  ConnectorNo auth