The MCP tool directory.

Lists the toll-free verifications this workspace holds, newest first. Filter by `status` to separate the drafts still being filled in from the ones a carrier is holding.

Lists everything the carriers ask for before they will review a toll-free verification, in the order to present it, with what you have already supplied and where each item stands. Read it with no verification named to get the blank form before starting one, or name a verification to see its own answers. An item's `state` says where it stands, and this read emits five: `not_supplied` asks you for the value; `supplied` means a draft holds it; `in_review` means the carrier holds the whole dossier, so nothing can change; `approved` and `rejected` are the carrier's verdict on the dossier, shared by every supplied item, and `reason` carries its words on a refusal. The set is open, since review can gain stages; a state you do not recognise is not yours to act on.

Fills in the business and messaging details of a verification that is still editable: a draft, one the carrier sent back asking for more, or a rejected one while its resubmission window is open. Send only the fields that change; anything omitted is left as it was. A submitted, under-review, or approved verification is locked.

Automatically solve CAPTCHAs on the current page using CapSolver AI. Supports Cloudflare Turnstile, reCAPTCHA v2/v3, and hCaptcha. Detects the CAPTCHA type and sitekey automatically, sends it to CapSolver for solving, injects the token, and optionally submits the form. Use this when a CAPTCHA blocks form submission during browser automation.

Find Hugging Face Spaces using semantic search. IMPORTANT Only MCP Servers can be used with the dynamic_space toolInclude links to the Space when presenting the results.

Retrieve the full text, metadata, and references of one Space Frontiers document. Use when: you have a `source_uri` from a search hit and need the body to quote, summarize, or extract structured facts; or you want to walk the citation graph via `references` and `referenced_by`. Do not use when: you have not yet found the document — call a `spacefrontiers_search_*` tool first to obtain a real `source_uri`. Do not guess DOIs. Returns title, authors, abstract, content (truncated above ~100K chars), references with URIs, and up to 30 `referenced_by` documents you can fetch next. For documents over ~20K tokens prefer `spacefrontiers_search_in_document` to extract only the passages you need. Examples: `https://doi.org/10.1038/s41586-023-06924-6`, `arxiv:2301.00001`, `pmid:38019072`.

Search peer-reviewed papers, books, patents, and Wikipedia in the Space Frontiers `documents` index. Use when: the user asks about scientific concepts, technical methods, prior art, citations, a DOI / ISBN / arXiv ID / PubMed ID, or wants peer-reviewed sources. Do not use when: the question is about news, current events, ongoing discussions, or social sentiment — call `spacefrontiers_search_social` instead. For general web pages or code, use a different MCP server. Examples: "crispr base editing efficiency", "doi:10.1038/s41586-023-06924-6", "isbn:9780262033848", "arxiv:2301.00001", "transformer attention scaling laws". Tips: - Run 2-6 parallel queries with varied phrasings (synonyms, narrower/broader terms). - Pass an empty `query` plus `filter_issns` to browse recent issues of a specific journal. - Use the returned `source_uri` verbatim with `spacefrontiers_fetch_document` for full text.

Find specific passages inside one Space Frontiers document without reading the whole body. Use when: the document is large (size > ~20K tokens shown in `content_size_tokens`) and you only need the parts relevant to a sub-question, e.g. "what error rates does this paper report?" against a 60-page review. Do not use when: you need the entire document to summarize or quote in full — call `spacefrontiers_fetch_document` instead. Do not call this without first obtaining a real URI via search. If no passage matches the query, the full document is returned in `fallback_full_document` so the caller never has to retry with a second tool call.

Search Reddit, Telegram channels, and YouTube transcripts in the Space Frontiers `social` index. Use when: the user asks about news, recent events, announcements, ongoing discussions, community opinions, or anything time-sensitive that wouldn't be in peer-reviewed literature. Do not use when: the question is about settled scientific knowledge, citations, or prior art — call `spacefrontiers_search_documents` instead. For general web search, use a different MCP server. Examples: "openai gpt-5 release date", "site:reddit.com/r/LocalLLaMA quantization", "@telegram_channel breaking news", "kubernetes 1.33 changes discussion". Tips: - Pair an empty `query` with `filter_uri_prefixes` to browse a subreddit or Telegram channel chronologically (combine with `filter_issued_after` for a time window). - For broad topics, also call `spacefrontiers_search_documents` in parallel for grounded sources.

Search special administrative appeal decisions (특별행정심판 목록 조회). Search decisions from Korean special administrative appeal tribunals. Args: tribunal: Tribunal name in Korean. Valid values: 조세심판원, 해양안전심판원, 국민권익위원회, 인사혁신처 소청심사위원회 query: Search keyword (default "*") display: Number of results per page (max 100, default 20) page: Page number (1-based, default 1) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" search: 1=사건명 (case name), 2=본문검색 (full text) sort: Sort order gana: Dictionary search cls: 재결례유형 (decision type classification) date: Reference date (YYYYMMDD) dpa_yd: Decision date range (YYYYMMDD~YYYYMMDD) rsl_yd: Resolution date range (YYYYMMDD~YYYYMMDD) ctx: MCP context (injected automatically) Returns: Special appeal decision list or error Examples: Search 조세심판원 decisions: >>> special_decc_search(tribunal="조세심판원", query="부가가치세")

Retrieve special administrative appeal decision full text (특별행정심판 본문 조회). Args: tribunal: Tribunal name (same values as special_decc_search) id: Decision serial number (재결례일련번호) oc: Optional OC override type: Response format - "JSON" (default), "XML", or "HTML" ctx: MCP context (injected automatically) Returns: Full decision text or error

Returns Naver's spelling correction for a misspelled search query (오타변환).

Returns Naver's spelling correction for a misspelled search query (오타변환).

Fetch SPF info for a given domain or host

Exchange an access token for a user's [Profile](/reference/sso/profile). Because this profile is returned in the [Get a Profile and Token endpoint](/reference/sso/profile/get-profile-and-token) your application usually does not need to call this endpoint. It is available for any authentication flows that require an additional endpoint to retrieve a user's profile.

Star a GitHub repository

Spends one researched cluster from the plan. Researches a topic deeply into a durable dossier: four search engines are each asked their own questions, the best sources found are fetched and read, and the claims extracted from them are merged into one list with source URLs, dates, the points where sources disagree, and the questions the research could not settle. Runs as a background job — poll get_research_dossier or wait_for. Research a topical cluster once and let its articles draw different subsets; researching per article costs more and is what makes articles in one cluster sound alike. Pass planId + workstreamId to research a workstream (its title, goal, audience and brand keywords are used automatically, and the workstream's existing dossier is reused), or topic for a free-form one. A workstream-bound run also proposes articles from the dossier when it finishes.

Find all train line transfer options at a specific subway station

Discover stocks that align with your investment strategy using the FMP Stock Screener API. Filter stocks based on market cap, price, volume, beta, sector, country, and more to identify the best opportunities.

Get detailed parameter information for a specific Stripe API operation. Provide the stripe_api_operation_id from stripe_api_search results to see all path, query, and body parameters with their types, descriptions, and whether they are required.

Execute any Stripe API operation: 1. Use stripe_api_search to find the operation ID. 2. Use stripe_api_details to understand its parameters (required for operations with nested object fields like address, metadata, or restrictions). 3. Call this tool with the stripe_api_operation_id and a parameters object containing path, query, and body parameters. Nested object fields use dot-notation (e.g. "address.city").

Search for Stripe API operations by keyword. Returns matching operations with their HTTP method, path, summary, and top-level parameter names with types. Does not include parameter descriptions, enum values, or nested object fields — use stripe_api_details to get those before calling stripe_api_execute.

Guides users through Stripe integration planning via interactive Q&A. Analyzes payment requirements and recommends the appropriate Stripe products (Checkout, Elements, Billing, Connect, etc.) with step-by-step implementation guidance. WHEN TO USE: Call this tool when the user expresses: - Payment keywords: "payments", "checkout", "billing", "subscriptions", "invoices" - Commercial intent: "sell", "monetize", "charge users", "e-commerce" - Stripe mention: User references "Stripe" directly IMPORTANT BEHAVIOR: - You may call this tool with partial information—the tool will ask clarifying questions. Do not wait until you have complete requirements. - Once a plan is in progress, stay in the Q&A flow until completion. If the user asks for clarification or advice (e.g., "what's best for me?"), answer them, then continue with the plan. Only exit early if the user explicitly requests it or the tool returns an unrecoverable error. - When the tool returns type="question", present the question to the user exactly as provided. PARAMETERS: - plan_id (optional): Required for continuing/updating. Omit when starting new plan. - answer (required): For new plans, provide summary. For existing plans, provide user response. Accepts option selections ('Option 1'), natural language, clarifying questions, or 'UNKNOWN'. - notes (optional): Technical context you've observed (e.g., "Python/Flask backend", "user wants minimal code to go live quickly", "already has Stripe SDK installed"). Returns JSON: - type="question": Plan in progress. Contains `question` to present to user and `plan_id` to include in next call. - type="summary": plan_id, status, summary (blueprints, prerequisites, sample_code) - type="error": status, error (code, message, user_visible, agent_guidance) WORKFLOW: - New plan: Call without plan_id + answer → Present question EXACTLY → Get answer → Call with plan_id + answer → Repeat - Continue plan: Present question EXACTLY → Analyze code → Formulate answer → Get approval → Call with plan_id + answer + notes → Repeat LIMITATIONS: - Generates integration guidance only; does not execute code or create Stripe resources. - Cannot modify completed or expired plans—start a new plan instead.

Add a sub-issue to a parent issue in a GitHub repository.

Search generated registry artifacts for likely duplicate entries before a user opens a submission PR.

Fetch read-only category examples and templates for faster, more accurate HeyClaude submissions.

Fetch category-specific HeyClaude contribution guidance, required fields, and review expectations.

Fetch HeyClaude's read-only submission, artifact, import, and maintainer-review policy for contributors and agents.