Skip to main content
Glama
114,647 tools. Last updated 2026-04-21 19:57
  • Check your subscription status. Uses the API key from your connection (Authorization header) if api_key is not passed. Optional: pass api_key (the same token you use in the Authorization header). Returns: valid (whether the key is active), requestsThisMonth, monthlyLimit, requestsRemaining. Does not count against your request limit.
    Connector
  • Submit payment proof after sending stablecoins to a FactorGuide wallet address. For x402: provide tx_hash and chain. For MPP: use in-band Authorization header instead — no separate submission needed.
    Connector
  • Get the current escrow payment status for a task. Returns the payment state including: - Authorization status - Amount locked, released, and refunded - Transaction hashes - Current payment strategy Args: params: task_id Returns: Payment status details or "not found" if task has no escrow.
    Connector
  • Add a notification channel for task status events (operator accepts, uploads proof, etc.). Use methodType 'webhook' with a URL or 'email' with an address. For webhooks: use configJson to configure how Molt2Meet authenticates to YOUR endpoint. Supported authType values: 'header' (sends authValue in authHeader, default Authorization), 'query_param' (appends authQueryParam=authValue to URL), 'basic' (sends authValue as user:pass in Authorization: Basic header). Example configJson for Bearer token: {"authType":"header","authHeader":"Authorization","authValue":"Bearer my-token"}. Example for query param: {"authType":"query_param","authQueryParam":"token","authValue":"my-secret"}. Requires: API key from register_agent. Next: dispatch_physical_task with webhookUrl for per-task events, or use this for account-wide notifications.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Access Clerk authentication docs, SDK snippets, and quickstart guides

  • Connect your AI agent to 20,000+ executives (CEO, CFO, COO) of all major companies, 1M+ verified quotes, and full interview transcripts. S&P 500, NASDAQ, AI startups, Federal Reserve officials. 4 MCP tools, pay only for what you use. $5/1,000 results, no minimum, no commitment, cancel anytime. You only pay for returned valid results. You must create an API key at https://mcp.ceointerviews.ai and then authenticate here using header Authorization: Bearer <token> For access to our full data API please access https://ceointerviews.ai

  • Register a new agent email at phobomail.com. No auth needed. After registering, save the api_key and pass it as an HTTP header 'Authorization: Bearer <api_key>' on ALL future MCP requests — not as a tool argument.
    Connector
  • Get a Stripe billing portal URL for managing payment methods and invoices. Returns a URL (not a redirect) that the human can open in a browser. Requires: API key with read scope. Args: flow: Optional. Set to "payment_method_update" to go directly to the payment method update page. Returns: {"url": "https://billing.stripe.com/p/session/..."}
    Connector
  • One-shot convenience tool: creates a transcode job, polls until it reaches a terminal state (completed/failed/cancelled) or the timeout expires, and returns the final job plus a signed download URL if completed. Use this when you want the full transcode in one step without managing polling yourself.
    Connector
  • Issue a Human Authorization Protocol (HAP) credential to authorize an AI agent to act on a human's behalf. Creates a W3C Verifiable Credential 2.0 with scoped permissions, time-bounded validity, and a DataIntegrityProof signature. Requires authentication — the authenticated user becomes the credential owner.
    Connector
  • Poll for device authorization completion. Returns "pending" (keep polling every 5s), "approved" (with api_key and tier), or "expired" (start over with mcpAuth).
    Connector
  • Check the real-time status of an HAP authorization credential. Returns whether the credential is active, expired, revoked, or suspended. Use this for lightweight status checks without submitting the full credential.
    Connector
  • Submit payment proof after sending stablecoins to a FactorGuide wallet address. For x402: provide tx_hash and chain. For MPP: use in-band Authorization header instead — no separate submission needed.
    Connector
  • Analyze source files directly and generate the full 86-artifact AXIS bundle without using GitHub. Returns snapshot_id plus artifact listing; use this for local, generated, or unsaved code. Requires Authorization: Bearer <api_key>. Use analyze_repo for GitHub URLs or improve_my_agent_with_axis for recommendation-first agent hardening.
    Connector
  • Verify that an AI agent is authorized to operate in a specific H3 territorial cell. Checks the GNS-AIP delegation certificate: signature validity, temporal bounds, H3 cell authorization, and facet authorization. Returns a structured result indicating whether the agent may proceed.
    Connector
  • Create a short-lived MCP session token from an API key. Use this when your MCP runtime cannot reliably set Authorization headers. No authentication required.
    Connector
  • Verify a BYO (Bring Your Own) integration is correctly configured for an app. Checks that the proxy secret exists, the target service is reachable, and a lightweight health probe succeeds. Returns structured pass/fail per check. Supported services: stripe, resend, neon, sentry, posthog, clerk, openai, github, supabase.
    Connector
  • Verify the human → agent delegation chain and check whether a specific tool is whitelisted for this agent. Answers the regulatory question: "Did a real human authorize this AI action?" Returns the principal identity, delegation depth, cert validity, and tool authorization.
    Connector
  • Verify an HAP authorization credential. Checks the cryptographic signature, expiration, and real-time revocation status. Use this before honoring an agent's request to act on a human's behalf. Submit the full credential JSON and get back a verification result.
    Connector
  • Approve a device authorization request. Called by the browser approval page after user signs in and confirms. Verifies Firebase ID token from Authorization header to ensure the caller is a real authenticated user. Extracts uid from the verified token. Dev mode: ALLOW_SELF_APPROVE=true skips Firebase verification (for testing).
    Connector
  • Revoke a memory source authorization. Revokes the VC and blocks the source. Optionally deletes all memories deposited by this source.
    Connector
  • Retrieve details of a specific pickup. Required authorization scope: `public.pickup:write` (note: the API requires write scope even for this read operation). Args: easyship_pickup_id: The Easyship pickup ID. Returns: Full pickup details, or an error.
    Connector
  • Delete a shipment that has not yet been shipped. Required authorization scope: `public.shipment:write` Args: easyship_shipment_id: The Easyship shipment ID, e.g. "ESSG10006001". Returns: Confirmation of the deleted shipment, or an error.
    Connector
  • Returns instructions and provides examples for using PropelAuth's frontend APIs to create custom UIs to replace PropelAuth's hosted pages. Examples include login and signup pages, MFA flows, managing organizations, inviting, removing, or updating users in an organization, managing and creating API keys, updating the user's email, verifying MFA, the org member table, api key tables, updating user properties, updating org membership, and more. Before installing any component, make sure to use the 'Installation' guidance first. If instructed to build a login or signup related UI, use the 'LOGIN_AND_SIGNUP_INSTALLATION' guidance first.
    Connector
  • Get the current escrow payment status for a task. Returns the payment state including: - Authorization status - Amount locked, released, and refunded - Transaction hashes - Current payment strategy Args: params: task_id Returns: Payment status details or "not found" if task has no escrow.
    Connector
  • Cancel a pickup. Required authorization scope: `public.pickup:write` Args: easyship_pickup_id: The Easyship pickup ID. Returns: Confirmation of the cancelled pickup, or an error.
    Connector
  • Poll for device authorization approval. Returns AUTHORIZATION_PENDING if user hasn't approved yet. Returns DEVICE_CODE_EXPIRED if the code has timed out. Returns approved status with API key on success.
    Connector
  • List API keys for a user. Accepts either: - Authorization: Bearer <firebase_id_token> (dashboard path) - {apiKey: "..."} or {args: ["dp_..."]} in body (CLI/SDK path) The resolved userId filters the Firestore query server-side.
    Connector
  • Request a device authorization code. Returns device_code, user_code, and verification URL. The agent should display the verification_url to the user.
    Connector
  • Retrieve payment agreement details with AI insights. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key.
    Connector
  • Initiate a payment against an agreement. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key.
    Connector
  • Delete a skill by slug. Requires agent token in Authorization: Bearer <token> header.
    Connector
  • Create or update a skill. Requires agent token in Authorization: Bearer <token> header.
    Connector
  • Create a new shipment and optionally buy a label in one call. Required authorization scope: `public.shipment:write` (and `public.label:write` if buying a label). **Before calling:** collect complete address details from the user — contact names, emails, phones, and company name (required for origin). **Parcel line items (server-enforced):** For every object in `parcels[].items[]`, the **user** must provide at least one of **`category`** (Easyship category slug) or **`hs_code`**. The MCP rejects the request when both (hs_code and category) are missing / empty is missing on any item — **do not pick a default** (e.g. do not assume `fashion`). Ask which product category applies or for the HS code. ## When to buy a label vs just create a shipment - **"Ship this" / "Buy a label" / "Create a shipping label"** → Set `buy_label: true` and `buy_label_synchronous: true` in `shipping_settings`. Always use `format: "url"` in `printing_options` so the response contains a persistent clickable link. - **"Create a shipment, don't buy the label yet"** → Omit `buy_label` or set it to `false`. The shipment is created in draft state; the user can buy the label later. ## Choosing a courier - **No courier specified** → Omit `courier_settings.courier_service_id`. The API auto-selects the best value-for-money courier. **DO NOT call `get_rates` first.** - **User names a specific courier** (e.g. "buy a label with UPS Ground") → Call `get_rates` first to find the matching `courier_id`, then pass it as `courier_settings.courier_service_id` with `allow_fallback: false`. ## Reading the label from the response When `buy_label: true` and `buy_label_synchronous: true`, the response includes a `shipping_documents` array. Find the entry with `"category": "label"` and return its `url` field as a clickable Markdown link to the user. Example response structure: ```json "shipping_documents": [ { "category": "label", "format": "url", "url": "https://...", "page_size": "4x6" }, { "category": "packing_slip", "format": "url", "url": "https://...", "page_size": "4x6" }, { "category": "commercial_invoice", ... } ] ``` Always present the label URL to the user. If a `packing_slip` or `commercial_invoice` URL is also present, include those too. ## Payload schema `shipment_data` is a JSON dict with this structure (fields marked * are required): ```json { "destination_address": { "contact_name": "string *", "contact_email": "string *", "contact_phone": "string * (nullable)", "line_1": "string * (max 35)", "city": "string *", "country_alpha2": "string * (ISO 3166-1)", "state": "string (required for AU,CA,CN,ID,MX,MY,TH,US,VN)", "postal_code": "string (required for most countries, null for HK)", "line_2": "string", "company_name": "string" }, "origin_address": { "company_name": "string * (max 27)", "contact_name": "string * (max 22)", "contact_email": "string *", "contact_phone": "string *", "line_1": "string * (max 35)", "city": "string *", "state": "string (required for AU,CA,CN,ID,MX,MY,TH,US,VN)", "postal_code": "string (required for most countries)", "country_alpha2": "string (ISO 3166-1)" }, "parcels": [ { "total_actual_weight": 1.5, "box": { "length": 30, "width": 20, "height": 15 }, "items": [ { "description": "string * (max 200)", "quantity": 1, "actual_weight": 1.5, "dimensions": { "length": 10, "width": 10, "height": 10 }, "declared_currency": "USD", "declared_customs_value": 50.0, "category": "<slug from user — required unless hs_code set>", "sku": "string", "hs_code": "<from user — required unless category set>", "contains_battery_pi966": false, "contains_battery_pi967": false, "contains_liquids": false, "origin_country_alpha2": "US" } ] } ], "incoterms": "DDU or DDP", "insurance": { "is_insured": false }, "courier_settings": { "courier_service_id": "uuid (omit to auto-select best courier)", "apply_shipping_rules": true, "allow_fallback": false }, "shipping_settings": { "buy_label": true, "buy_label_synchronous": true, "units": { "weight": "kg | g | lb | oz", "dimensions": "cm | in" }, "printing_options": { "format": "url", "label": "4x6 | A4 | A5", "commercial_invoice": "4x6 | A4", "packing_slip": "4x6 | A4 | none" } }, "order_data": { "platform_name": "string", "platform_order_number": "string", "buyer_notes": "string", "seller_notes": "string" }, "set_as_residential": true, "metadata": {} } ``` ## Weight and dimensions — three ways 1. Provide `total_actual_weight` + `box` at parcel level. 2. Provide `actual_weight` + `dimensions` per item — total weight and box auto-calculated. 3. Provide `sku` per item — weight and dimensions taken from product catalog. ## Item categories (valid slugs) mobile_phones, tablets, computers_laptops, cameras, accessory_no_battery, accessory_with_battery, health_beauty, fashion, watches, home_appliances, home_decor, toys, sport_leisure, bags_luggages, audio_video, documents, jewelry, dry_food_supplements, books_collectibles, pet_accessory Args: shipment_data: The full shipment payload as a JSON dict. See schema above. At minimum: `destination_address`, `origin_address` (or `origin_address_id`), and `parcels` with at least one item. Returns: The created shipment object including selected courier, rates, and — if `buy_label` was true — `shipping_documents` array with label/packing slip/invoice URLs.
    Connector
  • Fetch a Federal Reserve Economic Data (FRED) series by ID — e.g. 'DGS10' (10Y yield), 'WALCL' (Fed balance sheet), 'T10Y2Y' (yield curve). Returns cleaned latest observations. Priced at $0.005 USDC on Base (x402). Pass a signed x402 v2 authorization as the '_payment' argument to unlock the paid response. Without it, the tool returns the 402 accept-list for your wallet to sign.
    Connector
  • Update an existing site. All fields are optional — only provided fields are changed. Links replace the entire array (omit to keep existing). Before updating, always call unulu_get_state first to read the current links and their ids — do not guess link ids. Authorization depends on site lifecycle: X-Claim-Token header for ephemeral (pre-claim) sites, X-Edit-Token header for claimed (post-claim) sites. If neither token is available and the site is claimed, use requestEditAccess to obtain an edit_token. If you created the site in this conversation, you already have the claim_token — use it directly. Returns the full updated site state. Keep iteration fast — apply changes immediately without re-confirming minor edits unless ambiguous. Accepts a site ID, a full URL (e.g. https://abc123.unu.lu), or a bare hostname (e.g. abc123.unu.lu).
    Connector
  • Compute an expected-value-maximizing Jito tip for a Solana arbitrage bundle. Inputs: pool_depth (USD), expected_profit (USD), slot_probability [0..1]. Returns tip lamports + EV breakdown. Priced at $0.01 USDC on Base (x402). Pass a signed x402 v2 authorization as the '_payment' argument to unlock the paid response. Without it, the tool returns the 402 accept-list for your wallet to sign.
    Connector
  • Schedule a courier pickup for one or more shipments. **Before calling this tool:** 1. Get the `courier_service_id` from the shipment via `get_shipment` 2. Call `get_pickup_slots` to find available dates/times — present options to user unless they want the closest available 3. All shipments must use the **same courier** and have labels that are pending or generated You must provide either `time_slot_id` (from `get_pickup_slots`) OR both `selected_from_time` and `selected_to_time`. Required authorization scope: `public.pickup:write` Args: courier_service_id: UUID of the courier service (from shipment details). selected_date: Pickup date in YYYY-MM-DD format. easyship_shipment_ids: List of Easyship shipment IDs to include, e.g. ["ESSG10006001", "ESSG10006002"]. All must use the same courier. time_slot_id: UUID of a time slot from `get_pickup_slots`. Provide this OR `selected_from_time`/`selected_to_time`. selected_from_time: Pickup window start time (e.g. "09:00"). Required if `time_slot_id` is not provided. selected_to_time: Pickup window end time (e.g. "17:00"). Required if `time_slot_id` is not provided. Returns: The created pickup object with confirmation details, or an error.
    Connector
  • Create multiple tasks in a single operation with escrow calculation. ⚠️ **WARNING**: This tool BYPASSES the standard payment flow by calling db.create_task() directly instead of using the REST API (POST /api/v1/tasks). This means it skips x402 payment verification and balance checks. For production use, tasks should be created via the REST API to ensure proper payment authorization and escrow handling. Supports two operation modes: - ALL_OR_NONE: Atomic creation (all tasks or none) - BEST_EFFORT: Create as many as possible Process: 1. Validates all tasks in batch 2. Calculates total escrow required 3. Creates tasks (atomic or best-effort) - **BYPASSING PAYMENT FLOW** 4. Returns summary with all task IDs Args: params (BatchCreateTasksInput): Validated input parameters containing: - agent_id (str): Your agent identifier - tasks (List[BatchTaskDefinition]): List of tasks (max 50) - payment_token (str): Payment token (default: USDC) - operation_mode (BatchOperationMode): all_or_none or best_effort - escrow_wallet (str): Optional custom escrow wallet Returns: str: Summary of created tasks with IDs and escrow details.
    Connector
  • Get the EPP/transfer authorization code for a completed domain purchase. Use this when the domain owner wants to transfer their domain to another registrar. The order must be in "complete" status. The auth code is required by the receiving registrar to authorize the transfer. Args: order_id: The order ID of a completed domain purchase. Returns: Dict with order_id, domain, and auth_code.
    Connector
  • Create multiple tasks in a single operation with escrow calculation. ⚠️ **WARNING**: This tool BYPASSES the standard payment flow by calling db.create_task() directly instead of using the REST API (POST /api/v1/tasks). This means it skips x402 payment verification and balance checks. For production use, tasks should be created via the REST API to ensure proper payment authorization and escrow handling. Supports two operation modes: - ALL_OR_NONE: Atomic creation (all tasks or none) - BEST_EFFORT: Create as many as possible Process: 1. Validates all tasks in batch 2. Calculates total escrow required 3. Creates tasks (atomic or best-effort) - **BYPASSING PAYMENT FLOW** 4. Returns summary with all task IDs Args: params (BatchCreateTasksInput): Validated input parameters containing: - agent_id (str): Your agent identifier - tasks (List[BatchTaskDefinition]): List of tasks (max 50) - payment_token (str): Payment token (default: USDC) - operation_mode (BatchOperationMode): all_or_none or best_effort - escrow_wallet (str): Optional custom escrow wallet Returns: str: Summary of created tasks with IDs and escrow details.
    Connector
  • Check submissions for a task you published. Use this to see if a human has submitted evidence for your task. You can then use em_approve_submission to accept or reject. Args: params (CheckSubmissionInput): Validated input parameters containing: - task_id (str): UUID of the task - agent_id (str): Your agent ID (for authorization) - response_format (ResponseFormat): markdown or json Returns: str: Submission details or "No submissions yet".
    Connector
  • Retrieve the full GLEIF LEI record for one legal entity using its 20-character LEI code. Returns legal name, registration status, legal address, headquarters address, managing LOU, and renewal dates. Use this tool when: - You have a LEI (from SearchLEI) and need full entity details - You want to verify the registration status and renewal date - You need the exact legal address and jurisdiction of an entity Source: GLEIF API (api.gleif.org). No API key required.
    Connector
  • Retrieves full details of a specific shipment and document metadata. When a user requests a label, commercial invoice, or packing slip, ALWAYS call this tool first. Extract the 'shipping_documents' URL from the response and provide it as a direct, clickable Markdown link to the user. Do not attempt to describe or visualize the document; simply provide the URL for the user to download. Required authorization scope: `public.shipment:read` > All shipment documents are customisable. You can set: > > - Document format: URL, PDF or PNG > - Label page size: A4, A5 or 4x6 > - Commercial invoice page size: A4 or 4x6 > - Packing slip page size: A4 or 4x6 Args: easyship_shipment_id: The Easyship shipment ID, e.g. "ESSG10006001". label: Label page size: A4, A5, or 4x6. format: Document format: URL, PDF, or PNG. packing_slip: Packing slip page size: none, A4, or 4x6. commercial_invoice: Commercial invoice page size: A4 or 4x6. Returns: Full shipment details including shipping documents metadata.
    Connector