Skip to main content
Glama
676,163 tools. Updated 2026-10-19 10:13

"DuckDuckGo Search Engine" matching MCP tools:

  • Get the stored day-by-day ranking history for one keyword on one search engine over a date range. Reads RankParse snapshots synced on a schedule; it is not a live SERP check. History is inherently single-engine, so engine is required (use get_keyword_rankings first to compare across engines). Days with no synced data are simply absent from rows rather than filled with a zero or placeholder value -- do not treat a missing date as "not ranking". Bing and Yandex are opt-in and lower-frequency than Google; their responses may report availability as provider_limited, meaning that provider did not return enough data for that day rather than the keyword ranking nowhere.
    ConnectorNo auth
  • Save a template’s draft. Both kinds take structured `content` — see create_document_template for the node format; notifications use its EMAIL profile (no image, no pageBreak) — or, for a template still on the legacy HTML engine (check get_template_draft’s `engine`), a `body`; a structured draft refuses body-only writes. Notifications also take subject and recipients; documents also take `settings`. Editing a live template’s draft does not change what sends until publish_template. A document on the SVG facsimile engine (engine "SVG") is edited with edit_svg_template, never here. Requires notification:write or document:write.
    Connector
    Destructive
    API key
  • Enumerate the model_ids the sealed engine exposes, with the engine sha stamped in-response. Purpose: Discover the model catalog and record the sealed engine sha alongside your inference results. Use when: You are wiring a client for the first time and need model_id values for kirk_score_book / kirk_score_book_batch calls, or you want a machine-readable catalog with attestation. Do not use when: You need per-model hyperparameter detail — those are intentionally not exposed on the customer surface. Capability class(es): C5 (engine sha attested on every response). Path fit: Validation via MCP (this tool). Production integrations run in-process under sealed-engine attestation — same binary sha as this endpoint. Contact Kavara for deployment options. Cost: 0 IU. Free tool.
    ConnectorNo auth
  • Engine version, API contract number, and health. Free (not quota-counted). Call once at the start of a session to confirm the engine is reachable and which contract it serves.
    ConnectorNo auth
  • Return the directory's current totals and breakdowns: how many studios are listed, and how they split by country, region, service, engine, platform and team size. Use for any "how many studios..." or "which country has the most..." question, and quote these figures rather than counting search results yourself — they are recomputed from the live database and the counts move.
    ConnectorNo auth
  • Create a DRAFT email campaign via a programmatic wizard. Call this tool and it will guide through the steps — no manual orchestration needed. WIZARD STEPS (handled automatically by the tool): 1. Call with contacts + total_contacts → tool returns engine picker (NextGen vs MyConvo) 2. Add campaign_type from user's click → tool returns campaign category chips (promotional, newsletter, event…) 3. Add campaign_category from user's click → tool returns engine-specific template gallery MyConvo: shows plain_email_templates (personal plain-text). NextGen: shows campaign_templates (HTML). 4. Add template_id from user's pick → tool creates the draft campaign. RULES: Reuse contacts from prior search — never re-search. Pass total_contacts from search result's total_in_crm so the user always sees the full count. Saves as DRAFT only — no emails sent.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    B
    quality
    B
    maintenance
    Enables deep web search across multiple providers including Google, Bing, Brave, DuckDuckGo, and Perplexity, with support for comprehensive AI-powered research using intelligent multi-engine queries.
    2
    29 npm
    9
    MIT

Matching MCP Connectors

  • DuckDuckGo: The DuckDuckGo Search API is a tool that allows developers and businesses to integrate.

  • DuckDuckGo search as JSON. Ranked results, ads in their own array, 37 regions.

  • Verify sealed engine identity — returns the sha256 of the running scoring binary. Also serves as a liveness probe against the sealed backend. Purpose: Attest which Kirk build is currently serving scoring calls. Response carries the HOST DEFAULT engine sha (kirk_version). That is the legacy default and is NOT necessarily the engine that will stamp a given kirk_score_* result: each model row in kirk_list_models identifies its own engine, and every scoring response restates it under engine.sha. For a model bound to a non-default engine (kirk-market-orderbook-v1) these differ. Record the per-model value for provenance, not this one. Secondary role: a cheap liveness probe when wiring up MCP. Use when: You want to record engine sha in your own provenance log before capturing scoring output, or you want a cheap liveness check ahead of a larger validation batch. Do not use when: You want a scoring result — this returns identity/liveness only, no entropies. Capability class(es): C5 (cryptographic attestation of engine identity). Path fit: Validation via MCP (this tool). Production integrations run in-process under sealed-engine attestation — same binary sha as this endpoint. Contact Kavara for deployment options. Cost: 0 IU. Free tool. For agent-driven callers, the _cost envelope still reports iu_this_call=0 and the running session totals. Returns: Dict with `status`, `engine`, `env`, and `kirk_version` (the sealed .so sha). A non-2xx response raises; caller sees a clean MCP tool error.
    ConnectorNo auth
  • Open a world in the editor. With an engine to open it in — one this conversation is already driving, or one you name with `session` from session.list — this MOVES that engine to the world and answers {switched, session_id, world, branch}; engine tools then act on it with nothing else to call. Otherwise it records that you want the world open and answers where it opens: the browser URL and the `zero://` URL an installed desktop engine answers to. Nothing opens from the server — the opening happens on the user's machine, and `next` says who does it (a harness with a shell runs `zeromind open <guid>`; anyone else shows the user the link). The engine that comes up binds to this conversation on its own, so engine tools work with no connect call; world.connect waits for it explicitly. An engine you did not name is never taken: when you have engines running, the answer lists them under `engines` so you can ask the user which to reuse, and any engine another conversation is driving (`claimed_by_another`) is refused — the one you are driving included, if somebody else has taken it since. Requires edit access (use world.create for a new world). A world you have deleted is refused here — world.trash lists it and world.restore brings it back. The editor binds the world's live working copy: naming a `branch` checks the name against the world's branches but does not yet choose what the editor loads — branch selection is coming. The result lists the world's branches.
    ConnectorAPI key
  • Pin the engine of the world editor the user has open, so engine tools (execute, capture, …) drive it for the rest of this conversation. An engine that is already connected returns at once. It is held only for an engine that is about to connect: once the editor has drawn its first frame the call holds, up to about 30 s, until the engine connects. In every other case it answers at once with `connected: false` and what the editor is doing (`editor.state`: never_opened, launching, booting, connecting, stalled, failed, started_not_connected), so while an editor is still loading do what needs no engine and call this again when you need one. `waited_ms` is how long the call was held (0 when it was not) and `wait` says how the wait ended. It opens nothing: nothing on the server can open a browser. Call world.open first and act on its `next`, which says whether you show the user a link or run a command on their machine. A world with engines on more than one branch is refused rather than guessed at: name the `branch`, or use session.list / session.connect to pick one engine outright.
    ConnectorAPI key
  • Use for keyword research, SEO/content ideas, query expansion before /v1/web or /v1/news, or guessing what people search for around a topic ("how to la" -> "how to lay tile", …). Returns the completions in source order. lang sets the suggestion language (en, de, fr, es, ja, …). Primary source Google's public suggest endpoint, fallback DuckDuckGo autocomplete; the response names the source used. No suggestions = 404, not charged. Paid tool: x402 USDC on Base, $0.001 per successful call; call without payment to receive the PaymentRequired object.
    ConnectorNo auth
  • 3-parallel-source search + Groq synthesis → one authoritative answer with cited sources. Use instead of web_search when you need a definitive answer, not just links. Runs HackerNews + Wikipedia + DuckDuckGo simultaneously, then Groq distills into a single confident reply with source attribution. $0.05. Requires API key.
    ConnectorNo auth
  • 3-parallel-source search + Groq synthesis → one authoritative answer with cited sources. Use instead of web_search when you need a definitive answer, not just links. Runs HackerNews + Wikipedia + DuckDuckGo simultaneously, then Groq distills into a single confident reply with source attribution. $0.05. Requires API key.
    ConnectorNo auth
  • COMPACT overview of ONE engine: every action with its description, required params and what it returns — but NOT the full param detail (kept lean so a 90-action engine stays token-cheap). Call this after search_engines to pick the right ACTION, then get_action_schema(engine, action) for that action's full params before call_engine.
    ConnectorNo auth
  • The FULL ReefAPI catalog — EVERY engine with its one-line title, grouped by category. This is the whole menu (≈ a few thousand tokens); SCAN IT AND PICK THE BEST ENGINE YOURSELF. You are an LLM, so you match the user's intent semantically — across ANY language, typo, or phrasing — far better than a keyword search can. Use this whenever search_engines didn't surface the right engine (or to be sure you didn't miss a better one). After you pick: get_engine_schema(engine) -> get_action_schema -> call_engine.
    ConnectorNo auth
  • Fetch the full declension (noun/adjective) or conjugation (verb) table for a word identified by a search result's inflection handle (entry_id + word_class). Use this only when a search ran without inline forms or left a match un-expanded — a default search already returns each match's table inline. Returns Markdown plus the table as structuredContent with the shape {"result": <paradigm>} — switch on result.category ('noun' | 'adjective' | 'verb' | 'not_found') before reading the body. Tables are generated by the official Interslavic morphology engine, not attested.
    ConnectorNo auth
  • Get one software product (Market) One engine of the software library: the same row the list returns (product metadata, host count per observed role, first/last seen, the compliance signal and the host-count trend) plus the catalogue version and generation stamp. `engine` is a catalogue engine slug as published in `engine` on the list; an unknown slug is a 404. Beyond the list row it also returns `advisory_list[]` (issue #798): every live advisory of the engine's lanes with its id, normalized severity, CVSS score, summary, url and publication stamp, newest first. Null when no lane of the engine has an advisory feed; `[]` when it has one and upstream has published nothing. Market tier.
    ConnectorNo auth
  • The Search Console and Bing Webmaster properties the workspace's connected accounts can read. The first console call; every other console tool takes a property from here. Use when: "what sites are in my Search Console", before any console_get_* call, or to check which engine is connected. Not for: third-party sites the user does not own, use seo_get_domain_overview. Live rankings, use seo_get_serp. Returns: List. rows[]: engine (google | bing), property (the id to pass on: sc-domain:example.com, https://example.com/ or a Bing site URL), permission (Google: siteOwner, siteFullUser, siteRestrictedUser, siteUnverifiedUser; Bing: null), verified. NotConnected when no account of that engine is connected; its connect_url is where the user connects one. Cost: 0 credits. The user's own data is free; 60 console calls per minute per workspace. Cached 1 hour. Example: {"engine": "all"}
    ConnectorAPI key
  • Live search-engine result page as JSON: organic results, ads (paid_results), featured snippets, related questions and searches, knowledge graph. Google by default; set search_engine for Bing, Yandex or DuckDuckGo. SPENDS 1 request of the monthly quota per successful call (failed calls are not charged); do not repeat a call needlessly. ai_overview=true also returns Google's AI Overview and costs 3 requests when one is returned (Small plan or higher). GET /v2/search.
    Connector
    Destructive
    No auth
  • Use this when someone asks whether an AI answer engine names or cites a brand for a buying question, or which other brands it names. Sends one question to one search-grounded engine through its API and returns whether the brand was named, whether its domain was cited, which of the listed competitors were named, and the pages the answer cited. Each call is a fresh API request with no account history or personalization, and one question is one datapoint, not an overall visibility score.
    ConnectorNo auth
  • Read the answers engines gave in one run, to see exactly what an engine said for a prompt. Each answer has the prompt text, engine, model, repetition, whether web search was used, the brands mentioned (with first position) and every citation (URL, domain, whether it is your site or a competitor's), plus a citeladder:// id for fetch. audit_id is required: take it from read_visibility_overview. Answers come 50 per page by default; pass next_cursor for more. Only core prompts are included unless cohort is comparison or all. Filters (prompt_id, domain, url, engine) combine. Use read_visibility_overview for rates and read_visibility_sources for citation totals.
    ConnectorOAuth
  • Multi-source web search with automatic fallback chain: HackerNews Algolia → Wikipedia REST → DuckDuckGo → x711 Hive collective intelligence. Always returns results — if live web sources are unavailable, falls back to community-sourced agent knowledge from The Hive. Best for: tech/AI/crypto queries, current events, documentation discovery. Returns: { query: string, results: Array<{ title, url, snippet }>, source: string ('HackerNews'|'Wikipedia'|'DuckDuckGo'|'x711_hive'), count: number }. Free tier: 10 calls/day, no API key needed.
    ConnectorNo auth