Skip to main content
Glama
811,344 tools. Updated 2026-11-20 13:23

"A search for unexpected surprises" matching MCP tools:

  • The unified search over business data — combine free text and/or an amount range in one call. Set 'kind' to: all, expenses, income, transactions, clients, suppliers, products, or invoices (use 'all' to search the whole business). Set 'query' for text search (case-insensitive substring match across names, descriptions, notes, references, supplier/client names, categories) and/or 'min'/'max' for an amount range on the kind's primary amount field — both are optional, so omit the amount range for a pure text search (e.g. over clients or suppliers) or omit 'query' for a pure amount search. Optionally filter by date range with 'from' and 'to' in YYYY-MM-DD format. Set 'sort' to 'amount' (default — descending by amount) or 'date' (descending by date; best for clients/suppliers, which have no amount, or when recency matters more than size). Returns ALL matches, paginated — use limit/cursor to page through the full result set; narrow query/range/date if there are more than you need.
    ConnectorOAuth
  • 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
  • Use this when the user asks to inspect listening ports on a paired computer to diagnose local services, unexpected exposure or port conflicts. Reads the OS TCP listener inventory on Windows and macOS, and TCP/UDP listeners on Linux; process details depend on OS permissions. It does not connect to ports, scan remote hosts or change firewall rules.
    ConnectorOAuth
  • Search SaidItHere for real-world software dilemmas, framework gotchas, tool fatigue, and battle-tested community consensus workarounds from Reddit, Hacker News, GitHub, and Stack Overflow. Usage Guidelines: - Primary discovery tool: use FIRST when investigating bugs, library gotchas, unexpected price hikes, or developer complaints by keywords. - Sibling routing: follow up with 'get_problem(slug)' using the discovered dilemma slug to inspect full evidence quotes, sources, and step-by-step workarounds. - Sibling routing: if 0 matching dilemmas are returned, use 'suggest_dilemma' to queue the topic for crawler consensus synthesis. - Do NOT use for generic language syntax lookups or textbook documentation queries. Behavior & Side Effects: - Pure read-only, safe, and idempotent query without side effects. Does not modify user, session, or database state.
    ConnectorNo auth
  • Search hearings, floor sessions, and committee meetings. jurisdiction is required — the Open States events endpoint has no all-states search, so scope every call to a single state; use openstates_list_jurisdictions to pick one. Experimental — most states do not publish event data to Open States. Use after and before to scope to a date range. Set require_bills=true to filter to events with bills on the agenda, which is the most useful filter for tracking legislation through committee. Use include=agenda,participants for full meeting context. Empty results from an unfiltered search often indicate the state lacks event data rather than no events occurring.
    ConnectorNo auth
  • Search US SEC filing nodes for a disclosure claim. The search covers 8-K, 6-K, 10-K, 10-Q, and 20-F. Omit document_type to search all of those forms. Pass document_type to search only the forms you name. Do not use this for DEF 14A. How to search: 1. Always pass concept_groups. Every group is required (AND). Within each group's any_of list, one alternative must match (OR). Use 2-5 groups for separate parts of the claim: topic, action, metric, and a causal link when that link is essential. Example: geography + weaker demand + decline, or AI + productivity + margin. Add synonyms. English stemming covers inflections (decline/declined), not synonyms (sales is not revenue). Do not add a group for a detail the filing may leave implicit. 2. query is optional. Each item is an exact adjacent-token phrase. Put alternate full phrasings in the same list. Query plus concept_groups is hybrid search: an exact phrase ranks first, so a generic phrase such as "margin expansion" can outrank the causal sentence you want. Prefer phrases that state the relationship. Do not pass a broad topic word alone. Do not search with query only. Omit query for concept-only search. 3. start_date and end_date are required. tickers limits issuers. Optional document_type limits the search to one or more of 8-K, 6-K, 10-K, 10-Q, and 20-F. Omit it to search all of those forms. How to continue: 4. Each call returns one page. There is no total count. If HAS_MORE is true, call again with cursor set to NEXT_CURSOR and the same concept_groups, dates, query, tickers, ne_tickers, document_type, and match_scope. A cursor from different inputs is rejected. An empty page with HAS_MORE true is not the end: call again with that cursor. Stop when HAS_MORE is false or when later pages are not relevant. 5. If a page is mostly co-occurrence (the terms appear, but not the claim), start a new search with no cursor. Add a concept group or exact causal phrases. If a page is too sparse, start a new search with no cursor and drop the least essential group. Do not change filters while passing a cursor. 6. ne_tickers excludes issuers you have already reviewed. It does not load the next page. Results are candidates. Call read_node_content with document_id and node_id. node_id may start with sp-. Verify negation, causality, comparisons across periods, and numeric thresholds in the source text. Cite CITATION_MARKDOWN.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to call tools through a security gateway that intercepts requests, enforces deterministic policy and risk checks, blocks or escalates high-risk actions for human approval, and keeps tool credentials and audit logs protected.
    1
    MIT

Matching MCP Connectors

  • Fetch a LIVE Amazon search-results page (SERP) right now — the ranked organic + sponsored listings a shopper would see this minute for a query, with position, ASIN, title, price, rating and badges. Use when the user wants CURRENT ranking/visibility: 'who ranks for "dog bed" on Amazon right now', 'is my ASIN on page 1 for this keyword', 'what's sponsored vs organic for this search'. This is a real-time fetch (takes ~10-40 seconds) — for warehouse keyword search use search_products; for buying advice use shopping_search. Amazon marketplaces only; up to 3 pages per call.
    ConnectorNo auth
  • 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
  • Runs a web search and returns ranked results as {query, results: [{title, url, snippet}]}. Use it for raw links to read yourself; use research.answer for a written answer. Plain phrases work as well as keywords; since and until (YYYY-MM-DD) limit results to a publish-date range, which suits recent news. Needs an x402 payment per call; if the search fails or finds nothing, you are not charged.
    ConnectorNo auth
  • Runs a web search and returns ranked results as {query, results: [{title, url, snippet}]}. Use it for raw links to read yourself; use research.answer for a written answer. Plain phrases work as well as keywords; since and until (YYYY-MM-DD) limit results to a publish-date range, which suits recent news. Needs an x402 payment per call; if the search fails or finds nothing, you are not charged.
    ConnectorNo auth
  • Use this when the user asks how visible their product results are in Google web Search, and which product pages carry them. Search Console performance for one search appearance, defaulting to MERCHANT_LISTINGS: the appearance inventory of the property, a daily clicks / impressions / CTR / position timeline in date order, and the top pages (product URLs) behind it; appearances and pages are sorted by clicks, highest first, and CTR is a 0-100 percentage. Search Console merchant listings counts enriched product results in web Search only, so it does not reconcile to one figure with Merchant Center free listings. Not for the Shopping tab, Images, Lens, YouTube or Maps: use get_organic_shopping_performance. Always served from the live Search Console API: search appearance is never stored in the GSC Wizard warehouse, and it can be filtered on but never grouped with another dimension. `hasAppearance` is false when the property has no rows for the requested appearance, and `emptyBecause` is set whenever it has no impressions, which is normal for non-ecommerce sites. The window may span at most 16 months (Search Console retention); a longer one is rejected with bad_request. Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).
    ConnectorOAuth
  • Retrieve the full record behind a search result: the complete meeting transcript (for meeting:… ids) or the full document text (for doc:… ids). Long records are truncated at a safe length with a marker. WHEN: After the search tool, to read a result in full before answering or citing. WHEN NOT: Ids are opaque — never construct one by hand; only use ids returned by search. EXAMPLES: { "id": "meeting:lehi-ut:1f0c…" } { "id": "doc:lehi-ut:1f0c…:42" } A not-found error means that specific id is stale or unindexed — re-run search for fresh ids; it is not an access restriction.
    ConnectorAPI key
  • Search every upcoming event in one What's Up In city by words, dates, price, topic or place: music, dance, AI/tech, arts, comedy, food, sports, classes, volunteering, street fairs. Use it whenever the question has search words, a date range ("this weekend": from/to), free-only, a town or an area; for a day-by-day overview of the next few days with no search words use list_upcoming, and for an artist, festival or conference in several cities use search_across_cities. Words in `query` match the title, venue, performers, organizer or tags at the start of a word, singular or plural, with common synonyms; by default all must match, with match "any" (or | / commas between them) any one does; a misspelled word is read as the closest word the events use, and `search` in the result says how the query was read. Dates are the city's local dates. Keyword results come earliest first; semantic results are ranked by meaning when the selected city supports semantic search. At most `limit` events are returned; `count` says how many matched in total, so narrow the search rather than paging. Each event has its original listing (`link`) and an `id` for get_event. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
    ConnectorNo auth
  • Find live software by keyword before building from scratch. Public, no sign-in needed. Returns descriptions, USD license prices, tech stacks and listing links. Example: {"search": "invoice", "limit": 5}. Empty search browses recent software. When hasMore is true without nextCursor, narrow the search. Matching is lexical. Errors set isError; retry a rate limit later. Use z2h_compare_marketplace_listings for a shortlist or z2h_show_marketplace for cards. A result does not guarantee suitability or purchase availability.
    ConnectorNo auth
  • Use this when the user wants a word search puzzle (word find, word search maker, printable word search for kids or a class) from a list of words. Accepts 5-40 words for a letter grid: right and down for easy, adding diagonals for medium, all 8 directions including backwards for hard; checks placed words for duplicate occurrences and reports words left out. Shows a playable puzzle and returns a printable PDF with an answer key. Not for crosswords (use generate_crossword) and does not find words in a grid the user already has.
    ConnectorNo auth
  • Ranked search over one public table's rows, the same search its dataset page runs: words, prefixes, typos and spelling correction, served from the table's search package. NOT a catalogue search (search_datasets finds datasets) and not SQL. Example: {"table_id": "0f2f...", "query": "blade runner 1982"}. settled defaults to true (a finished query, which may be planned by a model); send settled: false for a fast keystroke answer planned by the parser alone. page_size is 1-100 (default 20). columns is a subset of the table's search display columns (default all of them). Returns {rows: [{row_id, fields}], plan, planner, retrieval, next_cursor, count, package: {generation_id, package_digest}, table_version_id, timings}. For the next page send the same query with the answer's plan and next_cursor. like: a row_id from an answer finds the rows most like that row (more like this; query, when not empty, is a topic beside it), on a table whose search has meaning vectors. mode (first page only): auto (default) lets the planner choose; meaning ranks by meaning alone; image finds rows whose pictures look like the query (posters showing a red sky over a city); emoji searches by the query's emojis. Most tables search words only. like and the meaning and image modes need meaning vectors, which a table has only when capabilities.search.semantic_columns from get_table_schema is not empty. When it is empty, use the default mode. A table whose search cannot run a mode answers invalid_plan. count: true also asks for the exact number of matching rows; count is null when the table cannot count yet. corrected, when present, is the spelling the search used. A table whose search collapses (a passages table that answers for the entities of another table) returns one result per entity: the answer carries collapsed_by (the key column), and each row is the entity's best match with matched_via (up to 8 of its other matching rows, each {row_id, fields}, in ranked order) and group_size (how many of its rows matched in the ranked window). Paging moves over entities. group: "row" asks for every matching row on its own instead; send the same group with a later page. A table whose search does not collapse accepts group and answers ungrouped rows. To point search at a passages table, in this order: declare collapse in its search spec; wait until its search has been rebuilt and is active for that declaration (a newly declared collapse reaches search only after its search build finishes and activates); run one search on that table and confirm the answer carries collapsed_by; only then set search_table_id. If the answer does not carry collapsed_by, do not set search_table_id. Find the table with search_datasets and list_tables. A table has row search only when get_table_schema returns capabilities.search. Its state says whether search_table answers now. ready means it answers. preparing means a package is being built, and search may still answer from the previous version's package, so try it. unavailable means no package and no build. No state means Cloud has not read it yet, or the table is a recorded stream, whose state Cloud never reads, so try it. A refused search answers search_unavailable with a reason and retry_after_seconds. preparing means the search package is being built or loaded, and service_unavailable means the search service is down. For both, wait retry_after_seconds and retry once. build_failed means the package failed to build, no_package means the table has no search package, and not_public means another workspace's private or link-shared table. For these three, retry_after_seconds is null and retrying will not help, so use query_table or sample_rows instead. Your own workspace's tables are searchable whatever their visibility. To filter, sort or aggregate, use query_table. No key needed on a public table: a keyless caller gets 30 calls a minute and 600 a day per address, and 300 a minute and 10,000 a day across all keyless callers, and settled calls share the dataset page's per-table limit. A refusal past that answers rate_limited with retry_after_seconds. Without a key, private and link-shared tables, and public tables whose publisher turned download off, answer table_not_available. An mr_use_ workspace key (Authorization: Bearer) or an OAuth connection lifts the limit to the key's query limit (60 calls a minute per key or connection, shared with query_table, and 5,000 a day per workspace) and adds the workspace's own tables. A keyed call counts against the workspace's allowance, as query_table does. Cite the package generation and digest.
    ConnectorNo auth
  • Turn a fuzzy or partial name into real, ranked candidate package names, using the registry's own live search index — not a guess at what the package is probably called. For npm this queries registry.npmjs.org's actual search API (the same one npmjs.com uses). For Cargo this queries crates.io's real search endpoint. For PyPI: there is currently no official PyPI search API (XML-RPC search was permanently disabled in 2022 and never replaced) — calling this with ecosystem 'pypi' returns an explicit message saying so rather than a fabricated or scraped result, along with a suggestion to use the exact package name with docs_get_package_info instead. Args: - ecosystem ('npm' | 'pypi' | 'cargo') - query (string): the name or description to resolve, e.g. "react" or "async http client" - max_results (number, 1-10, default 5) Returns JSON with: candidates (array of {name, version, description, score, url}), source_url, fetched_at. Error Handling: - ecosystem 'pypi' always returns an explanatory message, not an error and not fabricated results - Returns "Error: ..." only for actual npm/crates.io request failures
    ConnectorNo auth
  • Run 1 to 5 independent product searches for one selected Russian delivery region, up to 10 results per search. Each search supports the same text, brand, form, price, approved optional goal, sort and page filters as products_search. Results remain grouped in request order. Inspect each status and complete flag; a failed search is not an empty match. Use current catalog RUB prices; never substitute analogs without user confirmation.
    ConnectorNo auth
  • Query Google Ads, GA4 and Search Console with one field vocabulary. Prefer this over the source-specific tools for reporting and for comparing sources, e.g. Google Ads campaigns with their GA4 sessions (join on campaign_id), or GA4 landing pages with their Search Console clicks (join on landing_page). Rows missing in a source show null for its metrics. Ratios (ctr, cpc, cpa, roas, conversion_rate, engagement_rate) are recomputed from totals. Search Console data lags 2-3 days.
    ConnectorAPI key
  • Total Google Search clicks, impressions, CTR and average position for one Search Console site, split by a single dimension: country, device, search appearance (rich results, AMP, etc.) or date (one row per day, oldest first). Up to 250 rows; the same optional filters as gsc_queries apply (page, query, country, device, search type). Read-only; table card plus text summary; data lags 2-3 days. Use it for "which countries/devices do we rank in" or to chart organic traffic over time. It does not list queries or pages: use gsc_queries and gsc_pages for those, and gsc_performance for the overall summary with period comparison.
    ConnectorOAuth
  • Search Westminster written ministerial statements by text, exact UIN, minister, House, answering body and date made. Search returns plain-text previews; retrieve mode=detail with a returned statementId for the complete HTML. A UIN such as HLWS419 is reused across sessions: narrow it with madeFrom/madeTo. A UIN is not a statementId. Search covers all sessions. A CorrectedAnswer link carries a written-question questionId for ukparl_search_questions mode=detail. Follow collection cursors unchanged; use contentCursor for lossless oversized statements.
    ConnectorNo auth