The MCP tool directory.

Build a read-only maintainer-reviewed HeyClaude submission draft with canonical PR text and URLs.

Review a HeyClaude submission draft locally for schema errors, duplicate risk, and maintainer checklist items without writing to GitHub.

Fetch read-only HeyClaude submission schemas for PR-first intake by category.

Build prefilled HeyClaude submit and review URLs for a validated PR-first submission draft without making write calls.

Validate a HeyClaude content submission draft locally without creating GitHub issues, pull requests, or publishing content.

Update the status of a Submission (e.g. Submitted, Client Reviewed, Rejected, Hired).

Update the status of a Submission (e.g. Submitted, Client Reviewed, Rejected, Hired).

Update the status of a Submission (e.g. Submitted, Client Reviewed, Rejected, Hired).

Update the status of a Submission (e.g. Submitted, Client Reviewed, Rejected, Hired).

Create a Submission record linking a Candidate to a Job Opening for client review.

Create a Submission record linking a Candidate to a Job Opening for client review.

Create a Submission record linking a Candidate to a Job Opening for client review.

Create a Submission record linking a Candidate to a Job Opening for client review.

Persist targeting artifacts (keywords/subreddits) and return policy/preview. Prerequisites: - prompt pack must be acknowledged for `session_id` - artifacts should already be saved for best results Typical next step: - approve targeting (done automatically by `run_full_agentic_onboarding` when enabled) Formats: - keywords: list[str] - subreddit_groups: [{'subreddits': ['name1','name2']}]

Submit feedback about Busan Essentials data quality, coverage, or feature requests. Use this tool when you notice missing data, inaccurate information, or have suggestions for improvement. All feedback is actively reviewed and incorporated.

Validate and persist core onboarding artifacts for a product/session. Prerequisites: - prompt pack must be acknowledged for `session_id` - payloads should match the artifact schemas below Common use: - called by `run_full_agentic_onboarding` - can also be used for staged/recovery runs Expected formats: - market_position: patch object with market position keys - conversion_notes: {'Product Name','Payment Terms/Plans','General Notes'} - funnels: [{'url','description','primary_use_case', optional 'qualification'}]

Submit one or more ticket images (as base64-encoded strings) to the Identifai v2 API for batch tampering detection. Each ticket is analysed independently; results are retrieved asynchronously via get_tampering_batch_results using the returned batch_id. Supports PDF files (each page becomes a separate analysis entry). Maximum 10 tickets per batch. Authentication: provide your Identifai API key via the apiKey parameter or configure the X-Api-Key HTTP header in your MCP client (recommended).

Retrieves subscription information including limits and usage statistics for API units, workspace quotas, and API key details. This endpoint is free and does not consume any API units. Use doc tool first to get the real input schema.

Subtraction calculator that subtracts second number from first number

Subtracts the second number from the first number

Detailed service alerts with impact analysis, affected stations, and estimated resolution times

Get search suggestions (autocomplete) for a query

Generate schema-aware query suggestions with ready-to-run SQL. Great for exploring unfamiliar databases or finding useful queries.

Adds any number of numbers together

Open a support ticket and return the created ticket. Each call starts a new ticket; send follow-up details as a message on the existing ticket.

Read a support ticket and its full message history. Replies arrive asynchronously; re-read the ticket until a message with `sender_type: agent` appears that was not there before, or the ticket leaves `OPEN`.

List the support tickets opened from this workspace's organization, newest first, each carrying its full message history.

Reply to an existing support ticket by its ID. The response contains only the ticket ID; use `support_tickets_get` for the updated message history.

Record that the authenticated user has seen this support thread. This suppresses a reply-notification email when the user has already read the latest support reply.

Claim an open leg of a digital task. First agent to bid wins the leg. You will receive the previous leg's result as context when you start. Complete with swarmhaul_complete_digital_leg.