Tool search 164,478 tools · 10,067 live servers

Use this when the user needs to know which official documents a U.S. federal grant opportunity has, which revision is current, and whether the official record is complete. It returns every Full Announcement, revised announcement, supporting document and application package Grants.gov holds, with official download URLs. It does not read the documents, assess eligibility, predict an award, draft, or submit.

Use this after the document manifest, when the user needs the requirements stated inside a U.S. federal grant's official announcement — eligibility, cost share, deadlines, page limits, required submissions and evaluation criteria — each with the document, page and exact source text it came from. It returns CONFIRMED, CONFLICT, UNKNOWN or EXTRACTION_INCOMPLETE per requirement and never fills a gap with an inference. It does not determine legal eligibility, predict an award, draft, or submit.

Use this when the user needs to know what changed between revisions of a U.S. federal grant opportunity — deadlines, cost share, eligibility, funding — with the before and after value for each change and how much it matters. It reads the official revision history and reports what Grants.gov itself declared changed alongside the computed difference. It does not read announcement documents, assess eligibility, predict an award, draft, or submit.

Answers: which of this site's plugin updates are risky right now? Prefer this over the single check whenever there is more than one plugin to look at — a whole site's plugin list costs one call here instead of one call each. Same five verdicts as the single check (known-bad, wait, update-now, too-new, insufficient-data), per item and independent: a plugin that is not indexed reports its own error and the rest still answer. Returns a count of each verdict, so the risky ones can be found without reading every row. Up to 25 plugins per call; more than that is reported, not silently cut. `insufficient-data` means this service does not know, which is not the same as safe. Not a security advisory and not a CVE lookup: it reports what other site owners are saying, which is a different question from whether a release is vulnerable. wordpress.org plugins only — premium plugins have no public forum to read, and themes are out of scope.

Reports what wordpress.org's public support forum says about one plugin release, compared with the releases before it, counted the same way on both sides. It does not answer whether an update is safe: nothing here can see your site, your theme, your premium plugins or your PHP version. `state` is what the evidence supports doing, `signal` is only what was observed: HOLD elevated public signal for this release WAIT above this plugin's own normal, or the window is still open GUARDED_ROLLOUT no elevated public signal — roll out somewhere low-stakes first NOT_ENOUGH_EVIDENCE too little was attributable to judge; a gap here, NOT a finding about the release, and not a reason to reassure anyone The legacy `verdict` field keeps its five strings (known-bad / wait / update-now / too-new / insufficient-data) for clients that already read it. Use it before applying a plugin update, or when someone asks whether a specific version broke anything. Not a security advisory and not a CVE lookup: it reports what other site owners are saying, which is a different question from whether a release is vulnerable. wordpress.org plugins only — premium and paid plugins have no public forum to read, and themes are out of scope. Covers the most-installed plugins; one outside that set returns an error rather than a guess.

Search paid agent capabilities by task description. Returns the price, the input and output schemas, the networks each one settles on, and what has been verified about it. Sort by verified to put the ones with the most evidence behind them first. Use before paying an x402 endpoint you have not used.

Full detail for one capability: schemas, pricing, networks, the seller behind it, and every observation recorded against it.

Turn a goal and a budget into an ordered list of paid endpoints that could reach it, with a cost estimate and what has been verified about each step. Moves no money and buys nothing: it returns the plan for you to run yourself.

Search current U.S. Grants.gov opportunities by default, or set source=eu to search English EU Funding & Tenders topics with SEDIA status 31094502. Inputs are source, query, agency, statuses, limit, closing_within_days, and minimum_award_ceiling. Receive up to 20 normalized JSON records with title, agency, status, open and close dates, award amounts, eligibility, funding fields, and official_url.

Find new or changed U.S. federal grants for a maintained scope. Use scope, as_of, window_days, event_limit, and continuation cursor inputs. Receive JSON with events, changed fields, deadline risks, award-value changes, dataset status, evidence URLs, and next_request.

Read the current Grant Search data coverage and provenance.

Look up FCC radio licences with q as a company or licensee name, call sign, or FRN. Optional service, status, and limit inputs filter the results. Receive up to 20 JSON records with callsign, licensee_name, frn, service, status, grant_date, expired_date, and cancellation_date.

Company enrichment: return the radio-licence footprint for a named company. The data contains FCC radio licences only. Receive matched licensee entities, every matching licence up to the selected limit, licence dates and status, summary counts for all matches, the soonest upcoming expiry, store coverage, and FCC source provenance for every block as JSON.

Find FCC radio licence status changes since a date, filtered by frn, callsign, or service. Receive JSON records with usi, callsign, old_status, new_status, observed_date, and source_file. The since period is at most 31 days.

Web search results (SERP). Keyless web search returning ranked title, URL, and snippet for a query — with locale/region targeting, freshness filters (past day, week, month, year), pagination, a news mode that adds publish date and source, and selectable backend engine (auto rotation, or pin Brave, Yahoo, or Yandex). [$0.05/call]. Params — q: search query; num_results: max results, cap 25; region: locale, e.g. us-en, uk-en, de-de; timelimit: restrict to past day/week/month/year (d|w|m|y); safesearch: string (on|moderate|off); page: result page (pagination); mode: web results or recent news (news adds date+source per item). the news index is narrow, so a long or highly specific news query that matches nothing falls through to web rather than returning empty; those items carry requestedMode=news and servedBy=web (web|news); engine: search backend: auto (recommended - rotates engines and falls back on blocks) or pin one of yahoo, yandex (web mode); news mode supports bing. when set, each result carries an 'engine' field; if the pinned engine returns nothing, auto serves instead and results also carry 'requestedEngine' Example params: {'q': 'best python web scraping library', 'num_results': 10}

Bulk web search: up to 5 search queries in a single call, each returning ranked title, URL, and snippet, with the same locale, freshness, and news filters as the single-query web search. One paid call instead of five for research fan-out. [$0.10/call]. Params — queries: up to 5 search queries separated by '|'; num_results: max results per query, cap 25; region: locale, e.g. us-en, uk-en, de-de; timelimit: restrict to past day/week/month/year (d|w|m|y); safesearch: string (on|moderate|off); mode: string (web|news); engine: search backend: auto (recommended) or yahoo/yandex (web); bing (news) Example params: {'queries': 'python asyncio tutorial|rust tokio tutorial'}

Multi-engine web search (metasearch). One search query fanned out across 2-3 search engines (Brave, Yahoo, Yandex) with results deduplicated by URL and merged by reciprocal-rank fusion: consensus ranking across engines instead of one engine's bias, with per-engine rank attribution on every result. [$0.05/call]. Params — q: search query; engines: comma list of 2-3 engines: yahoo, yandex (web mode). news mode has a single live engine (bing), so multi-engine is web-only; num_results: max results per engine, cap 25; region: locale, e.g. us-en, uk-en, de-de; timelimit: restrict to past day/week/month/year (d|w|m|y); safesearch: string (on|moderate|off); mode: string (web|news) Example params: {'q': 'best vector database 2026', 'engines': 'yahoo,yandex'}

Describe a task in plain language (any language) and get back exactly which tools on this server do it, with ready-to-run example calls — instead of reading the whole catalogue and guessing. Also returns multi-step recipes when a task needs several tools chained (invoices to a ledger, a bank statement reconciled, a messy CSV turned into a deliverable). Deterministic and free: it calls no model, costs nothing, and never runs out of quota. Call this FIRST when you are not sure what this server offers.

List the open-source AI applications hosted and ready to run at AI NetCafé (ainetcafe.com). Each one normally requires local setup (Docker/Python + your own model API key); here they run pre-configured. Use this to find a tool for a task like translating a PDF with formulas intact, generating a PowerPoint file, polishing an academic paper, or running an autonomous research report. Do not call this first when the request already clearly matches compare_models, translate_pdf, deep_research, or make_slides; call that task tool directly. Example — GET https://ainetcafe.com/t/list_apps

Full details of one hosted application: what it does, how to use it, measured benchmark scores, source repository, and the URL a human can open to run it. Example — GET https://ainetcafe.com/t/get_app?slug=<slug-from-list_apps>

Bounded Toronto Police Service Major Crime Indicators rows.

Bounded Toronto Police Service Calls for Service Attended annual aggregates.

Real-time equity quotes, commodity prices, SGE physical-vs-COMEX premiums, physical-divergence regimes and trends, crypt

Returns the current list of trending hip-hop and rap artists ranked by LabelHead's composite momentum score. Each artist is scored across three dimensions: Acceleration (30-day streaming/social velocity), Cultural Gravity (press velocity, playlist adds, sync placements), and Longevity (catalog depth and retention). Use this to identify which artists are building genuine momentum right now.

Returns a detailed explanation of LabelHead's three-dimensional artist scoring methodology. Use this when you need to understand how composite scores are calculated, what each dimension measures, and how to interpret momentum labels.

Look up the current momentum score and signals for a specific artist by name. Returns the full three-dimensional score breakdown and notable signals driving their momentum.

Validate an oh-my-posh configuration against the schema. Supports JSON, YAML, and TOML formats.

Validate a segment snippet against the oh-my-posh schema. Useful for validating individual prompt segments before adding them to a configuration.

Compile source code and return assembly output, stdout, and stderr

List available compilers, optionally filtered by language

List supported languages. Each entry has `defaultCompiler` and `compilerCount`.

Start the Path B agent-walked install for the V1 flow. Returns a playbook the AI walks with the dev to land a kep_* PAT in their editor's MCP config. Current implementation routes through app.keploy.io/settings/api-keys (the existing PAT-issuance surface). The full auto-provision OAuth round-trip (browser OAuth → /auth/temp-code/exchange → /user/mcp/provision → PAT auto-pasted) lands when the enterprise-ui /auth/cli-install page is built; this tool's interface won't change when that lifts, only the underlying steps will get shorter. ABSOLUTE: this tool surfaces a public URL. Do NOT print API keys, PATs, or OAuth tokens to the conversation. The dev pastes the secret into their editor config directly; the agent never sees it.

Return the V1 "user maintains the flow" install guide — covers Path A (clipboard one-liner), Path B (agent-walked OAuth), and the keploy/api-tests/ on-disk layout V1 creates. Safe to call without authentication; call this when the dev asks 'how do I add Keploy to this repo?' or when a devloop_* tool returns missing-API-key.

Check whether the current MCP session has a valid-looking Keploy PAT attached. Returns { authenticated, auth_header_present, hint }. Useful as a first step for an agent to decide whether to call other tools or show setup instructions — differentiates 'no header at all' from 'header present but wrong prefix / unsupported format'.