Skip to main content
Glama
802,489 tools. Updated 2026-11-19 01:45

"A guide to understanding AI agents" matching MCP tools:

  • Get the current user's available AI tokens Returns the number of AI tokens available to the authenticated user. These tokens fund EVERY AI feature in SERPmantics — meta, outline, intent, internal-links, EEAT, EEAT competitors, score, AND the AISSistant prompts. The endpoint lives under /aissistant for historical reasons but the balance is shared across all AI features. Do NOT confuse with guide-creation credits (see /api/v1/credits). For a combined view (credits + tokens) prefer /api/v1/credits.
    ConnectorNo auth
  • What to know before going to a venue, from UPFRONT's venue guide: the bag policy and what fans can bring, gates and entry, parking, getting there by transit or rideshare, and food and drink, including what the guide says about gluten-free, vegetarian or vegan, halal and kosher food. Matches questions like "what's the bag policy at MetLife?", "when do doors open at MSG?" or "where do I park for Lambeau?". venue: the venue's name ("MetLife Stadium", "MSG", "Lumen Field, Seattle"). topics: optional; only these parts, at more length: any of "bags", "entry", "parking", "transit", "food". Without it, every part. Covers the 36 stadiums, arenas and amphitheaters UPFRONT has a guide for; for any other venue the answer says so and lists the ones with guides. Each part is the guide's own words ("text", plus the guide's "faq" questions and answers). factsLastChecked is the date UPFRONT last checked the guide's facts; rules can change for a single event, and the venue's own event page has the final word. guideUrl is the guide on UPFRONT. dietary lists what the guide says per diet; dietaryNotMentioned lists diets the guide doesn't cover, which doesn't mean the venue has nothing for them.
    ConnectorNo auth
  • Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query. IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS. Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was given back (unless the account has unlimited credits, where nothing was reserved): re-sending them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few minutes instead, and contact support if nothing shows up. Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length` with the number of queries you sent, never read `success` alone, and never re-send a query just because it is missing from `guides`.
    ConnectorNo auth
  • The store's front door as text: the full menu with prices, how x402 payment works here, the free shelf, and the house promises. Free. Completes when the guide text returns. NOT a purchase or payment endpoint — to buy, call a buy_* tool with x402 payment in _meta['x402/payment']; this only returns the guide. A store errand, for you the visiting agent — nothing here needs a human's decision.
    ConnectorNo auth
  • Read one of Sendora's documents whole, as Markdown: a guide (sendora://docs/…), an API operation (sendora://reference/…), the error codes (sendora://errors) or an SDK's README and rules for agents (sendora://sdk/readme and sendora://sdk/skill for TypeScript, sendora://sdk/python/readme and sendora://sdk/python/skill for Python, sendora://sdk/php/readme and sendora://sdk/php/skill for PHP, and sendora://sdk/laravel/readme for Laravel). sendora://index lists every document; search_docs finds the right one.
    ConnectorNo auth
  • Use when an investor asks to replay a historical crisis against their current portfolio. Use a scenario_id from list_stress_scenarios and a new request_id. After retry_after_seconds, call get_stress_test with the same request_id. Retries reuse the run and it appears in Investboard history. AI agents may start at most 8 new stress tests and prepared reviews a day for one investor, counted together. The result is hypothetical and leaves the portfolio unchanged.
    ConnectorOAuth

Matching MCP Servers

Matching MCP Connectors

  • Agent-to-agent advertising: labeled placements where autonomous agents look for tools.

  • The second brain your AI agents share. It builds itself from your work and keeps itself current.

  • Returns the canonical guide for using TMV from a coding-agent context. Covers the fix-test-retest loop, how to write a good test prompt, how to read the actionTrail / consoleErrors / failedRequests outputs, and common gotchas. Call this first if you're a new agent on a project — it'll save you a debug session. The same content is served at https://testmyvibes.com/docs/coding-agents.
    ConnectorNo auth
  • Returns the recommended production wallet setup for XRPL agents. Call this instead of create_agent_wallet() when building a production agent. The secure approach keeps the seed entirely in your own environment — AgentTrust only ever sees your public address and signed transactions. create_agent_wallet() returns a seed in plaintext (conversation transcript, logs). This guide shows how to generate locally so the seed never leaves your environment.
    ConnectorNo auth
  • Opens Enpitech's AgentReady scanner as a view in the conversation. Inside the view the scanner fetches the site's public pages and runs 22 checks across five weighted categories (Discovery & Access, Readable for Agents, Structured Data, Actions & MCP, Trust & Safety), then shows a 0-100 agent-readiness score, the per-category breakdown, and the fixes ranked by the points each would recover. Use it when the user asks how ready a website is for AI agents, their own or any site they name: how readable, accessible or usable it is to AI, to agents or to AI crawlers; whether ChatGPT or Claude can read or use it; how to show up in AI answers; or for an audit of llms.txt, robots.txt, schema.org markup or MCP support. url is optional: with no URL the scanner opens with an empty input for the user to fill in. This tool returns only the URL it was opened with; the scan runs inside the view, via agentready_scan.
    ConnectorNo auth
  • Checks whether AI assistants and AI agents can understand and act on a business from its public website, and explains what gets in the way. Use it when the user asks things like: "Does AI understand my website?", "What would an AI think this company does?", "Why doesn't ChatGPT know what my company sells?", "Is my site ready for AI agents?", "Audit this site for machine readability", "Can an AI figure out the pricing and how to buy or become a customer?", "What information is missing for AI to understand this business?", or after they changed their site and want to check the result. Returns a deterministic 0-100 AI Visibility Score across 8 dimensions (crawl access, business identity, offerings, pricing, structured data, trust, agent actionability, recommendation confidence), how AI would likely describe the business, what it could not determine, and the highest-impact issues, each with evidence (quotes and source URLs) and a one-line fix summary. Free. It never changes the website: it reads public pages the way AI crawlers do (raw HTML, robots.txt, structured data, llms.txt). When no recent analysis exists it runs one and stores the report on CanAIReadMe. It reuses an analysis up to 7 days old unless fresh=true (free re-analysis once per 24 hours per site). A site it has not seen takes about 10 to 40 seconds; if the result has status "running", call again with the returned scan_id. Do not use it to explain concepts (SEO, GEO, schema.org), for general SEO or marketing advice, to write content or build websites, to track brand mentions or rankings in AI answers (it does not measure those), or when no specific website is involved. To answer what a company does, sells or costs, use get_business_profile instead.
    ConnectorNo auth
  • Generates the complete, implementation-ready fix for the problems that stop AI systems from understanding a website. Use it when the user wants to fix what makes their site hard for AI agents to understand (its AI visibility), says "fix it" after an audit, wants to buy the AI visibility fix, or needs the exact changes (JSON-LD, meta tags, llms.txt) for a developer or a coding agent. Call it directly in those cases: it analyzes the site itself when needed, and its quote includes the current score and main problems to show the user next to the price. Delivers a machine-executable change list (target location, instructions, code snippets, before and after copy, validation criteria, score dimension affected), rewritten copy AI can understand, ready-to-paste schema.org JSON-LD, meta tags, llms.txt and robots.txt rules, FAQ answers, and 5 private re-scans over 60 days to verify the result. Paid: $49 one-time per website, not a subscription, refundable within 14 days. Calling this tool never charges anyone, so call it without asking first: the quote is free and safe. Without a completed purchase it returns status "payment_required" with the price, what is delivered, a purchase_id, an access_token and a secure Stripe checkout link. Then show the user payment.user_message (score, main problems, price, refund) and share the link only if they agree; the user reviews and pays on Stripe's page. After they pay, call again with purchase_id and access_token to receive the package. Pass an idempotency_key (a new UUID per purchase): retries with it return the same purchase and link instead of a second checkout. CanAIReadMe does not modify the website: apply the changes only with the owner's permission. If the user only wants to know what is wrong, use audit_ai_visibility instead. Do not use it for general advice or for a site the user has not asked to fix.
    ConnectorNo auth
  • PRO+ AI scheduling tool for agents. Proposes a new schedule for a project that fits all tasks before a target deadline while respecting dependencies. Designed for multi-turn agent workflows: call with mode="preview" to generate and present the proposal to the user, then call with mode="apply" once the user confirms. APPLY captures a "Before AI Schedule Proposal" baseline and commits all proposed dates in one atomic operation (requires project Owner or Manager role). Optionally levels resources to avoid overallocation. Cap: 100 tasks. Feature: aiAdvanced (PRO+).
    Connector
    Destructive
    OAuth
  • Fetch the Markdown for a single BANKSapi docs page. Accepts a docs path (e.g., /guide/quickstart) or a full URL; any .md/.html suffix and section index (e.g. /guide) are handled. For the API reference paths /api/banks-connect, /api/ai-connect and /api/pay-connect this returns a compact operation index rendered from the OpenAPI spec. Use when you need specific page content or code samples. Prefer 'search-banksapi-docs' for broader questions. Call 'get-banksapi-overview' first to get a list of available pages.
    ConnectorNo auth
  • Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Free to call. Lists the 7 AI Alert types (follow, sub, donation, bits, giftsub, host, raid), the two render tiers (Standard=Veo, Pro=Kling) with their real current credit prices (silent and with audio), and the character-generation price -- all derived live from AlertForge's billing config, never hardcoded. Call this before plan_alert_pack or generate_alert_character.
    ConnectorNo auth
  • Generate an original image with AI to accompany a post (#441). Describe the picture you want; the workspace's brand style guide is applied server-side, so do NOT restate colours or visual style. Takes 10-30 seconds. Costs one of the account's monthly image credits and returns the balance. Over MCP it returns an s3_key you pass to draft_post / save_draft / update_draft via the `images` field; over SMS/WhatsApp the picture comes back as an attachment. Either way it is saved to the user's media library. Use `upload_image` instead when the user already has a picture.
    ConnectorOAuth
  • List AI agents (`GET /v2/agents`): by default your own agents plus the public ones. Pass `appId` to list only the agents homed in that app (`GET /v2/apps/:appId/agents`, which needs you to manage the app; B2B tokens always use this form). Agents belong to your account, not to one app, so the same agent can answer in several of your apps. Public agents (e.g. the platform's Support Agent, sample personas) can be tried with `ethora-agent-try` and copied with `ethora-agent-clone`, not edited. Returns agents with ids, names, owner, visibility, categories and config. Auth: user session or B2B token. Errors: 401/403 wrong auth; empty list when nothing matches.
    ConnectorNo auth
  • Live check of ANY online store, tracked by Neoavis or not: can an AI shopping agent read it without clicking? Reads the UCP checkout profile (/.well-known/ucp), structured product data, robots.txt access for shopping agents, llms.txt and sitemap, in a few seconds. Use it when the user wants to buy from a store that consulter_marchand does not know, or wants to know if their own store is ready for AI agents. For a store Neoavis already tested, consulter_marchand gives the full purchase test. Returns: points (out of 15), verdict (pret, partiel or pas_pret), criteres_reussis, neoavis (score out of 100 and page when tracked), resume (one sentence to quote), detail_gratuit_humain (page with the per-criterion detail for a human) and suites_payantes (x402 URLs, USDC on Base, no account: per-criterion live check, and a full purchase test). Free: 10 checks per hour per address. Unreadable domain or unreachable site: error result.
    ConnectorNo auth
  • [AFFILIATE / REFERRAL / MARKETING, one programme, three names] Register as an RRG referral partner / marketing partner / affiliate. This is THE single programme for earning commission by bringing other agents to RRG. Works identically for humans and AI agents, identity is just your Base wallet. Partners earn 10% commission (1000 bps) on the platform's share of revenue from agents they refer/recruit. You will be assigned a unique partner ID and can start referring other agents immediately via `log_referral`. Requirements: a Base wallet address and an optional ERC-8004 agent ID.
    ConnectorNo auth
  • [AFFILIATE / REFERRAL / MARKETING, one programme, three names] Register as an RRG referral partner / marketing partner / affiliate. This is THE single programme for earning commission by bringing other agents to RRG. Works identically for humans and AI agents, identity is just your Base wallet. Partners earn 10% commission (1000 bps) on the platform's share of revenue from agents they refer/recruit. You will be assigned a unique partner ID and can start referring other agents immediately via `log_referral`. Requirements: a Base wallet address and an optional ERC-8004 agent ID.
    ConnectorNo auth
  • Search Scout's public licensed-agent directory. Returns agents sourced from state REC public rosters + MLS-ranked prospect lists. Indexed states are listed in scout.coverage() — call that first if you're unsure whether a state has meaningful data. Every result has a claim_url — unclaimed agents can claim to curate their AI profile and start receiving AI-routed leads. Unlike scout.find_agent (which requires a live pin), this returns the full directory regardless of pin freshness. Prefer scout.find_agent when you want agents who are live-available right now; prefer scout.find_public_agent when you want broad discoverability. Pass lat/lng OR address (US street address — we'll forward-geocode via Mapbox) to get distance-ascending results with a distance_miles field on each agent; otherwise results are sorted by flika_score descending.
    ConnectorNo auth
  • Samples the major AI engines for which companies they name for a query (e.g. "best CRM for startups"); returns a consensus shortlist (≤5). Use when you want to know who agents *recommend* for a category — not where a specific brand is mentioned (use scan_visibility for that). Free, no URL needed. Result: { companies[], tool_schema_version }.
    ConnectorNo auth