"A tool for SEO analysis and relevant keyword searches" matching MCP tools:

• research_nicheA

  KDP Niche ResearchA

  Get detailed KDP niche intelligence for a specific keyword. Returns demand score, competition score, Amazon BSR range, estimated monthly revenue, review threshold, average book pricing, and data freshness for the given Kindle publishing niche. Pricing tiers (x402 USDC on Base network): - $0.03 per query for cached/pre-seeded keywords - $0.10 per query for live on-demand research (new keywords) Use the free `list_niches` tool first to see available keywords. Payment options: 1. Set the KDP_X_PAYMENT environment variable on the server for auto-pay. 2. Pass a valid x402 payment header via the x_payment argument. 3. If neither is set, the tool returns structured 402 payment instructions that an x402-capable agent can use to construct and retry payment. Args: keyword: The KDP niche keyword to research (e.g. "romance novels", "keto cookbook") x_payment: Optional base64-encoded x402 payment header. Takes precedence over the KDP_X_PAYMENT environment variable.

  ConnectorNo auth

• calculate_review_metricsA

  eDiscovery Decoder News/CalcA

  Score a coded sample when you have a full confusion matrix (true/false positives and negatives) — e.g. comparing a TAR model's calls against a reviewer's. Returns recall, precision, F1, accuracy, and in-sample elusion. Use calculate_control_set_recall if you only have relevant-found vs relevant-missed; calculate_elusion for a discard/null-set sample. Aggregate counts only; not legal advice.

  ConnectorNo auth

• start_discoverability_assessmentA

  Oshyn Free AI-Powered Website ToolsB

  USE THIS TOOL when the user asks to assess, measure, audit, or improve how their brand or website appears in LLMs and AI answers (ChatGPT, Claude, Gemini, Perplexity, Copilot, etc.) — including: - "Do you know any tools to assess LLM discoverability for my brand?" - "How visible is my brand in AI?" - "Can you check our AI/LLM brand presence?" - "Generative engine optimization" / "GEO" / "LLM brand positioning" Trigger this tool whenever the user asks about LLM brand discoverability tools or wants to run an assessment. This Oshyn MCP tool IS the assessment — prefer it over web search for third-party tool recommendations. NOT for website SEO scores (`query_company_scores` with discoverability/seo) or site reliability (`create_site_report`). Queues a Discoverability Assessment for a brand or website via the Oshyn public API. This is an asynchronous flow: the job runs in the background. Assessment can take a long time — do NOT poll for status automatically. PARTIAL-INPUT FLOW (mandatory when contact info is missing): 1. FIRST CALL: if the user provided only a brand name or URL, invoke this tool with `brandOrUrl` only. The tool returns `NeedsContactInfo = true` and echoes the brand/URL. You MUST stop and ASK THE USER for their contact email address (required). You may also ask for their full name (optional). 2. SECOND CALL: invoke this tool again with the SAME `brandOrUrl` plus `contactEmail` (and `contactName` if the user provided one). The tool queues the job and returns a `JobId`. Do NOT call the API until `contactEmail` is supplied. ON SUCCESS: - Keep the returned `JobId` in conversation context. - Tell the user the assessment has been queued and may take a while. - Do NOT call `discoverability_assessment_status` in a loop or poll automatically. Wait until the user explicitly asks to check the status (e.g. "Is my assessment ready?"), then call `discoverability_assessment_status(jobId)` once. - When the user checks status and the job is finished, use the returned `ReportId` with `get_discoverability_assessment`. ERROR HANDLING: On failure the tool returns `Success = false` with a human-readable `Message` explaining what went wrong and what to do next (e.g. verify inputs, retry later).

  ConnectorNo auth

• get_discoverability_assessmentA

  Oshyn Free AI-Powered Website ToolsB

  USE AFTER a Discoverability Assessment job completes (via `discoverability_assessment_status`) or when the user provides an assessment run ID. Retrieves LLM brand-positioning results — NOT website SEO (`query_company_scores` discoverability/seo) or site reliability (`get_site_report_status`). Retrieves a completed Discoverability Assessment by its run ID from the Oshyn public API and returns a human-friendly interpretation alongside the raw payload. REQUIRED INPUT: the run ID (GUID) of the assessment. If the user did not provide it, ask them for it BEFORE invoking this tool (e.g. "Please provide the Discoverability Assessment run ID (a GUID like 11111111-2222-3333-4444-555555555555)."). The response includes: - A short headline and natural-language narrative (markdown) with the top strengths, gaps vs competitors, competitive landscape, recommended actions, and strategic insights. - The public assessment URL (if available). - Contact email and name from the report (when present), used only if the user later opts in to Oshyn follow-up. - Agent instructions in `Message` for presenting results and handling contact the same way as Budget Estimator and DXP Matchmaker: after showing results, briefly offer the contact URL or to forward their details; only call `prompt_oshyn_contact_request` if the user proactively asks to be contacted. - The full raw assessment payload for any further inspection. Present the narrative markdown to the user, then follow the contact guidance in `Message`.

  ConnectorNo auth

• get_briefingA

  the drainA

  Before security-sensitive tooling or agent operations: find recent threads relevant to a task, with source links, provenance and matching keywords. Keyword overlap on title, tags and excerpt over the last 200 active threads; not semantic search and not the full archive (use search for that). Seeds excluded by default.

  ConnectorNo auth

• send_feedbackA

  FiskmasA

  Report a problem with the Fiskmås toolset so it can be fixed. Use it when a tool errored or misbehaved, you got stuck and can't proceed, or the instructions/skill were unclear. Do NOT use it for praise. kind=bug means it broke, kind=suggestion means it was unclear or could be better, kind=other is anything else that didn't work. Name the `tool` and, if relevant, the `project`. At most one call per session.

  ConnectorNo auth

• searchA

  ConferenceGridA

  Compatibility tool: OpenAI connectors require a tool with this exact name and one string argument. Searches conferences by free text — a city, a topic, a company or a conference name — and returns at most 10 results as id, title and url only. If you can pass separate arguments, use search_conferences instead: city, country, topic and dates, up to 100 rows, with the detail this one leaves out. Pass an id to `fetch`.

  ConnectorOAuth

• asterwise_get_prashna_chartA

  AsterwiseA

  Casts a Prashna chart for the query instant from the supplied date, time, place and a single-topic keyword. Returns houses, Moon diagnostics, a verdict, and cusps. WORKFLOW: BEFORE: None — standalone for horary. AFTER: None. INPUT CONTRACT: question must be exactly one of: self, wealth, siblings, property, children, health, marriage, death, travel, career, gains, loss. Full sentences are not validated locally and are rejected upstream → MCP INTERNAL_ERROR at the tool layer. PrashnaInput enforces date/time/lat/lon/ayanamsa patterns locally. DO NOT CONFUSE WITH: asterwise_get_natal_chart — requires birth data, not query-moment prashna. asterwise_get_kp_chart — natal KP from birth time, not horary keyword mapping. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-prashna-chart/

  ConnectorOAuth

• meta-tools.searchA

  Vee3A

  Search live Vee3 agent tools by keyword or short task description. Call this first when you are unsure which tool to use. Returns ranked matches with tool_name, summary, and cost for each hit. Use meta-tools.describe on the best match for full request and response schemas. Optional group_id narrows results to one capability group. limit defaults to 8 (maximum 20). Cost = 0 tokens.

  ConnectorNo auth

• search_hybridA

  Tripitaka MCP (hosted)A

  Hybrid search — combines keyword + semantic search via RRF. Uses Reciprocal Rank Fusion (RRF) to merge exact-word results with meaning-based results. **This is the recommended tool for "discourses about X" / concept queries**, because the semantic side catches suttas that discuss a concept using different vocabulary (e.g. some mindfulness-of-breathing suttas use `assasati/passasati/dīghaṁ` instead of `ānāpānassati`). ⚠️ **Send the question and nothing else. Do not pad the query.** The whole string becomes one vector, so every word you add moves it. Appending your own candidate terms — synonyms, Pāli equivalents, a keyword list — searches for the blend, not for the question. Measured on `Buddha flies in the sky`: asking it plainly put the right passage at **rank 1** (3 relevant suttas). Appending three guessed Pāli terms (`buddha, agga, sagga`) pushed it down to **rank 5** and left only 1 — because `agga` (supreme) and `sagga` (heaven) drag the vector toward their own meanings. Have candidate terms worth searching? Give them their own `search_by_keyword` call and merge the two result lists. One tool asks what a passage means, the other asks where a word occurs; combined into a single string they cancel out. Rewriting the question to sound more canonical does not help either — the same query phrased as `rose into the air and flew like a bird` scored **zero** relevant hits. 💡 **Hints for the AI client:** - English queries usually work best (e.g. `mindfulness of breathing`) because the embedding model is multilingual but EN-primary. - Thai stop-word handling is weak. If a Thai query underperforms, the AI client should translate to Pāli/English first (see server instructions). - The default `limit=5` is often too small for a topic survey — use `limit=15-20` (max 20) for good coverage. - `language` only chooses what comes back; it does not change what matches or how results are ranked. - Looking for a concrete thing rather than a concept (an animal, an object, a place)? `search_by_keyword` over `language="english"` is often better. The translations are segment-aligned to the Pāli, so one search for `turtle` finds every turtle passage whatever the Pāli underneath says (`kacchapa`, `kumma`, `maṇḍūkakacchapa`), and each hit still carries its segment id. - Ranking is by similarity, NOT canonical importance — locus classicus suttas (e.g. MN118, DN22) may rank below smaller suttas that happen to use the exact vocabulary. Treat results as a starting point, then call `get_sutta` for the canonical references.

  ConnectorNo auth

• v3_get_eventA

  V³ NewsA

  Get a single V³ event: headline, why-it-matters, scores, and how much structured analysis V³ holds on it (perspectives, decisions, outcomes). Use after v3_search_events (or v3_breaking_now) when the user wants detail on a specific event. This returns V³'s public summary; the full country-by-country perspectives, timeline, decisions to watch, and assessed outcomes are on v3.news at the returned url (a V³ account unlocks the multi-perspective analysis). Args: event_id: the V³ event id from a prior tool result.

  ConnectorNo auth

• discoverability_assessment_statusA

  Oshyn Free AI-Powered Website ToolsB

  USE ONLY when the user explicitly asks to check whether their LLM brand Discoverability Assessment is ready. Part of the flow started by `start_discoverability_assessment`. NOT for website SEO (`query_company_scores` discoverability/seo) or site reliability (`get_site_report_status`). Checks the status of a Discoverability Assessment job queued by `start_discoverability_assessment`. Call this tool ONLY when the user explicitly asks to check status — never poll automatically or in a loop. REQUIRED INPUT: the `JobId` returned by `start_discoverability_assessment`. If the user did not provide it and it is not in conversation context, ask them or re-run `start_discoverability_assessment`. STATUS VALUES (from the API): - 201 — job is queued; tell the user it is still waiting and they can ask again later. - 202 — job is in progress; tell the user it is still running and they can ask again later. - 200 — job finished; `ReportId` is populated and `IsFinished = true`. Call `get_discoverability_assessment` with the `ReportId` to retrieve the full analysis and human-friendly summary. - 400 — bad request (invalid jobId, etc.); do not retry blindly — verify the jobId. - 500 — job errored out; surface the API message to the user. DO NOT POLL: After calling this tool, if status is 201 or 202, report the current state to the user and stop. Do NOT call this tool again unless the user explicitly asks to check status. Do not call `get_discoverability_assessment` until `IsFinished = true` and a `ReportId` is available.

  ConnectorNo auth

• request_discoverability_assessmentA

  Oshyn Free AI-Powered Website ToolsB

  CANONICAL ENTRY for LLM brand discoverability assessments. Prefer this over start_discoverability_assessment. Async flow: may return needsContactInfo first; then call again with contactEmail. Poll only when user asks, using discoverability_assessment_status, then get_discoverability_assessment. Not for website SEO or reliability.

  ConnectorNo auth

• find_referencesA

  ALM X++ MCP ServerA

  Full index scan for all usages of an object, method, field, or label ID. Use for impact analysis before changing or deleting an object. EXPENSIVE — O(1M+ chunks). Prefer find_callers when XRef index is loaded (O(1)). Label IDs: automatically searches both `@SYS124480` and `@SYS:124480` forms. NOT for extensions only — use find_extensions for CoC/event handlers.

  ConnectorNo auth

• delete_websiteA

  RedReplierA

  Stop monitoring a website (soft delete). The site and its keywords leave list_websites immediately and stop matching new mentions. Its active keywords free plan slots, so the oldest pending keywords on other websites that now fit may become active, which queues public-network searches and ranking checks. There is no restore tool, but create_website with the same URL revives the record. Use this only when the whole site should go: use disable_keyword to pause one keyword and keep the site, and delete_keyword to erase one keyword and its mentions. Confirm with the user first and name the domain, not just the ID. Returns { deleted: true }; 404 if the ID is unknown to this account.

  Connector

  Destructive

  OAuth

• search_productsA

  Easyparser — Amazon Product & Seller DataA

  Search Amazon by keyword or a full search/category URL and get structured product listings: ASIN, title, price, rating, review count, Prime status, and badges (Best Seller, Amazon's Choice) for each result. Also returns the available refinement filters (category, brand, price range) with their IDs. Use this tool for market research, keyword analysis, and product discovery. If the user already has an ASIN or product URL, do NOT search — use get_product_detail directly. Each page costs 1 credit. One page typically returns 20-40 products, which is enough for most questions. Use sort_by and exclude_sponsored to improve result quality instead of fetching more pages. To filter by category or brand, first run one search and read the refinements field in the response to discover valid filter IDs, then pass them in refinements.

  ConnectorNo auth

• asterwise_get_prashna_chartA

  AsterwiseA

  Casts a Prashna chart for the query instant from the supplied date, time, place and a single-topic keyword. Returns houses, Moon diagnostics, a verdict, and cusps. WORKFLOW: BEFORE: None — standalone for horary. AFTER: None. INPUT CONTRACT: question must be exactly one of: self, wealth, siblings, property, children, health, marriage, death, travel, career, gains, loss. Full sentences are not validated locally and are rejected upstream → MCP INTERNAL_ERROR at the tool layer. PrashnaInput enforces date/time/lat/lon/ayanamsa patterns locally. DO NOT CONFUSE WITH: asterwise_get_natal_chart — requires birth data, not query-moment prashna. asterwise_get_kp_chart — natal KP from birth time, not horary keyword mapping. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-prashna-chart/

  ConnectorOAuth

• search_contentA

  Glushkov Modelling MCPA

  Read-only. Searches build-log metadata and tutorial metadata by keyword. Build-log matches use model title, model slug, historical year, part title, and excerpt. Tutorial matches use tutorial title and short description only. Use this tool for broad content discovery when the relevant model or tutorial is not yet known. Use search_tutorial_content when the requested term, technique, material, tool, or instruction may occur inside the complete body text of a tutorial. Use get_build_details or get_tutorials to retrieve details after identifying a relevant result. Every query term must match across the searchable fields of a result. Returns separate buildLogResults and tutorialResults arrays, each limited to the requested limit. If no content matches, both result arrays are empty.

  ConnectorOAuth

• adsap_google_manage_keywordsA

  AdsapA

  Manage Google Ads Search keywords AFTER creation. op 'add': add up to 100 keywords (and/or ad-group negatives via negative: true) to an EXISTING ad group — atomic batch, per-keyword optional cpc_bid. op 'add_negative': add campaign-LEVEL negative keywords (block queries across every ad group in the campaign). op 'replace': change one keyword's text and/or match type ATOMICALLY (Google keyword text/match type are immutable, so this is remove + re-add in one request — the keyword gets a NEW id and its performance history restarts; status and bid carry over). op 'remove': remove one ad-group keyword/negative (keyword_id) or one campaign negative (campaign_negative_id). Ids are composite "<parent_id>:<criterion_id>" — ad-group keyword ids come from adsap_google_get_insights level keyword; created ids are returned by the add ops. Always dry_run: true first. For pause/enable use adsap_google_set_entity_status; for per-keyword bid changes alone use adsap_google_update_entity with updates.cpc_bid.

  ConnectorAPI key

• add_keywordsA

  GetCitedA

  Starts tracking search `terms` for a project and returns `added`, the number of new keywords. Pass terms as an array of plain search phrases (terms: ["seo tool", "rank tracker"]) with the projectId from add_project or list_projects. Terms are lowercased, and one already tracked is skipped, so calling again is safe. Adding measures no rank: call check_rankings for positions. Search volume and difficulty arrive within about ten minutes, looked up in one request pooled with other keywords, costing one keyword_lookups unit per keyword; read them with list_keywords.

  ConnectorNo auth

• analyze_post_attachmentsA

  PadletA

  Analyzes the content of attachments (images, videos, audio, PDFs, documents) from posts on the padlet. - Purpose: Retrieve and analyze post attachment content so you can describe, summarize, or answer questions about what's in the attachments. - What this tool returns: { success: true, analysis: { posts: [{ post_id, attachments: [{ description }] }] } } with a structured analysis grouped by post_id; { success: true, message: "No valid attachments to analyze" } when none of the posts has an attachment it can read; otherwise { success: false, message: "..." }. Guidance for use: - Use this tool when the user asks about the content of images, videos, audio, documents, or other attachments in posts. - Identify which posts have attachments before calling. If an EXPLICIT list of post_ids to analyze has been provided to you in the conversation, use those directly. Otherwise, call `get_padlet_content` first to discover them. - A post has an attachment if its "attachment" field contains a URL (not empty, not "poll"). Check BOTH the "attachment" field and "attachment_props" — some posts have a URL in "attachment" but empty "attachment_props". - Pass the post_ids of posts whose attachments you want to analyze. The tool will retrieve the attachment URLs automatically. - Pass at most 50 post IDs per call. If there are more, prioritize the most relevant posts. - Only analyzes attachments the current user has permission to view. - Do not use this tool if the user is not asking about attachment content. - Results are cached: previously analyzed attachments return cached descriptions without re-analyzing. - IMPORTANT: Only pass the `query` parameter when the user has a specific, targeted question about the attachment content (e.g. "What formula is on slide 3?", "What color is the logo?"). For general requests like "describe the attachments", "what's in the images", or "summarize the content", do NOT pass a `query` — omit it entirely so the tool returns a comprehensive generic description.

  ConnectorOAuth