Tool search 101,857 tools · 5,224 live servers

Run Disco on tabular data to find novel, statistically validated patterns. This is NOT another data analyst — it's a discovery pipeline that systematically searches for feature interactions, subgroup effects, and conditional relationships nobody thought to look for, then validates each on hold-out data with FDR-corrected p-values and checks novelty against academic literature. This is a long-running operation. Returns a run_id immediately. Use discovery_status to poll and discovery_get_results to fetch completed results. Use this when you need to go beyond answering questions about data and start finding things nobody thought to ask. Do NOT use this for summary statistics, visualization, or SQL queries. Public runs are free but results are published. Private runs cost credits. Call discovery_estimate first to check cost. Private report URLs require sign-in — tell the user to sign in at the dashboard with the same email address used to create the account (email code, no password needed). Call discovery_upload first to upload your file, then pass the returned file_ref here. Args: target_column: The column to analyze — what drives it, beyond what's obvious. file_ref: The file reference returned by discovery_upload. analysis_depth: Search depth (1=fast, higher=deeper). Default 1. visibility: "public" (free) or "private" (costs credits). Default "public". title: Optional title for the analysis. description: Optional description of the dataset. excluded_columns: Optional JSON array of column names to exclude from analysis. column_descriptions: Optional JSON object mapping column names to descriptions. Significantly improves pattern explanations — always provide if column names are non-obvious (e.g. {"col_7": "patient age", "feat_a": "blood pressure"}). author: Optional author name for the report. source_url: Optional source URL for the dataset. use_llms: Slower and more expensive, but you get smarter pre-processing, summary page, literature context and pattern novelty assessment. Only applies to private runs — public runs always use LLMs. Default false. api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.

Create a Disco account and get an API key. Provide an email address to start the signup flow. If email verification is required, returns {"status": "verification_required"} — the user will receive a 6-digit code by email, then call discovery_signup_verify to complete signup and receive the API key. The free tier (10 credits/month, unlimited public runs) is active immediately. No authentication required. Returns 409 if the email is already registered. Args: email: Email address for the new account. name: Display name (optional — defaults to email local part).

Complete Disco signup using an email verification code. Call this after discovery_signup returns {"status": "verification_required"}. The user receives a 6-digit code by email — pass it here along with the same email address used in discovery_signup. Returns an API key on success. Args: email: Email address used in the discovery_signup call. code: 6-digit verification code from the email.

Get a new API key for an existing Disco account. Sends a 6-digit verification code to the email address. Call discovery_login_verify with the code to receive a new API key. Use this when you need an API key for an account that already exists (e.g. the key was lost or this is a new agent session). Returns 404 if no account exists with this email — use discovery_signup instead. Args: email: Email address of the existing account.

Complete login and receive a new API key. Call this after discovery_login returns {"status": "verification_required"}. The user receives a 6-digit code by email — pass it here along with the same email address. Returns a new API key on success. Args: email: Email address used in the discovery_login call. code: 6-digit verification code from the email.

Free-tier prompt safety check. Analyzes text for prompt injection patterns and PII (credit card numbers, Brazilian CPF, US SSN, email, phone, passwords). Returns a safety assessment with specific warnings. No authentication required.

Register an action claim from an AI agent. The agent declares it performed an action (e.g., sent an email, created a PR, wrote a file) and ThinkNEO will verify it actually happened. Returns a claim_id for tracking. Part of the Outcome Validation Loop — 'From Prompt to Proof'. Requires authentication.

List your configurable Monitor Agent alert rules. Each rule watches a metric (e.g. an API key reaching a % of its budget, workspace spend, error rate) and notifies your channels (email/discord/whatsapp) when it fires. Requires an admin API key.

Create a Monitor Agent alert rule. Example: notify by email when API key 'X' reaches 75% of its budget → metric=key_spend_pct_of_budget, operator=gte, threshold=75, scope_value=<api_key_id>, budget_usd=<key budget>. Requires an admin API key.

Send a test notification through a rule's configured channels to confirm delivery (email/discord/whatsapp). Requires an admin API key.

Submit a disability insurance quote-comparison request to the Seaworthy Insurance sales pipeline (writes a Lead to Salesforce). Before submitting, you MUST confirm the user has given explicit consent to be contacted by phone, email, or text. A broker follows up within one business day (Mon-Fri, 8am-5pm Pacific). Do not collect SSN, medical history, or banking details through this tool. Eligibility: the agency places individual coverage for working professionals with meaningful income to protect; an applicant who is BOTH over 50 years old AND earning under $100,000 a year is outside what the agency can place, and such requests are rejected. Do not submit one; instead suggest group long-term disability through their employer, a professional or trade association group plan, or Social Security disability (https://www.ssa.gov/disability) if they are unable to work now.

Get TempGuru's published booking and procurement policies: minimum hours, cancellation/rescheduling, no-show backfill, COIs/additional insured, payment/invoicing, background checks, order confirmation, and quote response. Use for real booking questions that otherwise require an email. Values not supported by canonical copy are explicitly marked confirm_with_coordinator with TODO-for-Megan; never infer a missing number. <examples>get_policies() ; get_policies(topic='payment-terms') ; get_policies(topic='cancellation-rescheduling')</examples> <hints>Pass a topic to return one policy. Unknown topics return the available topic list. This is an operational summary, not a contract.</hints>

Create a safe buyer handoff for a TempGuru staffing quote. Use after the buyer has reviewed the plan and asks to proceed. Requires the saved non-PII plan_id returned by plan_staffing or save_staffing_plan and returns a prefilled TempGuru-owned review form. This tool does NOT accept or transmit a name, email, phone, company, or other contact details; it does NOT create a CRM lead or quote reference. The buyer must open the returned form_url, review the plan, enter their own contact details, and submit it themselves. Only that buyer submission creates the lead. Not a reservation; does not guarantee pricing or availability; no payment until the buyer approves a human-issued quote. <examples>request_quote(plan_id='ABCDEFGH2345', source_platform='claude-ai', skill_id='event-staffing-ordering', skill_version='1.7.0')</examples> <hints>If plan_staffing returned a complete continuation.form_url but storage did not return a plan_id, give that URL to the buyer directly instead of calling this tool. Never ask for contact details for an MCP call. If the plan expired, re-run plan_staffing. For urgent help, use megan@tempguru.co or (904) 206-8953.</hints>

Search for verified service professionals in Argentina by service type, city, neighborhood, verification status, minimum rating, and minimum review count. Returns a paginated list of professionals with display name, headline, ratings, verifications, and a `profile_url` that is the only sanctioned contact channel (no phone/email/whatsapp is ever returned). Use this for discovery; use `muovi_get_professional` for the full detail payload.

Fetch the full public profile for a single Muovi-verified professional by slug. Returns display name, headline, bio, portfolio image URLs, specialties, city + neighborhoods, services, ratings, verifications, and the canonical `profile_url`. The `profile_url` is the only sanctioned contact channel — phone, email, and whatsapp are never returned. Append `?create_task=1&service={slug}` to `profile_url` (or use `muovi_create_task_link`) to deep-link a user into the on-platform task creation flow targeted at this pro.

Build the business case to get your company to pay for leadership mentoring or coaching: computes the ROI in EUR (money saved + cost of delay avoided + missed opportunity + roadmap slippage avoided), suggests 3-6 month KPIs, and drafts a forwardable approval email for your manager. Based on 3,400+ mentoring sessions at marian.coach.

Create a pending direct booking without online payment for configured non-VRP fallback deployments. Use only after explicit user confirmation, with a propertyId from search, and only when no signed VRP direct_booking_url is available. For signed VRP offers, route to the signed host-domain URL instead. Requires Authorization: Bearer token (MCP_API_KEY or OAuth). Writes a pending booking server-side; not idempotent — check hemmabo_booking_status before retrying on timeout. Rate-limited per token. The booking is identified by propertyId + the checkIn/checkOut range + guests; guestName and guestEmail are required for host confirmation, while guestPhone is optional for check-in coordination.

Create a fallback non-VRP booking and return a host-configured Stripe checkout URL. Use only after explicit user confirmation when no signed VRP direct_booking_url is available. When get_verified_stay_offer returns a signed direct_booking_url, route the guest there instead. Requires Authorization: Bearer token (MCP_API_KEY or OAuth). Creates a pending booking and Stripe session server-side; not idempotent — check hemmabo_booking_status before retrying. Rate-limited per token. Pass quoteId to honor a price locked by hemmabo_booking_negotiate for the same propertyId/dates/guests, or omit it to price fresh at checkout; paymentMode picks the Stripe flow and channel picks the pricing channel, while guestName and guestEmail identify the guest.

Retrieve current status and full details of an existing booking by reservationId. Use to confirm checkout/create succeeded or before cancel/reschedule. Do NOT use for property discovery, availability, or pricing — use hemmabo_search_properties, hemmabo_search_availability, or hemmabo_booking_quote for those. Requires Authorization: Bearer token (MCP_API_KEY or OAuth). Read-only against the database — never writes, so it is safe to poll after a checkout timeout — but returns guest PII (name, email). Rate-limited per token. The only input is the reservationId returned by hemmabo_booking_checkout or hemmabo_booking_create — never the propertyId; without a reservationId there is no booking to look up yet.

Get the authenticated Cronofy account's details (id, email, name, default tzid, locale). API: GET /v1/account.

Get the OpenID-style profile of the authenticated user (sub, email, Cronofy profile info). API: GET /v1/userinfo.

UPDATES a customer's profile fields (first_name, last_name, email). This MODIFIES live store data. Foxy hAPI: PATCH /customers/{id}. Provide only the fields you want to change.

List delivery channels (in-app, email, push, SMS, etc.) with cursor pagination. Project API: GET /channels.

Creates a user (notification recipient) record in MagicBell. Additive — sends no notification. Provide at least one identifier (external_id or email). Project API: POST /users.

List customers, optionally filtered by store and/or email. API: GET /customers (filter[store_id], filter[email]).

List orders, optionally filtered by store and/or buyer email. API: GET /orders (filter[store_id], filter[user_email]).

List subscriptions with rich filtering by store, status, product, variant, customer, or buyer email. API: GET /subscriptions (filter[store_id], filter[status], filter[product_id], filter[variant_id], filter[customer_id], filter[user_email]).

Escribe una nota en una de tus entradas: lo que hay que hacer, lo que ya se ha hecho o lo que conviene recordar sobre esa oportunidad. Indica 'entrada_id' (el 'id' que aparece en listar_entradas o mis_novedades) y 'nota'. Si añades 'fecha' (AAAA-MM-DD), la nota se convierte en un vencimiento del calendario y se avisa por email 7 días antes y el día antes: úsala para plazos de presentación, reuniones o recordatorios. Con 'cliente' (opcional, solo modo clientes) la nota queda bajo ese cliente en vez de a la vista de todo el espacio de trabajo. Es la misma nota que se ve en boletinclaro.es. Requiere iniciar sesión.

Crea una alerta para que Boletín Claro vigile el dinero público que te interesa y te avise por email cuando salga algo nuevo que encaje. Es el paso de la búsqueda puntual a la vigilancia continua. Toma una 'descripcion' en lenguaje natural (sector o actividad, zona e importes si aplican); no necesitas saber códigos. IMPORTANTE: llama primero con confirmar=false (por defecto) para mostrar al usuario un resumen de la alerta y pedir su visto bueno; solo cuando lo confirme, vuelve a llamar con confirmar=true para crearla. Requiere haber iniciado sesión.

Crea una vigilancia de una o varias EMPRESAS concretas (competidores, clientes, proveedores) y avisa por email cuando tengan movimientos en el dinero público: contratos, subvenciones o cambios mercantiles. Para vigilar un TEMA (un sector o tipo de ayuda) usa crear_alerta; esta es para empresas con nombre y apellidos. Toma 'empresas' (nombres o NIFs separados por comas; por cada nombre se busca su NIF). IMPORTANTE: llama primero con confirmar=false (por defecto) para mostrar al usuario qué empresas se van a vigilar y pedir su visto bueno; solo cuando lo confirme, vuelve con confirmar=true. Es una función de pago. Requiere iniciar sesión.

Request a free Recao account for your human. This does NOT create an active account: it registers a PENDING one and emails your human an activation link; nothing works and no terms are accepted until they click it (the human accepts the terms at activation, not you). The API key in the response stays inert until then. Consent stays with the human, so calling this is a request, not a decision made for them: in an interactive session their approval of this tool call is the go-ahead; if you run autonomously, surface this step to your human instead of calling it. After activation, reconnect with header `Authorization: Bearer <key>`.

Show the authenticated account (plan, email, verification state), or confirm you're anonymous.

Creates a new customer in Orb (additive). Requires name and a valid email. Orb API: POST /customers.

Get a customer by id. By default `customer_id` is the Numeral id (cus_...); set id_type to "reference" to look up by your own reference_customer_id. Returns name, email, and tax-exempt status. Numeral: GET /tax/customers/{customer_id}.

MUTATES Raisely data: records a donation (use for OFFLINE/manual donations — e.g. cash or cheque). Raisely API: POST /donations with the body wrapped as { data: {...} }. Required by the API: amount (integer, in cents/smallest currency unit), currency (3-letter code), email (donor), type (ONLINE or OFFLINE), method (payment gateway, e.g. OFFLINE). Link it to a campaign/profile via campaignUuid/profileUuid. Everything else (firstName, lastName, message, date, items, public, private, ...) goes through `fields`. Returns the created donation.

MUTATES Raisely data: creates OR updates a supporter/donor, matched by email (safer than a plain create — no duplicates). Raisely API: POST /users/upsert with the body wrapped as { data: {...} }. Typed: email (the match key), firstName, lastName; everything else (phoneNumber, address, public, private, ...) via `fields`. Returns the upserted user.

Search/list users, optionally filtered by email or display name. All Quiet: GET /v1/user/search/list.

List the team members configured on a profile (booking page). YCBM API: GET /v1/profiles/{profileId} with a teamMembers field selection. Returns the profile's teamMembers block (each member has id, name, email, description, pic, calendarId).

MUTATES YouCanBookMe data: adds a team member to a profile. YCBM API: POST /v1/profiles/{profileId}/teammembers/items (JSON). Required: name; calendarId links the member to a calendar (find it via list_available_accounts). Use the `fields` passthrough for email, description, pic, etc. The path profileId is never sent in the body.

MUTATES YouCanBookMe data: updates a team member on a profile. YCBM API: PATCH /v1/profiles/{profileId}/teammembers/items/{teamMemberId} (JSON, partial update). Pass changed fields (name, email, description, calendarId, ...) via the `fields` passthrough. Path ids are never sent in the body.

Search / list the store's orders with optional filters (keyword, customer email/id, payment & fulfillment status, coupon, created-date range). Returns a paged collection. Ecwid REST: GET /orders.

Search / list the store's customers with optional filters (keyword, email, name, customer group). Returns a paged collection. Ecwid REST: GET /customers.

List a company's customers (id, customerName, contactName, emailAddress, addresses, status, defaultCurrency). Codat API: GET /companies/{companyId}/data/customers. Returns the paged envelope.

List a company's suppliers/vendors (id, supplierName, contactName, emailAddress, addresses, status, defaultCurrency). Codat API: GET /companies/{companyId}/data/suppliers. Returns the paged envelope.

列出某使用者的 Bug 報告（需提供 user_email + session_token 驗證身分）。List a user's bug reports — requires user_email and session_token.

取得某使用者當前頁面的即時 Console/Network 錯誤（需 user_email + session_token 驗證身分）。Live console/network errors — requires user_email and session_token.

取得某使用者終端機的即時錯誤日誌（stderr/throw/crash，需 user_email + session_token 驗證；付費功能）。開發者需執行 npx bugezy-watch -- <command>。Terminal error logs — requires user_email and session_token, paid feature.

Fetch a single subscriber by id or email address. MailerLite API: GET /subscribers/{id}.

Creates or updates a subscriber (upsert by email). Additive — does NOT send any email. MailerLite API: POST /subscribers.

List customers, newest first. Filter by email or creation time. Chargebee API: GET /customers.

Submit a task for the human operator to perform in the real world. Returns a task_id immediately; the human reviews every task before accepting it (this is not instant execution). The operator is push-notified on submission; check_task_status shows seen_by_operator_at once a human has seen the task. Free during the pilot. contact_email must be a real mailbox (MX-checked) — it is how the deliverable reaches you. No mailbox? Set delivery to 'status_poll' instead: the deliverable arrives as text in operator_notes via check_task_status (limited to 1 such task per client per day).

Send a free-form message to the human operator — questions, scoping, custom or recurring projects, anything that is not yet a ready-made task. reply_to is REQUIRED (an email you or your principal can read); it is the only way the operator can answer.

List customers with optional filters (email, ids, created/updated date ranges) and sorting. Returns { customers }. Pagination is cursor-based: pass `limit` (default 50, max 250) and read `next_cursor` / `previous_cursor` from the response. IMPORTANT: when paging with `cursor`, Recharge accepts ONLY `limit` alongside it — omit every other filter on cursor requests. Recharge REST: GET /customers.

List contacts (customers/vendors), newest first. Quaderno API: GET /contacts. Returns contact objects (id, kind, first_name, last_name, contact_name, email, country, tax_id, tax_status, …), wrapped as { data, pagination } when more pages exist.

Everything about ONE customer, resolved by id, email, domain, or company name: profile, subscription + MRR, how many users sit under the account, and their verbatim feedback. Read-only; returns the matched account, or an empty result when nothing matches the query. The money + people + voice join on one record — call it before answering anything about a specific account.

List all lists in the account. Returns {data:[...],paging:{...}} — each list's id, name, contact counts by status, and created_at. Paginate with `limit` (max 100) and `starting_after` (cursor from the previous page). EmailOctopus: GET /lists.

Get a single list by its id. Returns the list's full state — name, contact counts by status, and created_at. EmailOctopus: GET /lists/{list_id}.

List the contacts in a list. Returns {data:[...],paging:{...}} — each contact's id, email_address, fields, tags, status, and created_at. Paginate with `limit` (max 100) and `starting_after`. EmailOctopus: GET /lists/{list_id}/contacts.

Get a single contact in a list. Returns email_address, fields, tags, status, and created_at. `contact_id` is the MD5 hash of the lowercased email address, or the `id` returned by emailoctopus_list_contacts. EmailOctopus: GET /lists/{list_id}/contacts/{contact_id}.

List all campaigns in the account. Returns {data:[...],paging:{...}} — each campaign's id, name, status, subject, and created_at. Paginate with `limit` (max 100) and `starting_after`. EmailOctopus: GET /campaigns.

Get a single campaign by its id. Returns the campaign's full state — name, status, subject, from, content, and created_at. EmailOctopus: GET /campaigns/{campaign_id}.

Score a transaction for fraud risk. Returns the overall risk_score (0.01–99), IP risk, disposition, and remaining query funds — the lightest, cheapest assessment. Send at least device.ip_address (plus email/billing/order for a better score). API: POST /minfraud/v2.0/score.

Score a transaction AND get detailed risk insights: IP geolocation, email/address/device attributes, and per-component risk on top of the risk_score. Same request body as minfraud_score. API: POST /minfraud/v2.0/insights.

Contacts at the sponsoring company who are the likely buyers of podcast sponsorships — the people a podcaster or sales agency would pitch. Ordered by likelihood of owning the ad budget. Free to call. On credit-based plans, locked contacts come back masked (initials, no email/LinkedIn) with disclosure fields — has_email, email_domain, has_linkedin — showing what reveal_contact buys. Plans with contact data included get every contact unmasked here directly; those listings record deduplicated internal usage for billing parity (no credits are charged, nothing else changes).

Spend 1 credit to reveal a contact's full name, email, and LinkedIn URL. The unlock is permanent and org-wide: revealing an already-unlocked contact is free and never double-charges. Check the contact's has_email/has_linkedin fields from list_sponsor_contacts first so you know what the credit buys. Ask the user before revealing unless they already told you to, then set confirmed=true.