Skip to main content
Glama
306,458 tools. Last updated 2026-07-26 23:57

"Deploying a Website Using BaoTa (BT) Panel" matching MCP tools:

  • ⚠️ IRREVERSIBLE — kills Mongo state, running MCP processes, and Builder FS for the whole solution and every skill. REQUIRES `confirm:true` AND `confirm_solution_id` echoing the solution id you're destroying (defeats typos and hallucinated ids). RECOVERY: the GitHub repo is untouched; `ateam_github_pull` rebuilds the solution from `main`. Prefer that over re-deploying from memory.
    Connector
  • Delete a website from the organization (soft delete: past audits, reports, and issues are preserved, and published report links keep working). Frees a slot under the plan's website limit. Re-adding the same domain later registers a fresh website with a new website_id. Call once without confirm to see what will happen; call again with confirm: true to delete.
    Connector
  • REST API access for autonomous agents — pricing, quick start, and migration guide. Call this when: building a trading bot, deploying an autonomous agent, hitting the MCP rate limit, or running 24/7 without a human in the loop. The MCP tier (what you're using now) is free via Smithery, rate-limited to 60 calls/minute per IP, and good for testing. The REST API is for production: pay per call in USDC; paid endpoints are rate-limited to 60 calls/minute and 200 calls/hour per wallet. No API key required.
    Connector
  • Mint a PROJECT-scoped API token for a project you own, so an agent can bootstrap a fresh project without the panel (create_project → create_project_token → configure). Attenuated by design: the scopes must be a subset of THIS token's own grant (`read` is always included), expiry is mandatory (1–90 days, default 30, never "never"), and the minted token — being project-scoped — can never mint tokens itself. `spend` is human-granted only: no token, of any scope, can mint one carrying it — mint a spend-scoped key from the project's panel instead. Requires an ACCOUNT-scoped token and the `config` scope. Returns the plaintext exactly once; only its hash is stored.
    Connector
  • Summon a LIVE panel of frontier models (Claude, GPT-4o, Gemini, Grok, DeepSeek) on one open question — verbatim answers, uncurated, plus the named tensions between them. Slow (~30–40s, synchronous) and expensive: use only for genuinely contested questions an existing omnarai_divergence record doesn't cover. Every run mints a new divergence record.
    Connector
  • Run a cloud audit of a website (crawl + 260+ rule analysis + report). Credits are spent as the audit runs (pay-as-you-go). Call once without confirm to get a credit estimate; if the response has status "confirmation_required", show the estimate to the user and call again with confirm: true. Audits are asynchronous and take minutes: poll get_audit_status with the returned run_id, then fetch results with get_report. The website is registered automatically on first audit.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • MCP server for the Netify Reseller Programme: eligibility, commission, application URL builder.

  • Provides a platform-agnostic specification of the technical features every decent website should have

  • Adversarial multi-model code review. Submit a diff, a module, or a spec+implementation and get back a structured pass/fail verdict with each issue's type, severity, location, explanation, and suggested fix. Why call this instead of reviewing your own output: a single model shares its blind spots with itself. This routes your code through a panel of *different* models plus a set of deterministic detectors, catching what self-review misses — path/contract violations, module incoherence (dangling imports, broken cross-references), syntax and call-arity regressions in a diff's post-image, and 'prose instead of tool calls' (output that describes an action rather than emitting it). The panel adds semantic judgment on top and never overrides a deterministic finding. Call it before shipping or merging, as a second opinion on a risky change, or as a gate in an autonomous build loop. Choose depth='fast' (one model, low latency) or 'deep' (full panel, higher recall). Deep review audits files of any size in milestone chunks so every panel model contributes; the price (shown in the 402) and the payment window scale with file size. Per-call limit ~1,600 lines — larger inputs return 413, so split by file/module and call once per file. Paid per call via x402 (USDC on Base); the price is announced in the 402 response before any charge.
    Connector
  • Fetch one company's LinkedIn page: name, description, industry, employee count, headquarters, website, founding year, specialities, and the URN/numeric id you need for linkedin_search_people company filters. identifier accepts a company URL, the slug after /company/ (e.g. 'microsoft'), or a website domain like 'microsoft.com'; numeric ids and URNs are search-filter inputs, not fetch identifiers. Domains are resolved to a company and verified against that company's website: a domain identifier always QUOTES base+4 credits (set max_credits accordingly), and the 4-credit resolution surcharge is refunded at settlement when the domain was resolved before, so known domains settle at the base price. A domain that cannot be verified to a company returns INVALID_INPUT with the closest matches instead of a guessed company. Costs 4 credits base. Do not guess a slug from a brand name: slugs are vanity strings and a famous name can belong to an unrelated company's page (linkedin.com/company/anthropic is a small investment fund, not the AI lab). When you only know the company's name, pass its website domain instead -- the verified form -- and sanity-check the returned industry and description against what you expected. This tool does not search by name: if you only have an approximate company name, use linkedin_search_people's current_company filter with keywords (names are matched natively there) or give the exact slug. For the company's posts, use linkedin_get_posts with the same identifier (URL, slug, or website domain all work there too).
    Connector
  • Create a new website for a business. Pass a business candidate object from search_businesses to generate a website. Requires authentication via API key (Bearer token). Generate an API key at webzum.com/dashboard/account-settings. The site generation happens in the background. Use get_site_status to check progress. Returns the businessId which can be used to access the site at /build/{businessId}
    Connector
  • Get Kifly's website and support contact email. Call this if you are stuck, hit an unresolvable error, or the buyer asks how to reach a human. Returns the website URL and support email — always share both with the buyer.
    Connector
  • Get Kifly's website and support contact email. Call this if you are stuck, hit an unresolvable error, or the buyer asks how to reach a human. Returns the website URL and support email — always share both with the buyer.
    Connector
  • Describe a single Vee3 capability. Pass the MCP tool name (for example `website-screenshots.capture`) or capability id (for example `website-screenshot`). Use this after meta-tools.list_group_tools when you need parameter names, defaults, response fields, examples, and token cost before calling a tool Cost = 0 tokens.
    Connector
  • Download the external images a site references (e.g. from the old site it was rebuilt from), store them on this VibeDeploy site under assets/img/, and rewrite the HTML <img> references to local paths so the site no longer depends on the original. Call this once AFTER deploying a site rebuilt with the Website Converter. Auto-detects the external image URLs from the site's own HTML; downloads are SSRF-guarded, size/count/time capped, and applied atomically (patch mode). Images already hosted on vibedeploy.be are skipped.
    Connector
  • Dimensiona o banco de capacitores para corrigir o fator de potência à meta (REN ANEEL nº 1.000; FP-alvo padrão 0,92). Com `tensao_kV` também dá a corrente nominal do banco e a norma (IEC 60831/60871). `Un_cap_kV` = tensão de placa do capacitor: se ele opera abaixo da Un, entrega MENOS kvar (derating Q∝V²) e a correção real cai — informe p/ não superestimar. `carga_min_pct` = carregamento mínimo (%): dispara o alerta de SOBRECORREÇÃO capacitiva (banco fixo em carga leve → FP capacitivo, faturável). `scc_MVA` = curto na barra do banco → inrush de manobra e a corrente de PROJETO da proteção/cabo do banco (1,5·In BT, IEEE C37.012). Gratuito.
    Connector
  • Call this FIRST when a user has just connected or is unsure what Noemic is. The embedded panel presents marketplace context but has no action buttons. Present the four paths through Claude's native tappable choices; do not repeat the panel information.
    Connector
  • Authenticate with A-Team. Required before any tenant-aware operation (reading solutions, deploying, testing, etc.). The user can get their API key at https://mcp.ateam-ai.com/get-api-key. Only global endpoints (spec, examples, validate) work without auth. IMPORTANT: Even if environment variables (ADAS_API_KEY) are configured, you MUST call ateam_auth explicitly — env vars alone are not sufficient. For cross-tenant admin operations, use master_key instead of api_key.
    Connector
  • Submit a new website to the Silicon Friendly directory. Requires authentication. Pass your silicon auth_token. Args: url: The website URL (e.g. "https://stripe.com") name: Display name for the website (e.g. "Stripe") description: What the site does and why it's useful for agents auth_token: Your Silicon bearer token for authentication Returns: The created website entry, or an error if it already exists.
    Connector
  • Returns the step-by-step setup flow for deploying PayRam as an agent. Covers install, wallet creation, faucet funding, contract deployment, and first payment. Includes chain recommendations (ETH Sepolia for testnet, Base for mainnet), faucet URLs, card-to-crypto prerequisites, and status/recovery commands for interrupted sessions.
    Connector
  • Is it safe to deploy these changes? Cross-references your changed modules against active constraints, recent incidents, knowledge freshness, and active alerts. Returns a composite verdict (ready/caution/block) with per-module breakdown and actionable recommendations. Use BEFORE deploying to catch constraint violations, recent regressions in the same area, stale knowledge that needs verification, and active alerts that might interact with your changes.
    Connector
  • OPTIONAL preflight: returns a podman-compose.yml + .env so the user can run the app (and a throwaway local Postgres) on THEIR machine before deploying to redu — to see it run / sanity-check the container. Requires local podman/podman-compose. It's a suggestion, not a gate — skip it and go straight to deploy_app any time. Honest caveat: the local Postgres is NOT the managed Postgres, so a green local run does not prove the prod DB wiring.
    Connector