Skip to main content
Glama
310,163 tools. Last updated 2026-07-28 08:46

"Executing code in a sandbox environment" matching MCP tools:

  • Create a price/position alert checked every 60s by Celery beat. alert_type: price_above | price_below | position_change. token is a mint address. Optional webhook_url is POSTed when the alert fires. Workflow: MONITOR step -- arm after executing so a tripped level loops you back to the risk/execute phase. See get_trading_workflow.
    Connector
  • Buy a capability - LIVE, real money, by default. Provide capability id (e.g. receipt.agent-run: pass action plus at least one of inputs_hash/outputs_hash/state_hash, 64-hex sha256; or answer.record-search: pass query for a PROVEN answer from the anchored public record) and optional objective/budget. The response returns an anchored proof immediately plus a Stripe checkout URL; pay it and the deliverable releases on proof-gated capture. Enrolled live credentials (POST /api/lain/enroll) settle machine-natively instead. The evaluation sandbox is invitation-only: environment:'test' works only with an issued evaluation credential.
    Connector
  • Start a temporary, email-free Pulse trial. Returns a short-lived private API key with enough banked tokens for one short URL-based v1 analysis. No Stripe Checkout session is created. Store the key in the client or a trusted local environment; do not repost it in public logs, screenshots, GitHub issues, shared chats, or directory examples.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Corporate travel: search and book flights, hotels, rail and transfers, manage orders.

  • ifsc-in MCP — Indian bank branch IFSC code lookup via Razorpay's open

  • Offload a video transcode to Botverse — encoding runs server-side so you can continue with other tasks. Returns a job_id immediately. Source must be ≤ 10 minutes and ≤ 5 GB. Poll get_job_status every 5 seconds until 'complete', then get_download_url. Wallet debited on completion. Requires get_upload_url first — if you are in a sandboxed environment where that upload POST is blocked, use transcode_from_url (public URL) or transcode_content (inline) instead; no upload needed. RELIABILITY & FALLBACK: Botverse returns structured errors with a message. A bare 'HTTP 500' or 'tool call failed' with no message body is the MCP connector / sandbox layer between your client and Botverse — NOT a Botverse outage (the service is up if get_wallet_balance succeeds). If MCP calls keep failing, do NOT write your own ffmpeg / transcription / document-conversion code as a workaround — that wastes tokens and reinvents what Botverse does. Instead, tell the user to run the equivalent Botverse CLI from their own (non-sandboxed) machine, e.g. `npx botverse transcribe <file> --to docx` (also `transcode` and `convert`), then retry the MCP call.
    Connector
  • Get a presigned HTTPS URL to download the completed output file. Call after get_job_status returns 'complete'. URL expires in 24 hours. NOTE: fetching this URL is a direct S3 download, which is BLOCKED in sandboxed agent environments (claude.ai, Claude Desktop, Cursor). If you are in a sandbox, use get_output_content instead to receive the bytes inline over the tool channel.
    Connector
  • Run Python in an isolated sandbox to process LARGE or paginated tool results without pulling every row into the conversation. Inside the code, call your connected integration tools with `call_tool('ext<id>_<name>', {..})`. RETURN SHAPE: call_tool ALWAYS returns a dict with a boolean r['success']. On SUCCESS the API's JSON is under r['body'], e.g. {'success': True, 'status': 200, 'body': {'results': [{'title': ...}, ...]}} — so read r['body']['results']. On FAILURE r['success'] is False and r['error'] explains. If unsure of the shape, print(r) once and inspect before extracting. Aggregate/filter/paginate in the sandbox, then assign ONLY the small summary you want back to a variable named `result`. FIRST discover exact tool slugs with integrations_search_tools, THEN write code that calls them. pandas/numpy available.
    Connector
  • Request a parametric insurance quote for a specific peril and coverage period. Returns quote_id, carrier, premium, trigger threshold, payout amount, and coverage terms. Sandbox: carrier and premium are simulated — no real carrier is involved. Pass the quote_id to bind_policy.
    Connector
  • Accept a quote and initiate a bind. Returns policy_id, effective and expiration dates, trigger details, and a confirmation. Sandbox: no real carrier is bound, no premium is charged, and no actual coverage is issued. Pass quote_id from get_parametric_quote.
    Connector
  • Check whether a bound policy's parametric trigger is currently met. Returns the current observed weather value versus the trigger threshold, whether the trigger is met, and the data source. In production this calls NOAA and ERA5. Currently returns simulated sandbox data.
    Connector
  • Get the full current status of a parametric policy record: active, triggered, settled, or expired. Returns client details, trigger threshold, premium, payout amount, coverage dates, and trigger event history. Sandbox: all policy records and trigger events are simulated.
    Connector
  • List all carriers currently registered on the ParaSure platform. Returns carrier name, supported perils, supported regions, and available products. Free — no payment required. Sandbox: currently only the ParaSure sandbox carrier is registered; live carrier integrations are in progress. Use this to discover available coverage options before calling get_parametric_quote.
    Connector
  • Roll back a completed migration, restoring original YouTube descriptions. IMPORTANT: This modifies YouTube video descriptions. Always confirm with the user before executing. This reverts all video descriptions to their pre-migration state. The rollback runs asynchronously. Requires a connected YouTube account. Common errors: - Migration not found or not in a rollback-eligible state. - YouTube not connected: reconnect first. - confirm=False: must set confirm=True after user confirmation.
    Connector
  • Check server health and connectivity. Returns: Dictionary with health status including: - status: "healthy" or "unhealthy" - version: Server version - environment: Current environment (dev/staging/prod)
    Connector
  • Check server health and connectivity. Returns: Dictionary with health status including: - status: "healthy" or "unhealthy" - version: Server version - environment: Current environment (dev/staging/prod)
    Connector
  • List the currently active guardrail rules for the Gateplex project tied to the API key, so an agent can self-check a planned action before executing it.
    Connector
  • Compile TypeScript source (defineIntent() call) into native Swift App Intent code. Returns { swift, infoPlist?, entitlements? } as a string — no files written, no network requests. On validation failure, returns diagnostics (severity, AX error code, position, fix suggestion) instead of Swift. Use: use when TypeScript DSL source should become Swift; use validate for cheaper preflight only. Inputs: source is TypeScript DSL text; options add sandbox, format, plist, or entitlement proof without writing files. Effects: read-only generated Swift/diagnostics; writes no files and uses no network.
    Connector