Skip to main content
Glama
162,764 tools. Last updated 2026-05-30 11:46

"Enhancing and redesigning application user interface" matching MCP tools:

  • 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
  • Fetch full details for a single opportunity by ID. Use this after search_opportunities when: - The user wants to know more about a specific match - You need the full eligibility text to confirm a strong-match claim - The user wants to draft an application — you need the requirements The response includes all fields including the full body text and eligibility criteria. Present the eligibility as a checklist when relevant.
    Connector
  • Returns a chronological fill feed, filterable by `coin`, `dex`, and/or `user`. Each row is a single fill carrying price, size, side (`BID` or `ASK`), directional intent (`OPEN_LONG`, `CLOSE_SHORT`, `LIQUIDATED_CROSS_LONG`, `AUTO_DELEVERAGING`, and others), closed PnL, fees (negative values represent maker rebates), and order-level metadata (`order_id`, `client_order_id`, `twap_id`, `crossed`). For balance-changing events on a user (deposits, withdrawals, funding payments, vault flows), use `/v1/hyperliquid/users/activity`. At least one of `coin`, `dex`, or `user` is required. Filters compose additively — pass any combination to narrow further; a mismatched pair (e.g. `coin=cash:TSLA&dex=xyz`) returns empty. Defaults to the last 24 hours when no time range is specified — provide `start_time` and `end_time` to query older data. **Query Parameters:** - **coin**: Hyperliquid coin identifier. Core perps have no prefix (`BTC`, `HYPE`); spot pairs use `@N` (`@107`); builder DEXs prefix the symbol with the DEX name (`xyz:SILVER`).<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **dex**: DEX identifier. `perps` for core perps, `spot` for `@N` spot pairs, or a builder DEX name (`xyz`, `cash`, …). Call `/v1/hyperliquid/dexes` for the live set.<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **user**: Filter by address<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **start_time**: UNIX timestamp in seconds or date string (e.g. "2025-01-01T00:00:00Z", "2025-01-01", ...). - **end_time**: UNIX timestamp in seconds or date string (e.g. "2025-01-01T00:00:00Z", "2025-01-01", ...). - **limit**: Number of items* returned in a single request.<br>*Plan restricted. - **page**: Page number to fetch.<br>Empty `data` array signifies end of results. **Responses:** - **200** (Success): Successful Response - Content-Type: `application/json` - **Response Properties:** - **request_time**: ISO 8601 datetime string - **Example:** ```json { "data": [ { "block_num": 1, "timestamp": "string", "transaction_hash": "string", "direction": "string", "transaction_id": 1, "closed_pnl": 1.5, "fee": 1.5, "notional": 1.5, "dex": "string", "crossed": true, "price": 1.5, "size": 1.5, "market_name": "string", "start_position": "string", "fee_token": "string", "twap_id": 1, "user": "string", "client_order_id": "string", "order_id": 1, "coin": "string", "side": "string" } ], "statistics": { "elapsed": 1.5, "rows_read": 1.5, "bytes_read": 1.5 }, "pagination": { "previous_page": 1, "current_page": 1 }, "request_time": "string", "duration_ms": 1.5, "results": 1.5 } ``` - **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
  • Returns the list of perpetuals DEXs and spot, each with 24h activity stats (volume, trade count, unique users, asset count). Hyperliquid hosts a core perpetuals venue (`dex=perps`) alongside builder-deployed perpetuals DEXs that each list their own asset universe — `xyz` (commodities and macro indices), `cash` (tokenized equities), `km`, and others. Use this endpoint to discover valid `dex` filter values for venue-scoped queries on `/markets`, `/markets/activity`, `/markets/liquidations`, `/users`, and `/users/positions`. For platform-wide totals across all DEXs over arbitrary intervals, use `/v1/hyperliquid/platform`. **Public — no auth required.** **Responses:** - **200** (Success): Successful Response - Content-Type: `application/json` - **Response Properties:** - **request_time**: ISO 8601 datetime string - **Example:** ```json { "data": [ { "dex": "perps", "assets": 1, "volume_24h": 1.5, "trades_24h": 1, "unique_users_24h": 1 } ], "statistics": { "elapsed": 1.5, "rows_read": 1.5, "bytes_read": 1.5 }, "pagination": { "previous_page": 1, "current_page": 1 }, "request_time": "string", "duration_ms": 1.5, "results": 1.5 } ``` - **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
  • Returns trading aggregates per user: fill count, volume broken down by side, total fees (negative values represent net maker rebates), realized PnL, net funding paid or received, liquidation-fill count, distinct coins traded, and first/last trade timestamps. Omit `user` for leaderboard mode — returns a paginated list sorted by `sort_by`. Provide `user` for profile mode — returns a single row. Filters `coin` and `dex` compose additively — pass either or both to narrow the scope (`coin=BTC` for one market, `dex=xyz` for one venue, both together for redundancy). A mismatched combination (e.g. `coin=cash:TSLA&dex=xyz`) returns an empty result. Aggregation windows are fixed via the `interval` parameter — `1h`, `1d`, `1w`, `30d`, or omit for all-time. Data is refreshed hourly, so `1h` lags up to 1h. Vaults trade as normal accounts, so passing a vault address as `user` returns its trading performance — pair with `/v1/hyperliquid/vaults` for depositor-side stats. **Query Parameters:** - **user**: Filter by address<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **interval**: Lookback window for user statistics (1 hour, 1 day, 1 week, 30 days). Omit for all-time. - **sort_by**: No description. - **coin**: Hyperliquid coin identifier. Core perps have no prefix (`BTC`, `HYPE`); spot pairs use `@N` (`@107`); builder DEXs prefix the symbol with the DEX name (`xyz:SILVER`).<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **dex**: DEX identifier. `perps` for core perps, `spot` for `@N` spot pairs, or a builder DEX name (`xyz`, `cash`, …). Call `/v1/hyperliquid/dexes` for the live set.<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **limit**: Number of items* returned in a single request.<br>*Plan restricted. - **page**: Page number to fetch.<br>Empty `data` array signifies end of results. **Responses:** - **200** (Success): Successful Response - Content-Type: `application/json` - **Response Properties:** - **request_time**: ISO 8601 datetime string - **Example:** ```json { "data": [ { "user": "string", "coin": "unknown_type", "dex": "unknown_type", "total_funding": 1.5, "volume_sold": 1.5, "transactions": 1, "realized_pnl": 1.5, "volume_bought": 1.5, "liquidation_fills": 1, "last_trade": "string", "interval": "unknown_type", "buys": 1, "total_volume": 1.5, "sells": 1, "first_trade": "string", "total_fees": 1.5, "coins_traded": 1 } ], "statistics": { "elapsed": 1.5, "rows_read": 1.5, "bytes_read": 1.5 }, "pagination": { "previous_page": 1, "current_page": 1 }, "request_time": "string", "duration_ms": 1.5, "results": 1.5 } ``` - **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
  • Returns trading statistics per user: volume, PNL (realized, unrealized, total), trade counts, and activity window. When no user address is provided, returns a paginated leaderboard for discovery. Supports lookback windows via `interval`: `1h`, `1d`, `1w`, `30d`. Omit for all-time. Data refreshes hourly. **Query Parameters:** - **user**: undefined<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **interval**: Lookback window for user statistics (1 hour, 1 day, 1 week, 30 days). Omit for all-time. - **sort_by**: No description. - **limit**: Number of items* returned in a single request.<br>*Plan restricted. - **page**: Page number to fetch.<br>Empty `data` array signifies end of results. **Responses:** - **200** (Success): Successful Response - Content-Type: `application/json` - **Response Properties:** - **request_time**: ISO 8601 datetime string - **Example:** ```json { "data": [ { "user": "string", "buys": 1.5, "sells": 1.5, "volume_sold": 1.5, "transactions": 1.5, "realized_pnl": 1.5, "volume_bought": 1.5, "unrealized_pnl": 1.5, "last_trade": "string", "total_pnl": 1.5, "total_volume": 1.5, "first_trade": "string" } ], "statistics": { "elapsed": 1.5, "rows_read": 1.5, "bytes_read": 1.5 }, "pagination": { "previous_page": 1, "current_page": 1 }, "request_time": "string", "duration_ms": 1.5, "results": 1.5 } ``` - **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

Matching MCP Servers

  • A
    license
    B
    quality
    C
    maintenance
    Simple MCP Server to enable a human-in-the-loop workflow in tools like Cline and Cursor. This is especially useful for developing desktop applications that require complex user interactions to test.
    Last updated
    1
    53
    MIT
  • A
    license
    -
    quality
    C
    maintenance
    This server automatically validates consistency between AI-generated frontend and backend code by enforcing OpenAPI 3.0 specifications. It injects smart constraints into AI prompts to ensure that generated data structures and API calls remain synchronized across the entire stack.
    Last updated
    3
    4
    MIT

Matching MCP Connectors

  • Returns a chronological feed of balance-changing events for a user — bridge deposits/withdrawals, on-chain account deposits/withdrawals, vault deposits/withdrawals, liquidations, and funding payments. Each row carries an `event_type` discriminator and a `notes` field with type-specific extras (e.g. funding rate and position size for funding events). For trade fills, use `/v1/hyperliquid/markets/activity` instead. Supply `event_types` (comma-separated) to filter to a subset. Defaults to the last 30 days when no time range is specified — provide `start_time` and `end_time` to query older data. **Query Parameters:** - **user** (Required): Filter by address - **event_types**: Filter by balance-event type.<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **start_time**: UNIX timestamp in seconds or date string (e.g. "2025-01-01T00:00:00Z", "2025-01-01", ...). - **end_time**: UNIX timestamp in seconds or date string (e.g. "2025-01-01T00:00:00Z", "2025-01-01", ...). - **limit**: Number of items* returned in a single request.<br>*Plan restricted. - **page**: Page number to fetch.<br>Empty `data` array signifies end of results. **Responses:** - **200** (Success): Successful Response - Content-Type: `application/json` - **Response Properties:** - **request_time**: ISO 8601 datetime string - **Example:** ```json { "data": [ { "block_num": 1, "timestamp": "string", "transaction_hash": "string", "amount": 1.5, "counterparty": "string", "notes": "string", "token": "string", "user": "string", "event_type": "bridge_deposit", "event_index": 1 } ], "statistics": { "elapsed": 1.5, "rows_read": 1.5, "bytes_read": 1.5 }, "pagination": { "previous_page": 1, "current_page": 1 }, "request_time": "string", "duration_ms": 1.5, "results": 1.5 } ``` - **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
  • Retrieves the full context of a Quanti launch session. The user has pre-configured an analysis from the Quanti interface and was redirected here with a launch_id. Call this function to get the analysis details to execute (name, prompt or SQL template, project).
    Connector
  • Get the full chronological stage transition history for an application, including the initial assignment. Each entry has from_stage_id/name, to_stage_id/name, moved_at (Unix seconds), moved_by_type (system, user, automation), and moved_by_user_id. Use this for funnel analysis and time-in-stage reports instead of paginating through /candidates/{id}/activities when only stage data is needed.
    Connector
  • Search SecureLend's lender database for residential mortgage offers (purchase or refinance) matching the user's criteria (property value, loan amount, credit score, state, loan type). Returns available rates, terms, estimated monthly payments, and closing cost indicators from participating lenders. Results may change over time and may include offers from SecureLend’s database and authorized third-party integrations when enabled. The user selects a lender and is directed to complete their application on the lender's own platform.
    Connector
  • Submit a content correction, copyright concern, or factual error report. USE WHEN: user (via your interface) flags a wrong answer, broken translation, attribution issue, or DMCA concern. INPUTS: at least one of (questionId UUID, questionText, questionUrl), type (translation|factual|inappropriate|attribution|other), comment (optional, max 2000), reporterEmail (optional). OUTPUT on success: {ok:true, reportId}. On failure the result is marked isError:true with structuredContent {error, message} — error codes: invalid_input, not_found, rate_limit_exceeded (per-IP 5/min), internal_error.
    Connector
  • CONSENT REQUIRED BEFORE CALLING THIS TOOL. Before submitting a loan application, you MUST display the following disclosure to the user verbatim and obtain their explicit agreement (e.g. they say "I agree", "I consent", or "Yes"). Do NOT call this tool until the user has explicitly agreed. DISCLOSURE: "By submitting this application, you: (1) consent to and agree with IncredibleFi's Terms of Service, Privacy Policy, Credit Authorization Agreement, E-Consent, Arbitration Notice, Advertiser Disclosure, and Personal Loan Notice; (2) certify that all information herein is true and complete; (3) provide written instructions under the Fair Credit Reporting Act for Acqscale, Inc. (IncredibleFi.com) and its Marketplace Partners with whom Acqscale, Inc. (IncredibleFi.com) connects you to obtain your consumer credit report from contracted Credit Bureau(s) associated with your pre-qualification for credit inquiry; (4) understand your information will be presented to a network of lenders and/or lending partners who will review and verify your information to determine if you may qualify for a loan, and that lenders and financial service providers may share your personal information including approval and funded status; and (5) provide express consent to recurring communication at the telephone number provided by Acqscale, Inc. (IncredibleFi.com) and its Marketing Partners. Consent is not required to purchase any goods or services." Once the user has explicitly agreed, set tcpaConsent to true and submit the application. This tool always returns a URL for the user: either a direct lender match or curated loan options. May return "additional_information_needed" with extra fields to improve matching.
    Connector
  • Displays a form to collect application prefill data required to continue an enquiry. This tool only renders the form. When the user submits, the form calls submit_prequalification_details, which stores the data and may forward it to lender/partner APIs.
    Connector
  • Open Soundra-style studio wizard inside this conversation. Asks the user 4 short questions (purpose, genre, budget, room size) and builds 3 studio proposals (budget / optimal / premium) with hardware per slot (microphone, audio interface, monitors, headphones, MIDI controller, DAW) and direct purchase links to supersound.pl with UTM tracking. Use when the user asks to recommend studio gear, plan a home studio for X PLN/EUR, swap a device, or compare price tiers. IMPORTANT: ALWAYS pass `locale` (pl/en/de) inferred from the user's chat language so prices are localized (PL=PLN, EN/DE=EUR) and product names + supersound.pl URLs are returned in the right language.
    Connector
  • Search the National Drug Code (NDC) directory by labeler company, brand name, product NDC, or application number. Returns labeler name, brand name, generic name, dosage form, route, active ingredients, DEA schedule, listing type, and packaging details. Drug products are not linked by FEI; use this tool with company name to find drugs at a company. Related: fda_search_drugs (application-level data with submissions), fda_drug_labels (full product labeling), fda_search_nsde (NSDE cross-reference).
    Connector
  • Search application guides by free-text query, matched against section answers and action items. Use this when the user describes an engineering challenge (security review, evaluation harness, observability) and wants matching guides. Prefer guides.get when you already have the guide slug; prefer guides.list when you need the full inventory.
    Connector
  • Estimate the Swiss cantonal real-estate capital gains tax (Grundstückgewinnsteuer) for a property sale. Covers all 26 cantons with holding-period adjustments and Ersatzbeschaffung (replacement-residence) deferral. Educational estimate; commune surcharges and value-enhancing-improvement deductions are not modeled.
    Connector
  • 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
  • Search SecureLend's lender database for commercial mortgage offers (purchase or refinance) matching the user's criteria. Returns available rates, terms, and eligibility indicators from participating commercial lenders. Results may change over time and may include offers from SecureLend’s database and authorized third-party integrations when enabled. The user selects a lender and is directed to complete their application on the lender's own platform.
    Connector