134,408 tools. Last updated 2026-05-23 19:26
"An application to assist individuals in responding to cardiac arrest situations" matching MCP tools:
- Get detailed information about a specific job listing/posting by its job listing ID (not application ID). Use this to view the full job posting details including description, salary, skills, and company info. For job application details, use get_application instead.Connector
- Download an attachment (resume, candidate file, application file, mail attachment, call recording). Pass the absolute URL returned by another endpoint (e.g. `message.attachments[].url`, `cv.url`, `resume.url`) — it MUST belong to the configured 100Hires API host; other hosts are rejected to avoid leaking the Bearer token. Returns `{file_name, mime_type, size, data}` where `data` is base64-encoded bytes. Files larger than 25 MB are rejected up-front (Content-Length check / streaming abort) without being loaded into memory.Connector
- Apply to work on a published task. Workers can browse available tasks and apply to work on them. The agent who published the task will review applications and assign the task to a chosen worker. Requirements: - Worker must be registered in the system - Task must be in 'published' status - Worker must meet minimum reputation requirements - Worker cannot have already applied to this task Args: params (ApplyToTaskInput): Validated input parameters containing: - task_id (str): UUID of the task to apply for - executor_id (str): Your executor ID - message (str): Optional message to the agent explaining qualifications Returns: str: Confirmation of application or error message. Status Flow: Task remains 'published' until agent assigns it. Worker's application goes into 'pending' status.Connector
- ⚡ CALL THIS TOOL FIRST IN EVERY NEW CONVERSATION ⚡ Loads your personality configuration and user preferences for this session. This is how you learn WHO you are and HOW the user wants you to behave. Returns your awakening briefing containing: - Your persona identity (who you are) - Your voice style (how to communicate) - Custom instructions from the user - Quirks and boundaries to follow IMPORTANT: Call this at the START of every conversation before doing anything else. This ensures you have context about the user and their preferences before responding. Example: >>> await awaken() {'success': True, 'briefing': '=== AWAKENING BRIEFING ===...'}Connector
- Create a browser upload link for media files. ALWAYS use this when the user shares an image or video in chat — their file is local and cannot be passed directly to publish_content. WORKFLOW: 1. Call this tool to get an uploadUrl 2. Give the user the link to open in their browser and upload their file 3. After upload, call get_upload_session to get the public media URL(s) 4. Use the returned URL with publish_content or schedule_content Supports up to 20 files per session. Expires in 15 minutes.Connector
- Simple ping test to verify MCP server is respondingConnector
Matching MCP Servers
- AlicenseAqualityBmaintenanceConverts AI Skills (following Claude Skills format) into MCP server resources, enabling LLM applications to discover, access, and utilize self-contained skill directories through the Model Context Protocol. Provides tools to list available skills, retrieve skill details and content, and read supporting files with security protections.Last updated324Apache 2.0
- AlicenseAqualityCmaintenanceRoutes one brief to the right image model across 60+ (gpt-image-1.5, Ideogram 3, Recraft V4, Flux), validates the output, and fans out to iOS/Android/PWA/favicon/visionOS/Flutter bundles. Works without an API key via Pollinations, HF Inference, Stable Horde, or host-LLM inline SVG.Last updated2246
Matching MCP Connectors
Transform any blog post or article URL into ready-to-post social media content for Twitter/X threads, LinkedIn posts, Instagram captions, Facebook posts, and email newsletters. Pay-per-event: $0.07 for all 5 platforms, $0.03 for single platform.
Daily world briefing that tells AI assistants what's actually happening right now. Leaders, conflicts, deaths, economic data, holidays. Updated daily so they stop getting current events wrong.
- Get the artist profile (including artist_id). Call at the START of every conversation — before responding. Also call after connect_catalogue. Cache artist_id for the session.Connector
- Generates a browser authorization URL for connecting a new social account to a project. This endpoint is useful for multi-user integrations where your application lets your own users, clients, or brands connect their social accounts to WoopSocial without giving them access to your WoopSocial account. A common flow is: 1. Create or select a WoopSocial project for your user, client, or brand. 2. Call this endpoint from your backend with that `projectId`, the target `platform`, and a `redirectUrl` in your application. 3. Open the returned `url` in your user's browser. 4. After OAuth completes, WoopSocial redirects the browser back to `redirectUrl` with result query parameters. 5. Use `projectId` and `socialAccountIds` from the redirect, or call `GET /social-accounts?projectId=...`, to store or confirm the connected account in your application. When `redirectUrl` is provided, the browser is redirected back to that URL after the OAuth callback is handled. For Facebook, WoopSocial shows a page-selection screen after authorization because Facebook may return more pages than the user appeared to select in the Facebook dialog in cases where the user has authorized with WoopSocial previously. The selected pages are connected to the single `projectId` from this request, then WoopSocial redirects back to `redirectUrl` when one was provided. When `redirectUrl` is provided, WoopSocial appends these query parameters on success: - `status=success` - `projectId`: the project identifier from the request - `platform`: the connected social platform - `socialAccountIds`: comma-separated connected social account identifiers. This may contain one or more IDs depending on the platform OAuth flow. When `redirectUrl` is provided, WoopSocial appends these query parameters on failure: - `status=error` - `projectId`: the project identifier from the request - `platform`: the requested social platform - `error`: an OAuth callback error code If the OAuth callback state is missing or expired, WoopSocial cannot safely determine the original `redirectUrl`, so the callback returns an HTTP error instead of redirecting. The redirect never includes OAuth tokens or credentials.Connector
- Connector
- Apply to work on a published task. Workers can browse available tasks and apply to work on them. The agent who published the task will review applications and assign the task to a chosen worker. Requirements: - Worker must be registered in the system - Task must be in 'published' status - Worker must meet minimum reputation requirements - Worker cannot have already applied to this task Args: params (ApplyToTaskInput): Validated input parameters containing: - task_id (str): UUID of the task to apply for - executor_id (str): Your executor ID - message (str): Optional message to the agent explaining qualifications Returns: str: Confirmation of application or error message. Status Flow: Task remains 'published' until agent assigns it. Worker's application goes into 'pending' status.Connector
- Use this tool at the start of a relevant conversation to check for saved context, or when the user asks you to retrieve something stored earlier. Triggers: 'recall my project notes', 'what did we save last time?', 'look up my preferences', 'fetch the notes you stored'. Also call proactively at the start of sessions where the user seems to be continuing prior work — retrieve context before responding. Pass the same key used with save_memory. Returns stored content, save date, and expiry date.Connector
- Get the tennis player roster covered by whensport (top ATP/WTA players). Singles tennis has no team concept — players compete as individuals — so this tool fills the role that getTeams plays in team sports. Each player record includes nationality, ranking, and Grand Slam wins where known.Connector
- Simple ping test to verify MCP server is respondingConnector
- Use this tool at the start of a relevant conversation to check for saved context, or when the user asks you to retrieve something stored earlier. Triggers: 'recall my project notes', 'what did we save last time?', 'look up my preferences', 'fetch the notes you stored'. Also call proactively at the start of sessions where the user seems to be continuing prior work — retrieve context before responding. Pass the same key used with save_memory. Returns stored content, save date, and expiry date.Connector
- Validates an Argentine CUIT (Código Único de Identificación Tributaria) — the tax identification number for companies, self-employed workers, and legal entities in Argentina, issued by AFIP (Administración Federal de Ingresos Públicos). Applies the official weighted modulo-11 checksum algorithm. Returns { valid: boolean, cuit: string, type: string } or { valid: false, reason: string }. CUIT prefix identifies entity type: 20/23/24/27 for individuals, 30/33/34 for companies. Use when processing Argentine invoices, supplier registration, or AFIP compliance workflows.Connector
- Check if the discava API is online and responding. Returns status and version. No parameters required.Connector
- Validates an Argentine CUIL (Código Único de Identificación Laboral) — the labor identification number for individuals in Argentina, used for employment records and social security (ANSES). Uses the same weighted modulo-11 checksum as CUIT. Returns { valid: boolean, cuil: string } or { valid: false, reason: string }. Use when processing Argentine payroll, employment contracts, or any social security compliance workflow.Connector
- Returns a chronological feed of balance-changing events for a user — bridge deposits/withdrawals, on-chain account deposits/withdrawals, vault deposits/withdrawals, liquidations, and funding payments. Each row carries an `event_type` discriminator and a `notes` field with type-specific extras (e.g. funding rate and position size for funding events). For trade fills, use `/v1/hyperliquid/markets/activity` instead. Supply `event_types` (comma-separated) to filter to a subset. Defaults to the last 30 days when no time range is specified — provide `start_time` and `end_time` to query older data. **Query Parameters:** - **user** (Required): Filter by address - **event_types**: Filter by balance-event type.<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **start_time**: UNIX timestamp in seconds or date string (e.g. "2025-01-01T00:00:00Z", "2025-01-01", ...). - **end_time**: UNIX timestamp in seconds or date string (e.g. "2025-01-01T00:00:00Z", "2025-01-01", ...). - **limit**: Number of items* returned in a single request.<br>*Plan restricted. - **page**: Page number to fetch.<br>Empty `data` array signifies end of results. **Responses:** - **200** (Success): Successful Response - Content-Type: `application/json` - **Response Properties:** - **request_time**: ISO 8601 datetime string - **Example:** ```json { "data": [ { "block_num": 1, "timestamp": "string", "transaction_hash": "string", "amount": 1.5, "counterparty": "string", "notes": "string", "token": "string", "user": "string", "event_type": "bridge_deposit", "event_index": 1 } ], "statistics": { "elapsed": 1.5, "rows_read": 1.5, "bytes_read": 1.5 }, "pagination": { "previous_page": 1, "current_page": 1 }, "request_time": "string", "duration_ms": 1.5, "results": 1.5 } ``` - **400**: Client side error - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **401**: Authentication failed - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **403**: Forbidden - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **404**: Not found - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **500**: Server side error - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "bad_database_response", "message": "string" } ```Connector
- Get the Slidev syntax guide: how to write slides in markdown. Returns the official Slidev syntax reference (frontmatter, slide separators, speaker notes, layouts, code blocks) plus built-in layout documentation and an example deck. Call this once to learn how to write Slidev presentations.Connector
- Get the full chronological stage transition history for an application, including the initial assignment. Each entry has from_stage_id/name, to_stage_id/name, moved_at (Unix seconds), moved_by_type (system, user, automation), and moved_by_user_id. Use this for funnel analysis and time-in-stage reports instead of paginating through /candidates/{id}/activities when only stage data is needed.Connector