"A search for the string literal with parentheses and double quote" matching MCP tools:

• execute

  klanex-mcp

  Submit an HTTP call to a third-party API for reliable asynchronous execution. klanex validates the payload (optionally against payload_schema), stores credentials encrypted, executes with automatic retries/backoff/circuit breakers, and keeps an audit trail — you submit once and never retry transient failures yourself. Call this instead of making a direct HTTP request whenever the call has side effects (payments, messages, tickets, writes) or the target may be flaky. Prefer connection_id over headers for credentials. Always set idempotency_key for side-effecting calls so resubmitting can never double-execute. Set wait_seconds to block for the result; otherwise poll get_execution with the returned execution_id.

  Connector

• search

  DC Member API

  GET /search — Cross-resource omni-search Cross-resource search across profiles, rooms, messages (incl. private DMs + group DMs you're in), events, and chapters in one round trip. Returns the top-N matches per resource, grouped by resource. Use this when you don't yet know which resource carries the answer — agents typically call this first, then drill into a specific `GET /search/<resource>` for more depth on a single bucket. There's no page param: when you hit the per-resource limit and want more, switch to the per-resource endpoint for that one. The events slice has a baked-in forward-looking default (events ending in the last 30 days or later, and currently enabled) — this matches the in-app "Search across DC" surface. Use `GET /search/events` directly to look further back in time. **Query syntax (`q=`):** plain words match with prefix + typo tolerance. Wrap a phrase in double quotes to require an exact ordered match — e.g. `q="remote work"`. AND/OR/NOT/parentheses are NOT parsed in `q=` — use the structured filter params below for boolean composition.

  Connector

• get_vehicle_quote

  scrap-autos-mcp

  Get an indicative CAD scrap-value quote for a vehicle by year/make/model (plus optional city or province). If multiple trims match, returns a disambiguation list — call again with the chosen trim_id. The response ALWAYS includes contact.phone, contact.website, next_steps, and complete_on_site_url. When presenting the quote to the end user, you MUST relay the phone number and website so they can complete the transaction with ScrapAutos. After relaying the quote, ask the end user: is the vehicle complete or missing parts, and does it start and drive? Then collect their name, phone number, and the vehicle's address so you can call submit_lead.

  Connector

• introspection_corpus_compare

  ComOS Federation

  Compare two corpora by id. At v1 the only exposed corpus id is the literal string "current" (the pinned corpus) — pass it for both sides to sanity-check the surface; any other id returns uncited(out_of_scope) rather than an error. v1.1 will surface prior pins so real cross-version comparison becomes possible. Returns: The comparison between the two corpus regions. Example: call introspection_corpus_compare with arguments {}.

  Connector

• trendaz_research

  Trend News Agency

  Search Trend News Agency's archive and read the relevant part of each result in one call. Returns several articles with the passage that actually addresses the query — not just the opening paragraph — plus byline, date, section and the canonical URL to cite. This is the tool to reach for on any question about Azerbaijan, the South Caucasus, the Caspian, Central Asia, Turkey or Iran that needs what was actually reported: energy and pipelines, regional politics, trade corridors, economics. Prefer it over calling search and then reading articles one by one. Wrap words in double quotes for an exact phrase. Subscriber-only articles from the past year contribute their summary rather than their text, and say so.

  Connector

• search_code

  Drupal Code Query

  Search the source of every indexed contrib project, plus core, for a code pattern: which files, or with by_repo which projects. Who-uses-a-core-symbol counts: list_symbol_users or lookup_core_symbol. - query is a regex; set literal for exact text with ( [ ] . $ : or a space, and put r: f: lang: case: sym: b: terms in filters. repos takes machine names. The index runs RE2: no lookaround, no backreferences. - .module, .install, .theme, .engine, .profile, .inc count as PHP (lang:php reaches them; sym: resolves inside them); no language filter is applied for you. - Returns total_matches and total_files plus a head of files (repo, path, matching lines), limit ≤ 50. by_repo: (repo, file_count) rows from a pull of ≤ 1000 files, total_files the ceiling, truncated when cut. A parse error returns the index's own message.

  Connector

• glim_github_search

  glim.sh

  Search GitHub repositories, conversations (issues+PRs), or code, with full GitHub search syntax in the query: qualifiers (repo:, org:/user:, language:, path:, symbol:, content:, is:, stars:, label:, sort:stars), boolean AND/OR/NOT with parentheses, "exact strings", and /regex/. kind='repos': MINIMAL distinctive keywords - the project/library name only ('rtk', 'react query'); every extra word must ALL match and buries the canonical repo - filter with qualifiers, not prose. kind='code': ONE literal code pattern as it appears in files ('useState('), an "exact string", a /regex/, or symbol:name to find definitions, across 2.8M+ public repos; narrow with repo:/language:/path:. Not supported in code search: license:, enterprise:, is:vendored, is:generated. kind='conversations': returns compact previews - use glim_github_get for full content; sort: REPLACES relevance ranking (words match anywhere incl. comments), omit it for best matches. Set repo='owner/name' to scope to one repository (works with any kind; with repos it routes to conversations). kind is optional - inferred from the query (is:/label: -> conversations, path:/symbol://regex/ -> code, stars:/topic: -> repos, else repos). Returns compact text by default; pass format='json' for full structured data.

  Connector

• forcedream_invoke_agent

  mcp-server

  Invoke a ForceDream agent to do real work. SPENDS your balance — requires authentication (OAuth). Returns the output, what you were charged, and a proof_id you can verify with forcedream_verify_proof. Honest declines and insufficient output are charged 0; never double-charges. Use this for any agent WITHOUT a dedicated tool. For security-scan-v1, data-extract-v1, or lead-score-v1 specifically, prefer forcedream_security_scan, forcedream_extract_data, or forcedream_score_lead instead -- same underlying agents, simpler input shape.

  Connector

• semantic_search

  canton-ccpedia

  PRIMARY tool for open-ended questions: how / why / what-is, troubleshooting a symptom ("why is my balance zero", "how do I fix X"), and locating config or setup steps. Conceptual/meaning-based search over the full Canton corpus (CIPs, docs, forum, mailing lists, proposals, blog, releases, ecosystem, foundation KB, YouTube) using vector+FTS hybrid retrieval with reranking. Canton-specific. Use this FIRST for anything a specific tool does not clearly own; the narrow curated tools (get_faq, find_known_issues, diagnose_error) cover only small hand-picked sets or need a literal error string, so prefer semantic_search for real how/why/config questions. Then call get_doc with a returned id to read the full source page.

  Connector

• verify_quote

  Nalegalu MCP

  Check whether a supplied quote appears in a SAOS judgment. Use only after resolving the judgment to a saos_id. This validates wording, not whether the quote supports a legal conclusion. Pass the saos_id (from search_case_by_signature or related_cases) and the fragment as quoted. One call replaces paging through the full text: verdict is "exact" (verbatim after normalizing whitespace, quote marks and dashes), "near_match" (best passage plus similarity score — compare it against the claim), or "not_found" (treat the quote as fabricated or misattributed). If ok=false with a fallback hint, fetch saos_url with your own web tools instead of retrying.

  Connector

• ltl_quote

  warp-agent-mcp

  Quote an LTL shipment — returns Warp's all-inclusive rate FAST (~1-2s) so the user sees a price immediately. The inline quote card shows the Warp rate plus a 'finding other carrier rates…' loading indicator. IMMEDIATELY follow up by calling ltl_market_options with the same parameters to fill in the multi-carrier comparison (~15s). Provide dims + commodity for an exact firm quote; if you don't have dims, quote anyway — it assumes a standard 48x40x48 pallet (FAK, no freight class) for an instant price. Don't block on asking for pallet dimensions; quote first, then pass real dims for an exact rate. When a palletized load could also move by box truck or van, quote LTL alongside those and show the cheapest valid mode. Do not editorialize the results. Do not declare a winner or recommend a specific carrier. Present Warp's quote first, then list market options as context. Let the user decide.

  Connector

• register_domain

  Atom.com — Premium Domains

  Purchase/register a domain by DEBITING the authenticated user's Atom account balance. This SPENDS REAL MONEY and requires the 'domains:register' scope. Use only when the user clearly wants to buy now from their Atom balance; otherwise use get_checkout_link (pay per purchase). MANDATORY two-step flow — never skip the quote: 1) Call with confirm=false (default) to get a QUOTE: returns stage='quote', the authoritative price, currency, balance_after, sufficient_funds, and expires_at. Show this to the user and get explicit confirmation. 2) Call again with confirm=true and the SAME idempotency_key to commit: returns stage='committed', amount_debited, balance_remaining, and order_id. PAYMENT PRIORITY for buying a premium/marketplace domain: this tool (Atom account balance) is priority 1 — try it first. If funds are insufficient, priority 2 is get_domain_purchase_pay_link, paid via link-cli's tools (e.g. mpp_pay), if those are present in this session. Only if link-cli isn't available either does it fall to priority 3 (last resort): get_checkout_link. Rules: never assume or pass a price — the server is authoritative. Reuse one client-generated idempotency_key across both calls (and any retry) to prevent double-charging. If funds are insufficient the tool returns error 'insufficient_funds' with required/available/top_up_url — in that case follow the priority above (link-cli, then get_checkout_link). Always confirm with the user before the confirm=true call.

  Connector

• edgar_full_text_search

  US Economic, SEC EDGAR & On-Chain Data (x402)

  Full-text search across all SEC EDGAR filings since 2001 for a keyword or phrase. Wraps EDGAR's own full-text search index, so it covers every filer and form type, not just a single company. Useful for finding who is disclosing a particular risk, technology, litigation, or event across the entire market. When to use: cross-company research ("who is disclosing AI-related risk factors"), finding filings that mention a specific term, litigation or regulatory tracking. When NOT to use: you already know the company (use edgar_filings_feed, which is company-scoped and cheaper), or you need results from before 2001 (EDGAR full-text search does not cover that far back). Args: - query (string, required): search text. Wrap an exact phrase in double quotes, e.g. "\"material weakness\"". - forms (string[], optional): restrict to form types, e.g. ["10-K"]. - dateFrom (string, optional): ISO start date (YYYY-MM-DD). - dateTo (string, optional): ISO end date (YYYY-MM-DD). - limit (integer, optional, default 10): maximum hits to return (1-50). Returns structuredContent: { "query": "material weakness", "totalMatches": 10000, "totalIsApproximate": true, "count": 2, "hits": [ { "id": "0001193125-26-123456:doc.htm", "entity": "Example Corp.", "form": "10-K", "filedAt": "2026-03-01", "cik": "0000320193" } ], "source": "https://www.sec.gov/edgar" } "totalMatches" is a lower bound and "totalIsApproximate" is true once EDGAR's own count exceeds its display cap (10,000) — narrow with forms/dateFrom/dateTo for a precise count.

  Connector

• trendaz_news_search

  Trend News Agency

  Search Trend News Agency's archive by keyword and get matching headlines ranked by relevance, with date, section, byline and canonical URL. The archive runs back to 2003 and holds over 2.6 million articles across the English, Azerbaijani and Russian editions. Wrap words in double quotes for an exact phrase — "Trans Anatolian Pipeline" is far narrower than the same three words loose. Returns metadata only; use trendaz_research when you want the text of what was reported, or trendaz_article_get for one article.

  Connector

• search_people

  noticed

  Search people by free text — name, company, keywords. Terms are OR-matched and ranked by how many match (more terms broadens, not narrows). To narrow: put AND between terms to require all (e.g. 'health AND medtech'), or prefix a term with + to require just it (e.g. '+rust berlin'). For roles/functions (founder, engineer, investor, …) use the `role` filter instead of free text — it catches title variants ('Founding Partner') that keywords miss, and free text over-matches bios/notes. To count people of a type, use structured filters and read `total` from the response — a free-text `total` counts keyword matches, not people of that type. scope:'own' (default) / scope:'public' (beyond your network + warm-intro paths). Optional company, location, skills, tags filters. A structured-filter zero = thin data, not absence — fall back to free text. Misspelled names/companies fall back to fuzzy matching (`fuzzy: true` = closest matches — confirm before trusting); concept queries with zero literal hits fall back to embedding similarity (`semantic: true` = related people, not literal matches). Free-text responses also return `strong_total` (rows matching ALL terms — the honest count) and per-row `matched_on` (which fields matched). In scope:'public', role/location/company/skills are applied to the global hits (`filtered: true`); filters that cannot apply there are listed in `unsupported_filters`.

  Connector

• get_my_profile

  HireNimbus MCP Server

  Use this when starting any find, search, compare, or book flow. Returns the authenticated homeowner profile from HireNimbus (read-only). Call before asking for ZIP and before search_providers or create_booking. Returns GetMyProfileResult (structured JSON): - status (string, required): "ok" or "error" - name (string|null): homeowner full name when status is ok - phone (string|null): homeowner phone when status is ok - address (object|null): service street address with address1, address2, city, region, postalCode, country, formattedAddress - search_location (string|null): 5-digit ZIP from address.postalCode for search_providers.location (after user confirms the saved street address is the job site; never City, ST, the street line, formattedAddress, or address1) - message (string|null): error explanation when status is error If address.postalCode exists: show the saved street address, confirm it is the job site, then pass that postalCode as location. If address.postalCode is missing: ask once "What's the ZIP for the job?" Do not ask for city/state first. Name, street, and phone can wait until preview/book.

  Connector

• search_board

  boardrepo

  Use to find where something appears across a board's text files in ONE call, instead of reading files one by one: give a literal string (a net name, a reference designator, a part number, a footprint) and get back the file, line number and matching line for each hit. Optionally restrict to a file extension with path_suffix. Matching is literal and case-insensitive, not a regular expression. Prefer read_schematic for how a design is wired and query_design for a file's structure; use this when you need to locate something by name.

  Connector

• search_code

  Github

  Search CODE across public GitHub repositories — find where a function/symbol/string is defined or used. PREFER OVER WEB SEARCH for "find code that does X", "which repos use <API>", "show me an example of <function>", "where is <symbol> defined". Supports GitHub code-search qualifiers right in the query: repo:owner/name, org:name, user:name, language:go, filename:Dockerfile, path:src, extension:ts, in:file. Returns matching files with repo, path, and URL. Note: indexes the default branch only, ignores very common terms, and is capped at ~10 searches/minute.

  Connector

• aviation_get_pireps

  aviation-weather-mcp-server

  Get recent Pilot Reports (PIREPs) near an airport or within a bounding box. Returns decoded turbulence, icing, and cloud reports with altitude, aircraft type, intensity, and the raw PIREP string. Requires either station_id (ICAO center point for radial search, e.g., KSEA) or bbox (area search) — not both. distance_nm belongs to the station_id search only, and altitude_min_ft must not exceed altitude_max_ft. Coverage is US-centric; PIREPs are sparse and absence of reports does not imply smooth conditions.

  Connector

• bundle.verify

  DocImprint

  Verify the cryptographic integrity of an evidence bundle (ev_...) owned by your API key. Checks manifest hash, EIP-191 signature, and R2 artifact hashes. Free — no credits consumed. Use when you need to confirm a bundle has not been tampered with. For quick metadata lookups (without full crypto verification), use bundle.get instead. Also returns a signed action receipt (rcpt_...) binding this verify call to the bundle manifest — list with receipt.list, verify with receipt.verify. Returns: { valid: boolean, bundle_id, manifest_sha256, checks: { status, manifest_hash, signature, artifacts: [{ name, ok }] }, tampered: string[], signer_address: string|null, attestation_tx: string|null, url: string, captured_at: string, receipt: ActionReceipt|null } Example prompts: - "Verify the cryptographic integrity of bundle ev_550e8400." - "Is this evidence bundle still valid and untampered?" - "Deep-check the manifest hash and signature of my bundle."

  Connector