Skip to main content
Glama
207,068 tools. Last updated 2026-06-17 19:02

"LibreOffice Calc" matching MCP tools:

  • Fetch a public URL and inspect security-relevant response headers before you claim that a product or endpoint has a strong browser-facing security baseline. Use this for quick due diligence on public apps and docs sites. It checks for common headers such as HSTS, CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy, and X-Content-Type-Options. It does not replace a real security review, authenticated testing, or vulnerability scanning.
    Connector
  • Search npm or PyPI to estimate how crowded a package category is before you claim that a market is empty, niche, or competitive. Use this when you have a category or search phrase such as 'edge orm' and want live result counts plus representative matches. Do not use it to compare exact known package names or to infer adoption from downloads; it reflects search results, not market share. Registry responses are cached for 5 minutes.
    Connector
  • Run an Agent402 tool by slug (find slugs with search_tools). The 1065 pure-CPU tools execute free on this hosted connector (rate-limited). Wallet-only tools (live search, browser rendering, PDFs, durable memory) return instructions for paid access instead.
    Connector
  • Fetch a public pricing page and extract first-pass pricing signals before you quote plan costs, free tiers, or plan names. Use this when you already have a likely pricing URL and need a quick live scan of visible page text. It returns price-like strings, heuristic plan labels, free or free-trial signals, and cache information. It does not map prices to exact plans, normalize currencies, execute checkout flows, or guarantee that a price applies to a specific region or customer type. JavaScript-rendered, logged-in, or heavily obfuscated pricing details can be missed. Results are cached for 5 minutes.
    Connector
  • Check whether a factual claim is supported by a specific set of public evidence URLs that you already have. For each source, the tool performs a case-insensitive keyword match over the fetched page body, then marks that source as supporting the claim when at least half of the supplied keywords appear. Use this for evidence-backed claim checks on known pages, not for open-ended search, semantic reasoning, or contradiction extraction. The aggregate verdict is driven only by the per-page keyword support ratio. Fetched pages are cached for 5 minutes.
    Connector
  • Perform one live, unauthenticated fetch against a public URL or API endpoint before you recommend it, document it, or build on top of it. Use this when the question is simply whether an endpoint currently responds and what kind of response it returns. It reports HTTP status, content type, elapsed time, likely auth/rate-limit signals, and a short response sample. A successful result only proves basic reachability at fetch time. Do not use it to validate authenticated flows, POST side effects, JavaScript execution, or deeper business logic.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Compare two or more exact package names side by side using live npm or PyPI metadata. Use this when you already know the candidate packages and need evidence for claims such as 'tool A is newer', 'tool B is still maintained', or 'these packages use different licenses'. It returns per-package registry metadata in input order, with field availability varying by registry. Missing or unpublished packages return found=false. Do not use it to discover unknown alternatives, estimate market size, or compare packages across different registries. Registry responses are cached for 5 minutes.
    Connector
  • Place an outbound phone call to a US business or person. The A.I. assistant on the call will identify itself as A.I., follow your instructions, and return a structured outcome via get_call_status. USE THIS TOOL WHEN: the user wants to make a phone call, contact a business by phone, ask about hours/pricing/availability, book a reservation, gather info that's not online, follow up on a service request, or do any task that requires talking to a human on the phone. LIMITATIONS: - US phone numbers only (E.164 starting with +1). International is not yet supported. - English language only. - Cannot call emergency services (911, 988, etc.) — these will be rejected. - The A.I. will NOT commit to bookings/payments without user confirmation unless safety.must_confirm_with_user is explicitly set to false. - Default 5-minute call duration cap. Returns immediately with a call_id. Poll get_call_status(call_id) for the result.
    Connector
  • Returns 9 HBM market sub-tables: accelerators, specs, marketShare, spotPrices, leadingIndicators, qualificationFeed, revenueForecast, supplierRevenue, validationChecks. Optional `table` parameter narrows to a single sub-table; omitting returns all 9. USE THIS for: HBM3/3e/4 generation specs, SK Hynix/Samsung/Micron market share, spot vs. contract pricing. DO NOT USE for: per-accelerator HBM cost in a specific chip (use get_accelerator_costs.costBreakdown.hbmCostUsd); HBM cost in a hypothetical chip cost calc (use calculate_chip_cost with hbmStacks/hbmCost). Returns INTERNAL_ERROR if the upstream Supabase HBM tables are unreachable. Data refreshes monthly.
    Connector
  • Compare two to five public pricing pages side by side before you make competitive pricing or packaging claims. Use this when you want a quick, live comparison of visible prices, free-plan signals, and plan-name hints across vendors. The output is heuristic and page-level: it does not map every price to every plan or normalize regional billing differences.
    Connector
  • Poll the status of a call previously placed with place_call. Returns a CallOutcome with one of these statuses (in roughly likely order): queued/placing/ringing/connected — call still in progress, poll again in a few seconds completed — call finished cleanly, structured result available partial — call finished but some questions unanswered voicemail — recipient was voicemail; identified message left no_answer — recipient never picked up busy — recipient line was busy invalid_number — number is not in service rejected_ai — recipient declined to talk to A.I. (do not retry) needs_user_input — recipient needs info only the user can provide online_only — recipient said the task can only be done online timed_out — call exceeded max duration carrier_failure — telephony provider error (safe to retry later) api_error — internal failure (safe to retry) Always carries a free-form `exit_reason` string suitable for showing the user.
    Connector
  • Run a small verification plan made of concrete live checks and summarize whether a hypothesis is supported. Use this when one conclusion depends on multiple simple checks such as endpoint reachability, npm search counts, or whether a page contains an exact substring. This is a coordination tool, not an open-ended research agent: every test must be explicitly defined in advance, and tests run in order with no branching or early exit. The final verdict is mechanical: all tests passing => SUPPORTED, zero passing => REFUTED, otherwise PARTIALLY SUPPORTED. Use verify_claim when you already have evidence URLs, estimate_market for category sizing, and compare_competitors when you already know exact package names.
    Connector
  • Pre-execution safety oracle for agent actions: submit the tool call you are about to run (shell, http, sql, file, code, env) plus your stated intent, and get a machine-enforceable verdict before you execute it. Decodes what the call does, flags the danger toolkit (rm -rf, reverse shell, curl|sh, SSRF to cloud metadata, credential reads, DROP/DELETE-without-WHERE, path traversal, dynamic eval), and binds it to your intent (allowedHosts/allowedPaths/readOnly/noNetwork) - only a fully pinned, clean, intent-matched call is auto-exec-safe. Hybrid: a deterministic, uninjectable detector engine (authoritative) plus an LLM classifier that can only raise the risk. Fails closed. Detection of known-dangerous patterns, not a proof of safety; it never executes the call. [security; up to 8c/call]
    Connector
  • List all available Ground Truth tools and their access tiers. Zero-cost schema discovery. Call this to explore what verification tools are available before making a tool call. No quota consumption, no API key required.
    Connector
  • 住民税の年額・月額を瞬時に計算。所得割・均等割の内訳表示 (Browser-based tool)
    Connector
  • Search Agent402's 1112 pay-per-call web tools (encoding, crypto, text, time, math, validation, unit conversions, network, browser, PDF, search, memory). 1065 pure-CPU tools run free right here; the rest need a USDC wallet. Returns slugs + input schemas for call_tool.
    Connector
  • Create a persistent monitor that tracks a URL, pricing page, package version, endpoint status, vendor claim, or custom keyword pattern over time. Monitors run automatically on their configured schedule (hourly/daily/weekly) via the Cloudflare cron trigger, or on demand with run_monitor_now. Results are stored in the Durable Object SQLite database. Requires a team API key.
    Connector
  • Scan a public security, trust, compliance, or legal page for common enterprise buying signals before you claim a vendor supports a particular compliance posture. It looks for public references to SOC 2, ISO 27001, GDPR, HIPAA, DPA terms, subprocessors, SSO, SCIM, encryption, and data residency language. This is a signal scanner, not proof of certification or legal sufficiency.
    Connector