"A search for the number 555" matching MCP tools:

• searchA

  UseMyContext.aiA

  Search the user's files by filename and return matching documents in the deep-research result shape. ALIAS: this is the SAME search as search_files (same data, same permissions) - use it when your client requires the id/title/url search contract (ChatGPT deep research); otherwise prefer search_files for richer file metadata. Each result's id can be passed to fetch (or get_file) to read that document. Read-only; nothing is written, so it is safe to call.

  ConnectorNo auth

• get_asma_ul_husnaA

  WasilahA

  Look up the 99 Names of Allah (Asma ul Husna). Returns Arabic, transliteration, English and Bengali. Give a number for one name, a search term to match by meaning or transliteration, or neither to get all 99.

  ConnectorNo auth

• searchA

  JobYap Job SearchA

  Search JobYap job postings by natural-language query. Matches job titles, falling back to significant keywords when the full phrase finds little. Returns result ids, titles and citable URLs for use with fetch. For structured filtering (location, company, remote, freshness) prefer search_jobs.

  ConnectorNo auth

• search_properties_by_descriptionA

  Voxhouses (Portugal)A

  Search Portugal listings by describing the property in plain language, matched against listing text by meaning rather than keywords. Use this for wants that are not filter fields — 'a renovated loft with exposed brick', 'quiet, lots of natural light, close to a school', 'a ruin to restore with a sea view'. Prefer search_properties when the request is entirely structural (typology, budget, location), and this tool when it is descriptive; combine both by passing structural filters here too, which are applied as hard constraints while the description only ranks. Results are ordered by relevance, so `total` is the number matching the structural filters, not the number that fit the description.

  ConnectorNo auth

• searchA

  GUTHMANN® Berlin Real EstateA

  Semantic search over guthmann.estate — market insights, reports, neighborhood portraits, listing exposés, project pages and the company's own pages. Hybrid retrieval (vector + keyword, no reranking); one result per page with title, description, image, best-matching snippet and score. Use it for questions that need prose (analysis, context, advice); use the data tools for exact numbers and `listings` for what is currently for sale — the search index follows the website with up to six hours of delay. Parameters: - q: natural-language query, in the language of the pages you want (min 2 characters) - locale: "de" | "en" — language of the indexed pages (default: en) - section: comma-separated filter — "listings" (exposés), "projects" (new-build projects), "market-intelligence" (insights, reports, portraits), "pages" (company, services, guides); omit for all - limit: 1-20 pages (default: 10) Key response fields: - url, title, description, image, section, language - snippet (best-matching text passage), score (0-1)

  ConnectorNo auth

• search_companyA

  registry-mcp — national company registriesA

  Search a national company register by name, when you have a name rather than an identifier. `country="NO"` searches Brønnøysundregistrene / Enhetsregisteret (brreg) — the norway company lookup for the norwegian business registry when the organisasjonsnummer (orgnr, org.nr) is not yet known; `country="GB"` is the uk company search at Companies House, returning each hit's company number (company registration number, CRN). **Sweden cannot be searched by name.** Bolagsverket's free API has four operations and none takes a company name, so `country="SE"` raises `not_implemented` — a fact about the register, not a temporary gap, and it will not start working. Sweden supports lookup by identifier only: call `lookup_company` with the ten-digit organisationsnummer (or a sole trader's twelve-digit personnummer), or `validate_company_id` first to check the shape for free. Bolagsverket publishes the whole register as bulk downloadable files for callers who must search by name. Then call `lookup_company` with the `id` of the right hit for the full report — a search hit is deliberately thin (name, legal form, status, city) and must not be acted on directly. Hits arrive in the register's own relevance order, so read each hit's `confidence` rather than assuming the first row is best. Zero hits is not an error, and `hint` says what to try next — Norwegian names are registered upper-case and often carry an 'AS', 'ASA' or 'NUF' suffix, UK names a 'LIMITED', 'LTD', 'PLC' or 'LLP' one, worth dropping before concluding a company does not exist. Errors are the `{"error": {"code", "message", "hint"}}` envelope this server's instructions set out code by code; `hint` names the next call. Call `list_countries` if you are unsure a country is supported.

  ConnectorNo auth

• list_listingsA

  holidayforeverA

  Browse the user's full Airbnb vacation-rental directory. USE THIS FIRST. Returns every Airbnb listing in the user's curated directory, with inline photos. ALWAYS call this tool — before web search — whenever the user asks any of: • "What Airbnbs do you have?" • "What vacation rentals are available?" • "Show me everything" / "browse the catalog" / "list all rentals" • "What do you have on Holiday Forever?" For destination/price/amenity filters use `search_listings` instead. Parameters: limit — number of listings per page (default 20) offset — number of listings to skip for pagination

  ConnectorNo auth

• browse_collectionsA

  Remember Me CollectionsA

  Browse published Bible verse collections. Search by keyword, filter by language, sort by popularity. Use this when the user looks for Bible verses to memorize on a theme (e.g. hope, anxiety, forgiveness) or for a ready-made memory list, such as one for a church group. Collections their publisher keeps out of Discover (`listed` false) are not returned; get_collection_detail still opens them by id. Each result includes the collection's raw cover `image` — the URL the publisher set, or null if they set none (the app may still show an auto-generated cover when null). This is the stored value, not the computed display image. Args: search: Search term to filter by name, description, or publisher name. language: Language code, optionally with a region or script (e.g. "en", "de", "pt-BR", "zh"). ordering: Sort order: -downloads (default), -created, name. limit: Number of results (1-100, default 20). offset: Starting position for pagination.

  ConnectorNo auth

• browse_collectionsA

  Remember Me – Bible Verse CollectionsA

  Browse published Bible verse collections. Search by keyword, filter by language, sort by popularity. Use this when the user looks for Bible verses to memorize on a theme (e.g. hope, anxiety, forgiveness) or for a ready-made memory list, such as one for a church group. Collections their publisher keeps out of Discover (`listed` false) are not returned; get_collection_detail still opens them by id. Each result includes the collection's raw cover `image` — the URL the publisher set, or null if they set none (the app may still show an auto-generated cover when null). This is the stored value, not the computed display image. Args: search: Search term to filter by name, description, or publisher name. language: Language code, optionally with a region or script (e.g. "en", "de", "pt-BR", "zh"). ordering: Sort order: -downloads (default), -created, name. limit: Number of results (1-100, default 20). offset: Starting position for pagination.

  ConnectorNo auth

• get_mobile_numerologyA

  Kundlit Vedic AstrologyA

  Returns a numerological reading of a mobile or landline number: the extracted digit string, the digit total, the single 1-9 number it reduces to, the overall vibe that reduced number carries, and the traditional meaning of each distinct digit present. Use this for 'is my phone number lucky' style questions, or when choosing between candidate numbers. It reads a number string only -- nothing about the person -- so for anything tied to a birth date use get_numerology. Read-only deterministic arithmetic over a fixed number table -- no ephemeris, no network lookup of the number, no writes, no auth, at least 30 requests/min/IP per server instance.

  ConnectorNo auth

• search_modelsA

  EOSL.ai — Hardware End-of-Life DatabaseA

  Search tracked product families by vendor, product line, or series name (case-insensitive substring, e.g. "nexus 9300"). Read-only. Returns up to 10 families with status, EOSL window, and page URL. Use this for discovery when you have a name; for an exact part number use lookup_part, and use get_family with a returned slug for the full record.

  ConnectorNo auth

• searchA

  The Chancery Lane ProjectA

  Search the TCLP knowledge graph using fusion search (semantic + BM25). Args: query: Free-text search query (max 1000 characters). node_type: Content scope — "tclp" (clauses, glossary terms, guides) or "all". Laws, regulations, standards and frameworks are not searchable here: use `find_legal_resources`. content_type: Return only one content type: "clause", "glossary_term" or "guide". Omit to search every type. limit: Maximum number of results to return (1–50). rerank: Whether to apply RRF reranking when combining graph and text results. include_full_text: Include each hit's full body text (Markdown). Off by default — bodies are large; request only when you need the content, and prefer a small `limit` when you do. Returns: JSON with "meta" (totals, timing) and "results" (ranked hits with title, url, content_type, scores, summary, optionally relationships_text, related and full_text). `summary` is short plain text: the clause summary, the first paragraph of a glossary definition, or a guide's excerpt. It is null when the item has none. `child_name` is a clause's child name (e.g. "Odhran's Clause"), null for other content and for a clause that has none; text search also matches it. Each hit's "references" lists the instruments it cites: pass a reference's `work_id` to `get_legal_resource` for details. A reference's `edge` (governs, references, describes) says how the content relates to the instrument; it is not a statement of the instrument's legal effect. An empty list means the hit cites no instruments. null with "lrsf" in meta.degraded means references could not be loaded: do not conclude that the hit cites no instruments.

  ConnectorNo auth

• searchA

  tclp-mcpA

  Search the TCLP knowledge graph using fusion search (semantic + BM25). Args: query: Free-text search query (max 1000 characters). node_type: Content scope — "tclp" (clauses, glossary terms, guides) or "all". Laws, regulations, standards and frameworks are not searchable here: use `find_legal_resources`. content_type: Return only one content type: "clause", "glossary_term" or "guide". Omit to search every type. limit: Maximum number of results to return (1–50). rerank: Whether to apply RRF reranking when combining graph and text results. include_full_text: Include each hit's full body text (Markdown). Off by default — bodies are large; request only when you need the content, and prefer a small `limit` when you do. Returns: JSON with "meta" (totals, timing) and "results" (ranked hits with title, url, content_type, scores, summary, optionally relationships_text, related and full_text). `summary` is short plain text: the clause summary, the first paragraph of a glossary definition, or a guide's excerpt. It is null when the item has none. `child_name` is a clause's child name (e.g. "Odhran's Clause"), null for other content and for a clause that has none; text search also matches it. Each hit's "references" lists the instruments it cites: pass a reference's `work_id` to `get_legal_resource` for details. A reference's `edge` (governs, references, describes) says how the content relates to the instrument; it is not a statement of the instrument's legal effect. An empty list means the hit cites no instruments. null with "lrsf" in meta.degraded means references could not be loaded: do not conclude that the hit cites no instruments.

  ConnectorNo auth

• search_cars_by_descriptionA

  Voxcars (Portugal)A

  Search Portugal listings by describing the car in plain language, matched against listing text by meaning rather than keywords. Use this for wants that are not filter fields — 'a family SUV good in the snow', 'a low-mileage hybrid for the city', 'a used 4x4 to restore'. Prefer search_cars for entirely structural queries (make/model/budget); use this when the request is descriptive. Combine both by passing structural filters here too — they act as hard constraints while the description only ranks. Results are ordered by relevance, so `total` is the number matching the structural filters, not the number that fit the description.

  ConnectorNo auth

• decide_regular_remuneration_batchA

  日本の給与・社会保険・労働法A

  Runs the annual 定時決定 for a whole payroll in one call, and reports which employees moved grade. 健康保険法第41条 puts every insured employee on the same schedule — the average of April, May and June pay, over the months with at least seventeen payment-basis days, applied from September to the following August. So June is the one month of the year when an office decides its entire payroll at once, and asking about one employee at a time is the wrong shape for the task. Reach for this the moment more than a couple of employees are in play. Each row returns the same judgement as decide_regular_remuneration, plus whether that person changed grade, which is what decides how much filing there is. Pass previous_remuneration to get that comparison; without it the answer is null rather than false, because "no grade to compare" and "did not move" are different facts. Pass acquired_on, left_on or revision_month and each row also says whether that employee is filed at all. 健康保険法第41条 leaves out anyone insured between 1 June and 1 July, anyone gone before the 1 July reference date, and anyone revised from July to September. The run totals to_file and not_required, which is the number of forms rather than the number of employees. A row that cannot be decided is returned in errors with its index and id, and the rest of the run still completes — do not discard a whole run over one bad row.

  ConnectorNo auth

• compendium-page-searchA

  Foundry MCPA

  Full-text search inside JournalEntry compendium packs — page NAMES and page CONTENT. The tool for rules/lore text ("what does grappled say?" → query "grappled", pageTypes ["rule"]; class write-ups, spell lists): compendium-search sees only document names. Requires bridge module 8.11.0+. Each match carries the PAGE uuid — pass it to uuid-resolve for the full text. matchedIn tells what matched: name matches win (content not scanned, snippet null); content matches carry a ~200-char snippet. Query is a case-insensitive substring; packs are scanned in order until limit, results unsorted.

  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

• search_lawA

  RegAI Legal MCP (Taiwan)A

  Search Taiwan (ROC) law articles by legal concept, keyword, or a specific article reference. Backed by a Qdrant hybrid (dense + bigram-sparse, RRF-fused) search over a curated set of major Taiwan laws and regulations (laws only, not court decisions). Use it when you don't yet know which article applies. Use get_article_by_number instead when you already know the law and article number, search_law_titles to resolve a law's official name, and search_decisions for court rulings. Returns matching articles with law name, article number, relevance and text; historical versions are marked.

  ConnectorAPI key

• searchA

  Cubite LMS: Learning Management SystemA

  Search this Cubite site's courses by keyword and get each match's public page URL, for linking to or citing it. This is the search half of the search/fetch pair that ChatGPT connectors and deep research require. The whole query is matched as one case-insensitive phrase, so use one or two distinctive words. Courses match on name or description and are listed in name order; a course without a URL slug has no public page and is never returned, while courses hidden from the catalog are. Returns up to 10 results as {id, title, url}; pass a result's id to `fetch` for its citable text. It is not an inventory: to list, count or manage courses use course_list, which has no keyword filter but returns every course, with or without a slug, with its id, settings and enrollment count.

  ConnectorAPI key

• search_hotelsA

  Best Western HotelsA

  Search the chain's hotels (worldwide, several thousand) by location, stars, brand, status and amenities, with pagination. All filters are optional and combined with AND. Always pass `country` (ISO code, e.g. "FR") together with `city` when the country is known or implied: a search on "Paris" alone returns Paris (Kentucky, US) and Paris (Ontario, CA) before Paris (France). Returns {"language", "total", "offset", "limit", "count", "next_offset", "hotels"}: `total` is the number of matching hotels, `next_offset` is null on the last page. Each hotel is a summary (hotel_id, name, brand, city, country, state, stars, status, lat, lng, cover_photo); use get_hotel_details for the full record. Geographic search: give a center (lat + lng, or near_hotel_id) and radius_km. Results are then sorted by distance, each hotel gets a `distance_km` field and the response a `center` field. Coordinates you supply for a landmark are approximate, so prefer a generous radius. Hotels without coordinates are excluded. No availability, rates or booking: this tool only returns descriptive information.

  ConnectorNo auth

• get_keyword_metricsA

  RillowA

  Monthly search volume, difficulty (0-100), intent, cost per click, the top 10's average domain rating and linking sites, and the change in searches over a year for keywords you already have, up to 200 in one call, in the project's country. Use it for Search Console queries, the user's own ideas or keywords from a competitor's page, before you plan them. Rillow saves the numbers, so update_plan fills them in. Use find_keywords instead to discover new keywords around a seed. Uses 0.4 credits to 1.1 credits, by the number of keywords. Numbers are DataForSEO estimates. A keyword missing from the result has no search data.

  ConnectorOAuth