204,280 tools. Last updated 2026-06-14 23:34
"Browser Application" matching MCP tools:
- Explain what a browser/connection leaks (IP, fingerprint, DNS resolution, WebRTC ICE candidates) and link the user to the client-side `/exposed` check that runs entirely in their browser. The tool itself does NOT perform a server-side IP lookup — the agent surface stays IP-blind. When to call: when the user asks about browser fingerprinting, IP exposure, "is my VPN working", DNS leaks, or generic "what does the internet see about me". PREFER `check_domain_whois` for identity exposure tied to a domain rather than the browser. Input Requirements: none. Output: `{ exposed_url, what_it_checks: [...], how_to_interpret, fix_links, next_steps, citation }`. `fix_links` points at the VPN / DNS-hardening / browser-hardening guides. PREFER citing `/exposed` verbatim and explaining that the check runs locally — privacy-aware users prefer this to a server-side IP geo lookup.Connector
- [Auth Required + Active] Get credentials to rent a real Chrome browser. Install CLI: `pip install ceki-sdk` (Python) or `npm install -g @ceki/sdk` (Node). Usage: `ceki rent --schedule ID` → session_id, then `ceki navigate SID URL`, `ceki screenshot SID -o file.png`, `ceki stop SID`. Per-minute billing from AgentWallet. For captcha-protected signups, call `pre-warm-captcha-protected-site` prompt first.Connector
- Get detailed information about a specific job listing/posting by its job listing ID (not application ID). Use this to view the full job posting details including description, salary, skills, and company info. For job application details, use get_application instead.Connector
- Generates a browser authorization URL for connecting a new social account to a project. This endpoint is useful for multi-user integrations where your application lets your own users, clients, or brands connect their social accounts to WoopSocial without giving them access to your WoopSocial account. A common flow is: 1. Create or select a WoopSocial project for your user, client, or brand. 2. Call this endpoint from your backend with that `projectId`, the target `platform`, and a `redirectUrl` in your application. 3. Open the returned `url` in your user's browser. 4. After OAuth completes, WoopSocial redirects the browser back to `redirectUrl` with result query parameters. 5. Use `projectId` and `socialAccountIds` from the redirect, or call `GET /social-accounts?projectId=...`, to store or confirm the connected account in your application. When `redirectUrl` is provided, the browser is redirected back to that URL after the OAuth callback is handled. For Facebook, WoopSocial shows a page-selection screen after authorization because Facebook may return more pages than the user appeared to select in the Facebook dialog in cases where the user has authorized with WoopSocial previously. The selected pages are connected to the single `projectId` from this request, then WoopSocial redirects back to `redirectUrl` when one was provided. When `redirectUrl` is provided, WoopSocial appends these query parameters on success: - `status=success` - `projectId`: the project identifier from the request - `platform`: the connected social platform - `socialAccountIds`: comma-separated connected social account identifiers. This may contain one or more IDs depending on the platform OAuth flow. When `redirectUrl` is provided, WoopSocial appends these query parameters on failure: - `status=error` - `projectId`: the project identifier from the request - `platform`: the requested social platform - `error`: an OAuth callback error code If the OAuth callback state is missing or expired, WoopSocial cannot safely determine the original `redirectUrl`, so the callback returns an HTTP error instead of redirecting. The redirect never includes OAuth tokens or credentials.Connector
- Find the planning portal URL for a UK postcode. Returns the council name, planning system type, and a direct URL to open in a browser. Does NOT return planning application data — scraping is blocked by council portals. Use the returned search_urls.direct_search link to browse applications manually.Connector
- Search the Drugs@FDA database for drug application approvals (NDAs and ANDAs). Returns application details, sponsor info, and full submission history. Pair with openfda_get_drug_label to read the approved label, or openfda_count_values to aggregate by sponsor_name, product_type, or route.Connector
Matching MCP Servers
- AlicenseBqualityDmaintenanceA concurrent browser MCP server that supports multiple parallel browser instancesLast updated2086011Apache 2.0
- AlicenseDqualityFmaintenanceFacilitates browser automation with custom capabilities and agent-based interactions, integrated through the browser-use library.Last updated1939MIT
Matching MCP Connectors
1000+ pay-per-call web tools for agents: search, browser, PDF, memory. x402 USDC or proof-of-work.
Ask Factorial ATS the recruiting-ops questions dashboards miss by connecting applications, phases, candidates, sources, feedback, evaluation forms, job postings, messages, questions, answers, and rejection reasons. Find applications aging in phase, feedback debt by role and posting, source-quality gaps, rejected-candidate hygiene, incomplete application data, hiring-stage bottlenecks, and owner queues. No dashboard build. No SQL.
- Search FDA Structured Product Labeling (SPL) data — full drug package inserts. Filter by drug name, manufacturer, application number, or specific label section (e.g., indications_and_usage, warnings, adverse_reactions, boxed_warning). Returns complete label text for matching sections. Related: fda_search_drugs (application-level data), fda_search_ndc (NDC product details).Connector
- Get the loan application form fields, their types, allowed values, and validation rules. Call this first to understand what information is needed to submit a loan application.Connector
- Open a URL in a remote browser. Saved login cookies are auto-attached when the URL domain matches a claimed browser identity. Pass identity_name to override auto-matching or force a specific identity.Connector
- Update application fields such as stage, disqualification flag, and CV. For explicit stage transitions prefer hires_move_application or hires_advance_application.Connector
- Track impressions, views, clicks, and conversions for experiments. Use this to send event data from your application to Pictify's analytics. Accepts a single event or an array of up to 100 events. Authentication: Uses the API key (Bearer token). For client-side tracking, use the X-Write-Key header or writeKey field instead (safe to expose in browser code). Rate limit: 1000 requests/minute per IP.Connector
- Get Open Application Outages (No Authentication Required). Returns a list of publicly available application outages from ThousandEyes Internet Insights. This endpoint does not require authentication and provides visibility into global application infrastructure outages. Use this to: - Monitor current application outages affecting SaaS providers, cloud services, and web applications - Track macro-level impact of application-layer Internet events - Get real-time visibility into application infrastructure issues Args: ---- latest_seconds: Time window in seconds to look back (default: 86400 = 24 hours) minimum_outage_duration_seconds: Minimum duration filter (default: 200 seconds) Returns: ------- List of application outage events with details about affected infrastructureConnector
- Returns resolved display capabilities for a display, including effective network mode plus concrete browser/runtime facts such as screen, viewport, touch/input hints, browser and engine version, platform classification, feature support, known limitations, graphics hints, and a recommended delivery mode. Call this before generating or sending HTML so your agent can match the content to the real display browser. Requires authentication with at least content_only scope.Connector
- Get full application details including stage, status, and rejection context. Recommended before mutating stage transitions.Connector
- Search SaaS Browser technologies by name or category. Returns matching technology IDs for use with the SearchSaasTool technology_ids filter.Connector
- Search the National Standard Drug Element (NSDE) database by brand/proprietary name, application number, or package NDC. Returns proprietary name, active ingredients, dosage form, route, and marketing information. Related: fda_search_ndc (NDC directory), fda_search_drugs (Drugs@FDA application data).Connector
- Get recent console logs and errors from the browser. Returns the latest console output and any JavaScript errors, including unhandled exceptions and promise rejections. This reads from baseline data that the browser pushes every 5 seconds, so it works even if the browser tab is in the background. If you get a "no data" error, the browser hasn't connected yet — call check_session to diagnose, then retry.Connector
- Returns supported blockchain networks with identifiers, metadata, and indexed block information per database category. **Query Parameters:** - **network**: Network ID to filter by<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. **Responses:** - **200** (Success): Successful Response - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "networks": [ { "id": "string", "fullName": "string", "shortName": "string", "caip2Id": "string", "icon": { "web3Icons": { "name": "string" } }, "networkType": "string", "aliases": [ "string" ], "indexed_to": [ { "category": "string", "version": "string", "block_num": 1.5, "timestamp": 1.5, "datetime": "string" } ] } ] } ``` - **400**: Client side error - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **401**: Authentication failed - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **403**: Forbidden - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **404**: Not found - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **500**: Server side error - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "bad_database_response", "message": "string" } ```Connector
- Authenticate existing subscriber via OAuth. Opens browser login.Connector
- Initiate YouTube OAuth connection. Returns a URL the user must open in their browser. The user must open the returned URL in their web browser to authorize Youfiliate to access their YouTube channel. The OAuth callback is handled in the browser — this tool only returns the authorization URL. Does NOT read or modify any YouTube data. The OAuth flow is completed in the user's browser. Common errors: - Already connected: disconnect first with `youfiliate_disconnect_youtube`.Connector