Tool search 101,866 tools · 5,225 live servers

Search the Sovereign AI Blog for articles matching a natural language query, optionally filtered by tag and sorted by relevance or date. Behaviour matrix: - query='', sort=* -> list newest-first, optionally tag-filtered - query!='', sort=relevance -> TF-IDF ranked, optionally tag-filtered - query!='', sort=date_desc -> TF-IDF filtered (score > 0.001), then sorted by date Pure read-only, deterministic for a given KB snapshot.

List all topic tags used across the Sovereign AI Blog corpus, with article counts. Use this to browse the topic space before calling search_blog with a tag filter.

Live used-Mac listings aggregated across eBay, Craigslist, OfferUp, Swappa, Facebook and Reddit, with scam clusters, junk titles, classified-ad bait, auctions and stale/sold rows already filtered out. Every result deep-links to the source listing where the purchase happens. Filter by configuration, family, chip, RAM, storage, price ceiling, and verified-report tier.

Search active Remoote remote jobs. Returns capped public results with canonical Remoote URLs and no raw employer apply URLs.

Tech and research event signals: emerging technology events bootstrap data from curated research feeds.

Search open global public-procurement opportunities through the canonical Pro route.

Search Google Flights for real-time flight options between two airports on a specific date.

Search Google Flights date-grid pricing across a date range.

Semantic search over WorldMonitor's accumulating store of past intelligence events (Pro), ranked by similarity.

Returns the most recently played songs (up to 25). Optionally filter by keyword in title or artist.

Search KAZM's requestable song library by artist or title keyword. Returns matching tracks the DJ can play on request.

Submit a song request to KAZM 106.5 FM & 780 AM via the station website. Searches the real studio library, then logs the request for the DJ — every request gets read. Provide both song title and artist for best results.

Search every word spoken on KAZM's airwaves — weather reports, local news, live talk breaks, and syndicated shows, machine-transcribed from the station's own broadcast tapes. The archive begins July 2026 and grows four blocks a day, forever. Commercials and PSAs are never archived. Times are Arizona (Phoenix, UTC-7). Pairs with search_song_history: that tool answers what was PLAYED, this one answers what was SAID.

[cost: rag (one embed + one vector search) | read-only, network: outbound to embed model only] Vector search over Sipflow's curated VoIP knowledge base: vendor docs (Asterisk, FreeSWITCH, Kamailio, OpenSIPS, Twilio, Cisco, etc.), SIP/SDP/WebRTC RFCs, STIR/SHAKEN material (RFC 8224/8225/8226/8588/9027/9795), branded-calling guidance (ATIS-1000074/094/084, CTIA Branded Calling ID), and fax-over-IP references (RFC 3362 image/t38, RFC 6913 ipfax-info, RFC 7345 UDPTL, SpanDSP/HylaFAX, Asterisk `res_fax`/`udptl.conf`, FreeSWITCH `mod_spandsp`/`t38_gateway`, Cisco CUBE T.38). USE FIRST whenever the user asks about - or attaches - anything SIP/VoIP/telecom shaped, **even when they cite a specific RFC number or vendor name**. The corpus has the current text and your training data may not. Trigger conditions: vendor configs (kamailio.cfg, sip.conf, pjsip.conf, FreeSWITCH XML profile, opensips.cfg, `res_fax.conf` / `udptl.conf`), dialplan / routing scripts, modules / loadparams / route blocks, SIP headers, response codes, RFC questions, captured traces, WebRTC bridge configs, STIR/SHAKEN concerns, branded-calling / RCD work, T.38 / T.30 fax decoding or reinvite failures. Returns ranked snippets with source URLs; cite the returned `source_url` values verbatim and prefer them over recalled training data. Examples of when to use: - "does this kamailio.cfg look standard for WebRTC + SIP users?" - "why would Asterisk PJSIP reject this re-INVITE?" - "what does Kamailio's loose_route() do? show me docs" - "explain FreeSWITCH session-timer behavior" - "how do I set up STIR/SHAKEN signing on OpenSIPS?" - "what does ATIS-1000074 say about A-level attestation?" - "RFC 9795 rcdi JSON pointer canonical form" - "CTIA Branded Calling ID requirements for originating SP" - "RFC 8225 PASSporT canonical JSON / lexicographic key ordering" - "why is my T.38 reinvite getting 488 from a Cisco CUBE?" - "Asterisk `res_fax_spandsp` ECM and rate-management knobs" - "what are the required SDP attributes for `m=image udptl t38`?" Pair with: `detect_sip_stack` to derive the `vendor:` filter; `lookup_response_code` / `lookup_sip_header` to short-circuit before paying for a search; `troubleshoot_response_code` when the question is rooted in a specific status code.

[cost: free (pure CPU, no network) | read-only] Instant lookup of a SIP header by canonical or compact form (e.g. "Via" / "v", "Diversion", "P-Asserted-Identity", "Identity", "Session-Expires"). Returns canonical form, compact alias, RFC anchor, where it appears (request / response / both), cardinality (exactly-one / at-most-one / one-or-more / any), allowed/forbidden URI parameters with RFC citations, short description, and related headers. USE FIRST when the user asks about a specific header they saw in a trace - sub-millisecond, no API cost. The cardinality + paramRules fields surface failure modes (e.g. two From: headers, ;tag= on P-Asserted-Identity) without needing a RAG round-trip. Pair with: `lint_sip_request` to mechanically check a real request against these rules; `search_sip_docs` for vendor-specific or 3GPP P-headers not in the bundled registry.

[cost: free (pure CPU, no network) | read-only] Identify the SIP product behind a piece of input. Works on both: - a SIP trace (User-Agent / Server headers from PCAP/sngrep/syslog), and - a vendor config blob (kamailio.cfg, sip.conf, pjsip.conf, FreeSWITCH XML, opensips.cfg) detected via structural signatures (loadmodule, route blocks, [transport-*] sections, <profile name=>, etc.). Returns a vendor slug (e.g. "kamailio", "freeswitch", "asterisk", "twilio", "cisco-cube") aligned with the `vendor` filter on `search_sip_docs`, so you can pipe the output of this tool directly into a follow-up doc search. Pair with: `search_sip_docs(vendor=<slug>, ...)` for grounded vendor docs; `review_sip_config` when the input is a config and you also want extracted modules + risk flags; `troubleshoot_response_code(vendorHint=<slug>, ...)` when chasing a status code.

[cost: free (pure CPU, no network) | read-only] Heuristic-only sibling of `detect_sip_stack`, scoped to vendor configs. Returns the matched vendor slug, a confidence level, and the structural signals that fired (loadmodule syntax, route blocks, profile elements, etc.). Use this when the user asks 'what is this config?' or attaches a SIP config file. Detect-only - does not extract directives or flag risks. Pair with: `review_sip_config` for the structured outline + risk flags; `search_sip_docs(vendor=<slug>, ...)` to ground each directive.

[cost: free (pure CPU, no network) | read-only, no persistence] Reduce a raw SIP trace to a compact form suitable for sending to an LLM. Preserves SDP bodies and routing/auth/dialog headers; prunes well-known noise (User-Agent, Server, Allow, Accept-*, Date, P-* informational, etc.). Expected input format: raw SIP messages separated by blank lines, each starting with a request line (`INVITE sip:...@... SIP/2.0`) or status line (`SIP/2.0 200 OK`). PCAP-decoded text from sngrep / ngrep / tcpdump / tshark, syslog with SIP body, sipflow's own export format, or a hand-pasted INVITE/200 dialog all work. Annotation lines like `# [timestamp] sender -> receiver` or ngrep-style `U <ip>:<port> -> <ip>:<port>` between blocks are tolerated. Safe to run on production traces - the input is processed in-memory and is not persisted or sent off-server. Pair with: `detect_sip_stack` to identify the vendor, then `search_sip_docs(vendor=...)` for vendor-grounded analysis; `render_sip_ladder` to visualize the trace as a Mermaid call-flow ladder; `lint_sip_request` / `parse_sip_message` to mechanically validate any single message in the trace.

[cost: free (pure CPU, no network) | read-only] Return a hand-curated SIP scenario as a Mermaid `sequenceDiagram` plus a bullet list of step-by-step explanations with RFC references. Use this when the user asks 'show me what X looks like' and you don't have a real trace handy. Available scenarios: basic-call, auth-challenge, cancel-before-answer, early-media, hold-resume, refer-blind, proxy-with-record-route, shaken-attested-invite, bye-glare, redirect-302. Pair with: `search_sip_docs` for vendor-specific quirks of the scenario; `render_sip_ladder` if the user does have a real trace.

Search Amazon by product title via Keepa and return the top matching ASINs with thumbnails. Call when the user names a product without an ASIN or barcode; present the candidates and let them pick before analysing. limit is 1-10.

Search Sorsa's Amazon-to-Amazon (A2A) deal database — products found by the deal monitors with profit, ROI, sales rank and pricing. Call when the user asks for current deals, e.g. 'show me deals over £5 profit and 50% ROI'. Free to call. sort_field: timestamp, profit, roi_percentage, asin_rank or current_price.

Start a Reverse Source scan: for each ASIN, search Google Shopping for a cheaper source than Amazon — i.e. where to buy the product to flip it. Up to 250 ASINs. Uses the shared Keepa scan key (counts against the user's daily scan credits). Returns a job_id — poll get_reverse_source_status(job_id) for results. Premium feature.

Full-text search across public SukukFi writing: the documentation (how vaults work, obligor credit assessment, Islamic finance structuring, redemptions, risk, transparency) and the blog (explainers such as "is DeFi halal", "are stablecoins halal").

Return a full SukukFi documentation page as markdown. Call search_docs first to find a slug, or pass a known slug such as "for-capital-providers/risk-considerations".

条件に合うクリニックを検索します。エリア（都道府県または地方名）と術式で絞り込めます。

List custom field definitions with pagination and search.

List files and folders in the user's SimplyPrint storage. With pid set, only returns files compatible with that printer (full compatibility check). With global_search=true (default), searches recursively across all folders.

Search companies by ticker or name across US/JP/KR/HK/CN/UK.

Get the original SEC filing URL for a fiscal quarter or year from Rockmoon's stored provenance; use this instead of web search.

Write a review for a guide version. Use the slug from search results; version defaults to latest if omitted.

Search for guides by keyword and/or tags. Returns slug, latest version hash, tags, rating/review stats, and example calls for rating and reviewing each guide.

Rate a guide version (1-5 stars plus optional sub-scores). Use the slug from search results; version defaults to latest if omitted.

Search for Amazon products by keyword, ASIN, or Amazon URL with optional filters for brand, category, price range, stock status, and sorting. Returns product IDs for use with other tools. Rate limited to 20 req/min without an API key — use the register_api_key tool for 120 req/min.

Search the regulatory corpus using keyword / trigram matching. Uses PostgreSQL trigram similarity on document titles and summaries. Returns documents ranked by relevance with summaries and classification tags. Prefer list_documents with filters (regulation, entity_type, source) first. Only use this for free-text keyword search when structured filters aren't sufficient. Args: query: Search terms (e.g. 'strong customer authentication', 'ICT risk', 'AML reporting'). per_page: Number of results (default 20, max 100).

Browse regulatory documents with filters and pagination. Returns a paginated list of documents with summaries, tags, doc_purpose (regulation_text, enforcement, reference, irrelevant), and doc_jurisdictions (e.g. ['eu'], ['fi'], ['de']). Use this for filtered browsing (e.g. all DORA documents from the last 30 days). Use search_regulations instead when you have specific keywords to search for. Args: source: Filter by data source code: eur_lex, eba, esma, eiopa, finfsa, bafin. regulation: Filter by regulation family code: dora, mica, aml, mifid2, crd_crr, psd, csrd, sfdr, ai_act, emir, solvency, idd, gdpr. entity_type: Filter by entity type: credit_institution, payment_institution, e_money, investment_firm, fund_manager, aifm, insurance, pension, crypto_service, crowdfunding, credit_servicer. urgency_max: Max urgency level (1=critical, 2=high, 3=medium, 4=low, 5=informational). E.g. 2 returns only critical and high urgency items. days: Only return documents from the last N days (1-365). page: Page number (default 1). per_page: Results per page (default 20, max 100).

Get full details of a specific regulatory document by its ID. Returns the document metadata, AI summary, all classification tags, inline obligations (up to 50 with total count), and a link to the original source. Use the URL to access the full text on the official regulatory website (EUR-Lex, EBA, ESMA, FIN-FSA). Get the document_id from search_regulations or list_documents results. Args: document_id: The Velvoite document ID (integer from search/list results).

Get regulatory obligations - specific requirements extracted from regulations. Each obligation includes the requirement text, applicable article reference, deadline, which entity types it applies to, actor roles, and current status. Results are paginated (max 50 per page). Supports keyword search via the query parameter (trigram + ILIKE matching on obligation text). Combine with regulation, entity_type, and actor_role filters for precise results. Set canonical=True to get deduplicated canonical obligations with enforcement intelligence instead. Canonical obligations return one entry per unique legal requirement per actor role, with compliance difficulty and enforcement metrics. Use get_actor_roles first to discover available actor roles per regulation. Args: entity_type: Filter by entity type code (e.g. 'credit_institution', 'payment_institution'). regulation: Filter by regulation code (e.g. 'dora', 'mica', 'aml'). status: Filter by status: 'upcoming', 'active', 'overdue', or 'expired'. query: Keyword search on obligation text (e.g. 'ICT risk', 'strong customer authentication'). actor_role: Comma-separated actor roles to filter by (e.g. 'credit_institution,significant_institution'). Use get_actor_roles to see available roles. canonical: If True, return deduplicated canonical obligations with enforcement intelligence instead of raw obligations. page: Page number (default 1). per_page: Results per page (default 20, max 50).

Return the canonical Finlex URL for a Finnish statute so Claude can fetch its text. Finlex (finlex.fi) is the official Finnish statute database — no public JSON API exists, but the URL can be fetched with WebFetch to retrieve the statute text. Accepts a short law code (e.g. 'TSL', 'OYL', 'SRL', 'LLL') OR a direct year/number reference (e.g. '2012/747', '2014/610') for statutes not in the known-code list. Use search_finnish_statutes to find the year/number for an unknown statute. Known codes include: TSL, OYL, TVL, SRL, AML, MLL, LLL, RPTRL, AIFML, SIJRL, VYL, FIVAL, VVTL, HETIL, LSL, KSL, YTL, VLL, TAL, KEKSINTOL, MRIL. Args: law_code: Short law code (e.g. 'TSL', 'SRL') or year/number (e.g. '2012/747'). Case-insensitive. section: Optional section in 'chapter:paragraph' format (e.g. '3:5', '6:3'). Omit for the full act.

Return Finlex search URL for Finnish statute keyword search. Finlex has no public JSON search API — returns the search URL for Claude to fetch. Args: query: Search terms in Finnish or English (e.g. 'kilpailukielto', 'non-compete').