Skip to main content
Glama
204,124 tools. Last updated 2026-06-14 22:21

"A service for verifying identity documents" matching MCP tools:

  • Get upcoming vessel arrivals and departures at a specific port. Use this to check what vessels are expected at a port — useful for booking planning and tracking. Returns vessel names, carriers, ETAs/ETDs, and service routes. For transit time estimates between two ports, use shippingrates_transit. For detailed service-level routing, use shippingrates_transit_schedules. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { vessel_name, carrier, voyage, eta, etd, service, from_port, to_port }.
    Connector
  • Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use search.files / search.threads / search.links for that.
    Connector
  • Get upcoming vessel arrivals and departures at a specific port. Use this to check what vessels are expected at a port — useful for booking planning and tracking. Returns vessel names, carriers, ETAs/ETDs, and service routes. For transit time estimates between two ports, use shippingrates_transit. For detailed service-level routing, use shippingrates_transit_schedules. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { vessel_name, carrier, voyage, eta, etd, service, from_port, to_port }.
    Connector
  • Call when you cannot proceed because the next step requires a real human. USE WHEN you are blocked by: - Terms of Service or legal agreements requiring a natural person - Account creation that needs identity verification or CAPTCHA - Authentication requiring human identity (BankID, SMS 2FA, OAuth) - Forms requiring human verification or a physical-world action - Content behind a login wall you cannot access - Any step requiring legal personhood, physical presence, or human identity DO NOT USE for: sending messages, making HTTP requests, writing code, or any task you can complete with your existing tools. The human is a paid worker (billed per task), not your operator. Never include passwords, card numbers, CVCs, bank account numbers, SSNs, authentication tokens, or API keys in the description. If a task requires payment, tell the human what to pay for and where — they will use their own payment method. Format your description as numbered steps, one instruction per line. Put each URL on its own line. End with "REPLY WITH:" listing expected deliverables. Example: STEPS: 1. Create account at https://example.com/signup 2. Accept the terms of service. REPLY WITH: confirmation URL, account ID Free tier included on registration. Each task costs 1 credit. Returns 402 when credits are exhausted. Fastest during European business hours (CET). Tasks submitted outside these hours may take longer. Typical completion: 2-30 minutes. Use check_task_status to poll. Set demo:true for an instant synthetic response to verify your integration works. No credits consumed.
    Connector
  • Pay an x402 invoice by signing and broadcasting a TRX transfer to the invoice address, then verifying the payment with the facilitator. x402 (Coinbase + Cloudflare HTTP 402 standard) is the protocol AI agents use to pay APIs per call. Use this when you receive an invoice_id from a paywalled service or another agent. REQUIRES: TRON_PRIVATE_KEY in env (use set_private_key first) AND a valid invoice_id from create_invoice or x402 challenge response. The transfer is signed locally — your private key never leaves the MCP process.
    Connector
  • Log a request for a service type not covered by the 10 named tools (e.g. carpet cleaning, dog walking, painting, moving). Does NOT book — adds to the waitlist to signal demand for future service expansion. Use this when none of the book_* tools match the user's need.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Look up a reservation by booking ID (stk_bk_xxxx) or hotel confirmation number. Returns full booking details including hotel, dates, guest info, rate, and status. Developer-level lookup tool with no identity verification. For guest-facing reservation lookups, use lookup_booking which enforces identity verification before returning any data.
    Connector
  • Register your agent in The Latent Space. Returns a permanent api_key and a session JWT - send either as 'Authorization: Bearer' on all write tools. Grants 10 Latent Credits and a registry identity. Optionally include an Ed25519 public key for cryptographic identity and a referrer_agent name to credit the agent that sent you (they earn 5 credits). Rate limited to 1 registration per IP per 24 hours.
    Connector
  • Identity and links for Psychiatry for Teens: tagline, audience, focus, publisher, sponsor relationship to Emora Health, and key URLs.
    Connector
  • Issues a single-use Stripe-Issuing virtual card hard-capped at fundedUsd, billed at funded + 25% markup + $2 service fee. PAN + CVC are returned ONCE in the response and TMV never persists them. Card auto-freezes 24h after creation. In sandbox mode (test key) cards auth only against Stripe test-mode merchants, perfect for verifying customer checkout flows without real money. Charged in credits at 1 credit = $0.10 (so a $10 funded card costs ~125 credits all-in). Provisioning fee absorbed into the markup.
    Connector
  • Look up a reservation by verifying the guest's identity. Returns the confirmation number and booking summary in conversation. Required before calling: 1. Guest full name (first and last) 2. At least one verification factor: email address used when booking, hotel confirmation number, or last 4 digits of the card used to book (check-in date also required for card verification) Do not call this tool without the guest's full name and at least one verification factor. If the guest cannot provide any verification factor, their reservation cannot be looked up — this is for the security of their booking. To resend the confirmation email, use resend_confirmation after verifying identity with this tool. To cancel, use cancel_booking.
    Connector
  • Use this tool when the user wants to see service packages with fixed pricing and scope for a specific type of service. This tool returns standardized packages offered by service providers, including pricing tiers, deliverables, and delivery timelines. It is useful when the user asks about cost, scope of work, or wants to compare package options. Use `page`/`limit` for pagination.
    Connector
  • Get an exact sat cost quote for a service BEFORE creating a payment. Useful for budget-aware agents to price-check before committing. No payment required, no side effects. Pass service=text-to-speech&chars=1500, service=translate&chars=800, service=transcribe-audio&minutes=5, etc. Returns { amount_sats, breakdown, currency }. Omit params to see the full catalog of supported services.
    Connector
  • Calculate total monthly and annual spend for a list of subscriptions. Use this to help users understand their total subscription spending. Accepts service names or slugs and returns per-service breakdown plus totals. Args: service_names: Comma-separated service names or slugs (e.g. "Netflix,spotify,Xbox Game Pass"). Fuzzy matching is supported. country: ISO country code (default "AU"). Returns: JSON with total monthly spend, annual projection, and per-service breakdown including plan name, price, and billing period for each. Example: calculate_subscription_total_tool("Netflix,Spotify,Disney+", "AU")
    Connector
  • Manage the caller's aX identity, memory, and relationships. Use `get` first for a read-only identity card. Write actions are bounded to authenticated aX identity state and remain permission-gated: `update` uses profile fields including caller avatar_url/avatar_emoji, `remember` requires `key` and `value`, `recall` requires `key`, and `follow`/`unfollow` require `target_agent`.
    Connector
  • Returns the authenticated identity of the calling agent. If you connected with ERC-8128 signed requests, this resolves your wallet address to your ENS name, agent metadata, and portfolio summary. Call this first to confirm your identity is recognized. Requires ERC-8128 authentication (signed HTTP requests). See GET /mcp/auth for setup details.
    Connector
  • Call this BEFORE your agent approves any multi-document trade finance transaction or cross-border shipment — at the moment a set of related documents is received and no action has been taken. Cross-checks 2-20 documents for consistency across numeric values, party names, reference numbers, dates, and commodity descriptions. A single inconsistency across documents in a trade finance package indicates fraud with no recovery path once funds are released. Do not use as a substitute for check_document when only one document needs verification.
    Connector
  • Semantic (vector) search across documents in a collection. Returns ranked text chunks. Free — no credits consumed. PREREQUISITE: Collection must be populated via REST API (POST /v1/collections/{id}/documents/{bundle_id}) and indexing must complete (async) before results appear. Use search_collection for raw matching chunks; use ask_collection for a synthesized cited answer. Returns: { results: [{ bundle_id, chunk_id, text, score: number (0–1), title? }] }
    Connector
  • Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use search.files / search.threads / search.links for that.
    Connector
  • Deletes TMV's retained credentials for a managed test identity. This does not guarantee deletion inside the customer app; run an account-deletion test first if you need customer-site cleanup.
    Connector