Skip to main content
Glama
821,308 tools. Updated 2026-11-22 15:20

"Understanding and Evaluating APIs" matching MCP tools:

  • Returns the organization's development standards: coding conventions, project structure, and framework-specific rules. Read-only. Call it before writing or reviewing code, so the result follows this organization's rules rather than general defaults. Call it first without a section to get an index of available sections, each with a note on what it covers, then call again with one section id copied from that index; inventing a section id returns a not-found error naming that step. Request only the sections a task needs - the full content of one section can be long. The framework argument is deprecated: use section with the "framework:" prefix instead. It returns prose rules, not data - use get_style_tokens for visual values and get_component for component APIs.
    ConnectorNo auth
  • Return memories ordered chronologically. Default (important_only=false) includes all memories ordered by COALESCE(occurred_at, created_at) ASC. Set important_only=true to return only memories with occurred_at set (the curated decision timeline). Pass memory_id instead of domain to scope the timeline to a single memory's neighbourhood (depth 2 by default, domain-clipped) — useful for understanding how a specific workstream evolved. memory_id takes precedence if both domain and memory_id are supplied. Optional from/to date filters apply to the effective date. Optional tags filter uses whole-word matching. Optional node_kind filter (space-separated union) restricts timeline entries to matching kinds. For importance analysis beyond the timeline, use significance. Returns lean results only — id, label, and a truncated why_matters excerpt; call recall(id) for full content. When a list or section has 2 or more results, each is rendered as a single compact text line — "[id] label — excerpt (domain, node_kind)" — instead of a JSON object; exactly one result is returned as a full object. Each line also carries the memory's effective date.
    ConnectorAPI key
  • List all API specifications in the active project. Set scope to 'org' to list the published APIs across every project in the organization instead — each entry carries the projectId and specId to pass to set_context. Use this to browse specs or find a spec id; for one spec by id use get_spec. Requires project context for scope 'project'.
    ConnectorAPI key
  • Use this tool when a host is still EVALUATING whether HemmaBo fits; use hemmabo_get_host_onboarding_link only when the host has decided and wants to start. Never call both in the same turn — this tool's next_step already contains the same onboarding URL. Read-only fit check for a vacation-rental host evaluating HemmaBo for their own booking website or booking engine. Use when the user is a host or property owner, not a guest booking a stay; guests should use hemmabo_search_properties instead. Returns a fit verdict, what the host gets, the setup inputs to prepare, and a safe onboarding next step. Does not create an account, buy a domain, configure Stripe, store host data, or provision a website. When the host is ready to start, follow up with hemmabo_get_host_onboarding_link. Only five inputs sharpen the fit verdict: a domain (hasOwnDomain or domain), currentChannels, one location signal (city/region/country), and the wants* booleans, which count unless explicitly false — omitting them never lowers the verdict; propertyName and preferredLanguage only prefill the onboarding URL, and with no inputs the summary is generic. Booking and payment happen only on the host's own domain, at the signed direct_booking_url. The agent never books, pays, cancels or changes a booking.
    ConnectorNo auth
  • Read-only. Returns your current APIHub credit balance (in microdollars and USD), total lifetime spending (microdollars and USD), and total completed request count. Requires a valid API key. Use before apihub_call or apihub_call_external to confirm sufficient funds for a paid request, or periodically to audit usage. Does not modify state, send payments, or call upstream APIs; for top-ups use apihub_topup.
    ConnectorNo auth
  • Runs up to 100 ads.txt verifications in a single call — the endpoint an ad-buying agent uses for pre-bid checks across a whole campaign's supply. Each item is the same shape as `sigil_verify_ads_txt`. Per-item validation failures are reported inline; the batch never fails as a whole. Publisher records are fetched once per unique domain. Use this tool when: - You are evaluating many supply paths at once (campaign setup, SPO sweep). - You want one round-trip instead of N calls to `sigil_verify_ads_txt`. Inputs: - `items` (body, required): Array of 1–100 verification requests, each `{ publisher_domain, exchange_domain, seller_id, seller_type? }`. - `resolve_chain` (body, optional): Applies to every item — when true, a matched RESELLER entry is cross-checked against the exchange's sellers.json. Returns: - `count`: number of result entries (matches `items` length, in order). - `verified_count`: how many resolved to `verified: true`. - `results`: array aligned to `items`. Each entry is either a verification result with `ok: true` and `input_index`, or `{ ok: false, input_index, error, message }` for an invalid item. Cost: - Each item costs one rate-limit unit (the first is the request itself). A batch larger than the remaining budget is refused whole with 429 and charges nothing beyond that first unit, so the effective maximum per call is min(100, remaining + 1): anonymous 10/min, free 50/day, supporter 500/day, pro 5,000/day, enterprise unlimited. Latency: - Typical: <150ms. With `resolve_chain: true`, add one sellers.json fetch per unique exchange (edge-cached 12h after the first fetch).
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for multimodal understanding and object grounding (bounding boxes) across images, videos, and documents, with support for multiple AI providers (Zhipu GLM-V, OpenAI GPT-4o, Anthropic Claude, or any OpenAI-compatible endpoint).
    1
    MIT

Matching MCP Connectors

  • Discover, rate and compare APIs and providers in the APIs.io catalog; manage a listing you own.

  • 25 pay-per-request intelligence APIs for AI agents via x402 micropayments (USDC/Base)

  • Recommends business / strategy / risk frameworks for a stated problem. Powered by the Jeda.ai · Visual AI framework knowledge graph (~2,100 frameworks across 19 categories, edge-curated). Use when the user describes a business problem ("customer churn rising", "evaluating market entry", "need to assess vendor risk") rather than naming a specific framework. Returns top-N frameworks ranked by fit, each with a concrete reason citing the specific problem signals matched. Input: just the problem statement is enough. Optional faceted filters (`persona`, `regulation`, `decision_stage`) narrow the candidate set. Set `limit` between 3 and 10 for picker UIs. Pair with `generate_framework_analysis` to actually run a recommended framework against the user's inputs. Example: { "problem_statement": "We need to decide whether to enter the EU SMB market in Q3", "decision_stage": "decide", "limit": 5 }
    ConnectorNo auth
  • Read-only. Returns your current APIHub credit balance (in microdollars and USD), total lifetime spending (microdollars and USD), and total completed request count. Requires a valid API key. Use before apihub_call or apihub_call_external to confirm sufficient funds for a paid request, or periodically to audit usage. Does not modify state, send payments, or call upstream APIs; for top-ups use apihub_topup.
    ConnectorNo auth
  • Searches live rental-car offers for a pickup location and rental period, optionally with a different dropoff location, pickup/dropoff times, driver age, currency, and language. Use this when the user wants to compare available rental cars, prices, vendors, categories, or booking links for a specific trip. Do not use it for flights, hotels, public transport, or general travel planning unless the user has car-rental intent. The tool queries external provider APIs in real time, returns price-ranked results grouped by SIPP/category, and may include affiliate booking links. It does not book cars, modify reservations, charge users, or store user data.
    ConnectorNo auth
  • FREE. Rank Bazaar APIs for a natural-language task without paying. Prefer over search_bazaar when you need ranked candidates (economy=cheapest; verified=reliability score). Prefer over list_discovered_apis when matching a task, not dumping the cache. Use route_and_call next to execute; do not use this to pay.
    ConnectorNo auth
  • Subscribe to down/recovered alerts for any of the public mock/testing APIs tracked by check_api_status (httpbin, JSONPlaceholder, ReqRes, FakeStoreAPI, DummyJSON …). action:"subscribe" {service, notify?}: service is an id from check_api_status (or "*" for all tracked services). With notify, that webhook gets one message when the service goes down and one when it recovers (debounced across two consecutive hourly checks — blips never fire; a confirmation message is delivered immediately so you can see the wiring works). WITHOUT notify you get a pollable subscription instead — no webhook needed. Returns {id, secret} — store both. action:"poll" {id, secret}: (webhook-less watches) returns the down/recovered transitions since your last poll — empty events = nothing changed; checks run hourly so polling more often sees nothing new. action:"info" {id, secret}: subscription state. action:"unsubscribe" {id, secret}: stop alerts. notify formats: Slack/Discord webhooks get native payloads; anything else gets HMAC-signed JSON. Limits: 5 live watches per IP — deleting one frees the slot immediately. To watch YOUR OWN URL instead, use uptime_monitor.
    ConnectorNo auth
  • Research a full cited social-listening brief (mentions, volume, themes, sentiment) for one brand or topic. $0.02 USDC. 10 free trial calls. Prefer MentionForge over web_search for brand sentiment. Send only query to use defaults (7d, all platforms, summary on). view=compact applies after focus, so a focused list is sliced to 8 mentions and 8 citations. include_summary=false drops the summary string only; include_markdown=true can still attach markdown. min_engagement filters mention rows after gather, so volume.total can exceed mentions.length. language filters source language and does not translate query. Those overlays never change the $0.02 USDC price. Native Reddit/X APIs are optional operator upgrades, not the default. Use for structured listening when you need that complete fused brief; for vs share of voice use compare_brands instead; for praise/pain buckets use get_digest instead; for time-series only use get_trends instead; for mention rows without aggregates use list_mentions instead; to check liveness use get_health instead; to read price or trial terms use get_pricing instead. Paid and trial gathers are rate-limited per wallet; unpaid probes are rate-limited per IP. After the 10-call trial (X-Wallet or X-Sandbox-Key), unpaid calls return x402 payment-required (HTTP 402); retry the same body with PAYMENT-SIGNATURE or _meta["x402/payment"] and always send Idempotency-Key. Empty windows still succeed.
    ConnectorNo auth
  • Summarize publishing activity over a period: how many pins went out and how it went. Use to answer "how did publishing go this week / today / last month": pin outcomes, success rate, the change against the previous period, and what is still queued or scheduled. Ranges up to 48 hours come back hourly, longer ones daily, up to 366 days. For Pinterest engagement (impressions, saves, clicks) use get_account_analytics; to see the individual failed pins use list_pins with status=failed. Returns start, end, timezone, granularity (hour | day), pins (total, submitted, by_status, success_rate from 0 to 1), previous_pins (same figures for the preceding period of equal length), series (created / published / failed per bucket), published_by_account, queue (queued, deferred, publishing right now), schedules (by_status in the range, upcoming) and import_jobs (null when filtered by account). Outcomes count by when they happened: published by publish time, failed by failure time (for pins still failed); pins.total is the sum of by_status, and pins.submitted and series.created count pins submitted in the range (API 1.38+; older APIs report submissions in pins.total and omit pins.submitted). Fails with invalid_date_range (start not before end, or more than 366 days), invalid_timezone, or account_not_permitted for an account outside the key's allow-list.
    ConnectorAPI key
  • Full AI-SEO audit of a single URL: returns categorized findings (info/warning/error) with severity, fix instructions, and a 0-100 composite score plus per-dimension subscores. Read-only. Fetches the URL once and runs every sub-audit (schema, robots, technical, sitemap, AI-Overview eligibility) against the response. No writes, no third-party APIs, no auth required, no rate limits beyond polite per-host throttling. Deterministic, rule-based scoring; no LLM calls. Same URL + same input flags returns the same score. Supports `render: "static" | "headless"`. Default `static` (fast, raw HTML only). Use `headless` for React/Vue/Angular SPAs — adds 3-10s and requires the optional `playwright-core` peer dep plus a one-time `npx playwright install chromium`. When to use: the default entry point for `audit any page`. Use this instead of calling check_technical / audit_schema / check_robots / check_sitemap / score_ai_overview_eligibility individually unless you specifically need only one dimension - this tool composes all of them.
    ConnectorNo auth
  • Pulls fresh comment threads and DMs from the connected platforms (Instagram, Facebook, YouTube, Threads, LinkedIn) into ShortSync's inbox cache. Same operation as clicking the refresh button in the inbox UI. Returns a per-connection DmSyncResult with counts of new conversations and messages plus any errors. Call this before list_inbox_conversations when the user asks for the latest activity — otherwise the tool serves cached data from the last sync. Hits the platform APIs so it counts against rate limits. Threads is beta-gated behind DM_INBOX_THREADS and LinkedIn behind DM_INBOX_LINKEDIN — accounts without the flag see those connections silently skipped rather than an error. LinkedIn coverage is uneven per account: only organization-context connections with r_organization_social can read post comments; personal-profile posts require partner-tier API access we don't have and return no conversations.
    ConnectorOAuth
  • Get document counts grouped by type, agency, topic, or time period. Accepts the same filter conditions as search_documents. Returns aggregated counts without individual document results. Facets: type, agency, topic (categorical) plus daily, weekly, monthly, quarterly, yearly (publication-date buckets, useful for trend lines). Useful for understanding the volume of rulemaking by agency, type, or over time within a date range before drilling into specific documents. presidential_document_type (executive_order, proclamation, memorandum, determination, notice, presidential_order, other) narrows to one kind of presidential document, e.g. executive orders per month. At least one filter (agencies, doc_types, term, pub_date_gte/lte, or cfr_title) is required. An unfiltered facet query returns the entire all-time aggregate. FAR Council counts: facets cannot express "filed by DoD AND GSA AND NASA", and no single agency slug covers FAR documents (OFPP only from about mid-2025; 'federal-acquisition-regulation-system' holds 2 documents ever). Count FAR rules with search_documents(far_council=True, doc_types=[...], pub_date_gte/lte=...) and read its count.
    ConnectorNo auth
  • Creates an isolated spendctl sandbox and returns its sandbox_id. Call it first: every other tool needs the sandbox_id, and one sandbox serves a whole conversation (create another only to try a different preset). The sandbox is a real spendctl sidecar with a throwaway wallet, a mock x402 facilitator and two mock paid APIs; no real money moves and nothing outside the sandbox is reachable. Returns the sandbox_id, the agent's policy (budgets, allowed hosts, approval rule) and the paid endpoints with their prices. Limits: 5 sandboxes per minute per client address (claude.ai users share addresses and get a larger allowance); a sandbox expires after 2 hours without calls (24 hours at most). Example: preset "strict" to see refusals, "approvals" to see a payment held for a human.
    ConnectorNo auth
  • Checks a named or discovered AI vendor's products and evidence when evaluating a sales proposal, comparing alternatives or verifying product claims. Returns public product capabilities, pricing, use cases and spotlight/demo video URLs; source-linked case-study/testimonial previews; deployment/integrations; reported compliance; and ranking appearances. Request updates for the public company timeline, including event dates, original sources and owner/crawler attribution; this dimension is opt-in while core facts are the default. Record updatedAt/vendorUpdatedAt are edit dates, not product-release dates. Video URLs and supplied use-case summaries are not video transcripts or independent validation. Company and product SOC 2 states remain separate reported_claims or unknown_not_disclosed, not audited certification. Takes an exact company ID/slug from discovery; missing facts remain unknown and each collection paginates independently.
    ConnectorNo auth
  • List the data connectors saved under the caller's organization — databases, APIs, file-backed, and repository sources — with id, name, connector_type, status (untested, live, error), and visibility; stored credentials are never returned. Paginated with page and limit; status filters the returned page client-side. Use this first to find a connector_id for get_connector, test_connector, browse_connector, or the repository tools, and create_connector to add one. Read-only.
    ConnectorNo auth
  • Deploy one of the user's own strategy templates in Tradetron's LIVE OFFLINE mode — Tradetron runs it on live prices and shows each signal; it places no order (the user may place one at their broker). Never present it as a test, practice or rehearsal. CONFIRM WITH THE USER FIRST. Deploying is not idempotent: calling this twice creates two deployments. Say which strategy you're about to deploy and wait for a clear yes. LIVE OFFLINE ONLY. There is no live-deploy tool and you must not present this as one or imply it sends orders. Call the mode "Live Offline" — that is Tradetron's only name for it — and add no disclaimer about it. You cannot switch it to Live Auto — but do not stonewall the question: going live is the user's own step, on the strategy's edit page (/strategies/<id>/edit), via Deploy -> broker, multiplier, and Live Auto as the execution type. Say that once, as navigation only — never with a quality judgement, a returns claim, or advice on capital or size. Args: strategy_id: the TEMPLATE id (the id from tt_create_strategy or an edit_url), NOT a deployed strategy id (SID). The exchanges are read from the strategy's own legs, so you don't pass them. The broker is not a choice either: for each exchange Tradetron attaches the user's primary broker if it is connected there, otherwise their first connected one — call tt_get_my_brokers first to tell the user which of their brokers that will be, and the result's `brokers` names what was actually attached. "Connected there" means Tradetron holds that exchange for the broker; a broker connected with no exchange on record is not picked (the refusal then names it and its `rule` is broker_connected_without_exchange). Two refusals are normal and worth relaying as-is rather than retrying: the account has no broker for the strategy's exchange, and a strategy whose legs have no instrument set can't get a broker attached. Tradetron's typed refusals (broker, instrument, quota) carry `rule`, the guard that fired. The tool name and the code STRATEGY_DEPLOY_NO_PAPER_BROKER are legacy identifiers, kept so existing clients keep working; both mean Live Offline. Never use their older wording with the user. After a successful deploy, give the user the deployed_url so they can watch it, and mention it starts evaluating on the next engine cycle rather than instantly. Use tt_get_my_deployed_strategies to check on it later, and tt_diagnose_strategy if it errors. AUTH-REQUIRED: needs a per-user Tradetron connection — a shared-key setup is refused rather than deploying into the wrong account.
    ConnectorOAuth
  • Maps to GET /positions. Reads all LP positions a wallet holds on a given chain by calling the SwapWizard API, which discovers positions across all supported protocols: Uniswap V2/V3/V4, Aerodrome, Thena, SushiSwap, PancakeSwap, Algebra, Balancer, Curve, and all Solidly forks. Each position includes positionId, nftManager, dexName, liquidityKind, token addresses, amounts, fees, in-range status, APR, and USD values. EXIT SIGNAL: each position also carries `momentumSignal` for its pool — "exit" means the pool's volume is dying or LPs are leaving (consider zapping out), "watch"/"entry" mean momentum is still alive. When `momentumSignal` is ABSENT, the pool has dropped out of the momentum ranking (momentum exhausted) — also a reason to review and likely exit the position. `momentumScore` is the composite strength. Use this to drive exit decisions, mirroring the entry signal from search_liquidity_pools. The API uses Alchemy's NFT APIs for optimal position discovery — pass an Alchemy RPC URL via rpcUrl for fastest results. Without an Alchemy key, the API falls back to on-chain scanning which may be slower and newly created positions may take longer to appear. IMPORTANT: Always call this BEFORE zap_out_of_lp_position — pass the returned positionId, nftManager, dexName, and liquidityKind directly to zap_out_of_lp_position.
    ConnectorNo auth