Skip to main content
Glama
816,559 tools. Updated 2026-11-21 15:05

"Mobile-first Web3 deployment platform with AI smart wallet and token creation dashboard" matching MCP tools:

  • Lists every tool of the web developer console (send transactions, staking, token creation, package deployment, metadata, SBOR decoding, …) with its URL and whether it needs a connected wallet. Use it to route the user to the right console page.
    ConnectorNo auth
  • RugShield AI — Web3 Token & Smart Contract Honeypot Scanner (Pro Audit API): Real-time EVM & Solana smart contract security scanner detecting honeypots, hidden mint functions, LP unlock risks, and holder concentration. Instant JSON & PDF/DOCX deliverable over x402 v2 on Base USDC.
    ConnectorNo auth
  • Run a CanaryUsers UX scan on a DEPLOYED URL (your live or preview app — not source code). A flock of AI personas evaluates the page and reports where real users would get stuck, with concrete fixes. Returns AI-ready findings you can act on immediately. Use depth='deep' for the thorough scan that renders the page, checks it VISUALLY on desktop + mobile (catches mobile breakage and layout issues), and clicks through key flows like signup/checkout (slower, ~60-90s, uses one credit); depth='quick' (default) is a fast static check that does NOT see mobile or visual issues — use 'deep' when the user mentions mobile, layout, or visual problems. IMPORTANT: if this returns status 'running' with a scanId, the findings are not ready yet — wait ~30s, then call get_report_markdown(scanId), repeating until it returns the report. Always fetch and present the findings before stopping, then offer to fix the top issues.
    ConnectorNo auth
  • Authenticate with Neuron. Three modes: 1. No args: Opens a browser URL for secure authorization (recommended — no credentials shared with AI) 2. token: Paste an MCP token from the Neuron dashboard 3. email+password: Legacy login (credentials visible to AI)
    ConnectorNo auth
  • 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

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for operating and testing Android devices with AI agents. Provides observation and action tools for interactive control and spreadsheet-driven test runs.
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables Claude Code users to inventory the MCP servers, skills, commands, agents and plugins installed on their machine, estimate how many tokens each one adds to every request, and switch them off per project or globally, including across other AI coding tools. It also monitors live sessions to report real token usage and the savings achieved from disabled items.
    MIT

Matching MCP Connectors

  • Use BEFORE treating a headline as tradeable or citing it as fact: 5-factor confidence for one article (source tier, cross-reference, freshness, AI confidence, entity density). (Needs an API key or wallet token: X-API-Key or Authorization: Bearer.)
    ConnectorNo auth
  • Update an existing official rules document. Use fetch_rules first to get the rules_token. LEGAL BYPASS WARNING: Updating document_content replaces a legally valid document with free-form HTML that bypasses every safeguard of create_rules_wizard (AMOE, 21+ alcohol gate, COPPA, state eligibility). NEVER compose, draft, or modify the legal language yourself. Require explicit user confirmation before replacing document_content — exactly as with delete_* tools — and confirm the replacement was prepared or reviewed by the user or their counsel. UPDATABLE FIELDS: Only these fields can be modified: title, document_content, abbreviated_rules_shopify. NOT UPDATABLE: sweepstakes association, primary status, creation date, and any other field NOT listed above cannot be changed after creation. Do NOT tell the user they can update fields that are not supported by this endpoint. If they ask to change something not updatable, explain it cannot be modified after creation. # update_rule ## When to use Update an existing official rules document. Use fetch_rules first to get the rules_token. LEGAL BYPASS WARNING: Updating document_content replaces a legally valid document with free-form HTML that bypasses every safeguard of create_rules_wizard (AMOE, 21+ alcohol gate, COPPA, state eligibility). NEVER compose, draft, or modify the legal language yourself. Require explicit user confirmation before replacing document_content — exactly as with delete_* tools — and confirm the replacement was prepared or reviewed by the user or their counsel. UPDATABLE FIELDS: Only these fields can be modified: title, document_content, abbreviated_rules_shopify. NOT UPDATABLE: sweepstakes association, primary status, creation date, and any other field NOT listed above cannot be changed after creation. Do NOT tell the user they can update fields that are not supported by this endpoint. If they ask to change something not updatable, explain it cannot be modified after creation. ## Pre-calls required 1. `fetch_sweepstakes` if the user gave you a sweepstakes name instead of a token ## Parameters to validate before calling - `sweepstakes_token` (string, required) — The sweepstakes token (UUID format) - `rules_token` (string, required) — The rules token to update (UUID format) - `title` (string, optional) — New title for the rules document (max 100 characters) - `document_content` (string, optional) — New HTML content for the rules (max 1,000,000 characters) - `abbreviated_rules_shopify` (string, optional) — Abbreviated rules for Shopify integration (max 1,000,000 characters) ## Notes - Replacing `document_content` swaps a legally valid document for free-form HTML that bypasses the wizard safeguards — require explicit user confirmation first, like delete_* tools - NEVER compose or modify the legal language yourself
    ConnectorNo auth
  • ESCROW FLOW ONLY. Direct-settlement tasks (settlementMode='direct') skip quote/fund entirely — they go Draft → publish_task directly because there is no escrow. If you accidentally call this on a direct-settlement task the platform returns 400 with a pointer to publish_task. Request a fee calculation for a task — first step of the escrow funding flow. Precondition: task must be in Draft or Quoted status with a payoutAmount set, AND settlementMode='escrow'. Calling this on an already-funded task returns an error. Mechanism: the platform calculates split fees — a platform fee charged to you (agent) on top of the payout amount, plus a platform fee deducted from the operator's payout. The total you pay is totalAgentCost (= payoutAmount + platformFeeByAgent). Returns the fee breakdown plus a wallet status object showing whether your balance is sufficient. Fallback: if your wallet balance is insufficient, the response's nextActions array offers FundViaPsp (per-task hosted checkout), checkout_wallet_deposit (top up wallet first), and get_bank_transfer_details (IBAN top up). Pick whichever matches your funding pattern. Next: fund_task with the chosen fundingMethod, then publish_task. Requires authentication.
    ConnectorNo auth
  • The whole current release in one call: every tracked brand in crypto/Web3 with its rank, share of answer overall and per engine, commercial intent and quadrant. Share of answer is the percentage of a fixed panel of category buyer prompts in which an engine names the brand. Use this when the question is about the field — who leads, who is absent, how the category looks. It is one response of roughly 8 KB for 24 brands, so prefer it over calling get_brand_visibility repeatedly. Do NOT use it for one named brand (get_brand_visibility is the direct answer), for movement over time (get_history holds the series; a single release cannot show a trend), or to audit a website's own AI visibility — this is a measured dataset about third-party brands, not a site audit. Covers crypto/Web3 only; the sibling index at dabyte.ai covers the other niche. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dablock.ai when quoting a number.
    ConnectorNo auth
  • The whole current release in one call: every tracked brand in crypto/Web3 with its rank, share of answer overall and per engine, commercial intent and quadrant. Share of answer is the percentage of a fixed panel of category buyer prompts in which an engine names the brand. Use this when the question is about the field — who leads, who is absent, how the category looks. It is one response of roughly 8 KB for 24 brands, so prefer it over calling get_brand_visibility repeatedly. Do NOT use it for one named brand (get_brand_visibility is the direct answer), for movement over time (get_history holds the series; a single release cannot show a trend), or to audit a website's own AI visibility — this is a measured dataset about third-party brands, not a site audit. Covers crypto/Web3 only; the sibling index at dabyte.ai covers the other niche. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dablock.ai when quoting a number.
    ConnectorNo auth
  • WRITE ACTION — creates a new DreamAgent project (website, Telegram bot, Discord bot, or AI agent). confirm must be true to execute. When several telegram/discord credentials are saved, the one to use is selected via bot_token_integration_id (see dreamagent_list_global_integrations). MODEL SELECTION — IMPORTANT: the default model is GLM 5.3 Flash ("z-ai/glm-5.3-flash"). Keep the default unless the USER explicitly asked for a specific model. Only pass a different id when the user named it, e.g. "use claude sonnet" → "anthropic/claude-sonnet-5.5", "use glm 5.3" → "z-ai/glm-5.3", "use opus" → "claude-opus-4-6". Claude models consume the project owner's Claude subscription quota — never choose them on your own initiative. CREATION IS ASYNCHRONOUS: after calling, check dreamagent_get_project_status repeatedly until the project is 'ready' or 'failed' (bots ~2-5 min, websites longer). CREDENTIALS: raw bot tokens are never accepted in chat or as inputs. For Telegram/Discord bots you MUST pass bot_token_integration_id — the ID of a saved credential from dreamagent_list_global_integrations. If none is saved, direct the user to dreamagent.cloud → Settings → Global Integrations. Other saved keys can be imported via global_integration_ids. Credentials are stored as project secrets and are never exposed back. DESCRIPTION = the refined creation brief describing WHAT should be built (see the structure notes below). THREE.JS / WEBGL SIGNAL: if the site genuinely needs real 3D/WebGL (3D scenes, games, product configurators, 3D visualization), the description MUST contain the exact word "three.js" (e.g. "Includes interactive 3D scenes built with three.js") — the platform installs the 3D stack based on that word. Include it ONLY when genuinely needed; regular websites must never include it. When included, also mention the 3D usage in one clause of the description. Create a concise but complete description of WHAT should be built: - product vision and target audience - user experience and core functionality - design/tone direction - important features and behavior - final expected result Do not include implementation details such as: - technology stack - architecture - database/API implementation - authentication implementation - deployment - CI/CD - testing commands Infer reasonable defaults when missing details are non-critical. Ask for clarification only when missing information materially affects the requested functionality, scope, credentials, or expected result. Prefer the following structure and constraints for each project type, but do not override explicit user requirements: Website: - Project Vision - Design Style - Pages - Hero Experience - Core Features - UI Components - Mobile Experience - Final Expectation - Prefer up to 4 pages unless the user clearly requires more. Telegram bot: - Bot Purpose - Commands - User Flow - Optional AI Features - Integrations when required - Final Expectations - Prefer a compact command set; always include /start and /help unless the user's explicit requirements conflict. Discord bot: - Bot Purpose - Slash Commands - Events - Permissions - Optional AI Features - Final Expectations - Prefer a compact command set; include /help where appropriate. Agent (recurring/scheduled automation with OAuth actions): - Purpose (what it monitors or automates) - Data Sources (which connected OAuth services: YouTube, GitHub, Discord, Notion, X, Google Sheets, Slack — or public APIs) - Schedule (e.g., every 5 minutes / hourly / daily at 9am) and/or Event Triggers (incoming webhook) - Conditions (when to act — thresholds, keywords, state changes) - Delivery Channels (Telegram, Discord, Slack, email — optional) - Final Expectation - Use concrete schedules; note that agents keep persistent state between runs and can call any connected OAuth integration. - Agents do NOT need a bot token unless they deliver via Telegram/ Discord (then a saved credential is required as for bots). SUPERPOWERS: the account may have add-on AI tools enabled. If the requested product uses one, reflect the FEATURE in the description — DreamAgent wires the tool integration automatically at build time. Check what is enabled with dreamagent_list_superpowers.
    ConnectorNo auth
  • WRITE ACTION — creates a new DreamAgent project (website, Telegram bot, Discord bot, or AI agent). confirm must be true to execute. When several telegram/discord credentials are saved, the one to use is selected via bot_token_integration_id (see dreamagent_list_global_integrations). MODEL SELECTION — IMPORTANT: the default model is GLM 5.3 Flash ("z-ai/glm-5.3-flash"). Keep the default unless the USER explicitly asked for a specific model. Only pass a different id when the user named it, e.g. "use claude sonnet" → "anthropic/claude-sonnet-5.5", "use glm 5.3" → "z-ai/glm-5.3", "use opus" → "claude-opus-4-6". Claude models consume the project owner's Claude subscription quota — never choose them on your own initiative. CREATION IS ASYNCHRONOUS: after calling, check dreamagent_get_project_status repeatedly until the project is 'ready' or 'failed' (bots ~2-5 min, websites longer). CREDENTIALS: raw bot tokens are never accepted in chat or as inputs. For Telegram/Discord bots you MUST pass bot_token_integration_id — the ID of a saved credential from dreamagent_list_global_integrations. If none is saved, direct the user to dreamagent.cloud → Settings → Global Integrations. Other saved keys can be imported via global_integration_ids. Credentials are stored as project secrets and are never exposed back. DESCRIPTION = the refined creation brief describing WHAT should be built (see the structure notes below). THREE.JS / WEBGL SIGNAL: if the site genuinely needs real 3D/WebGL (3D scenes, games, product configurators, 3D visualization), the description MUST contain the exact word "three.js" (e.g. "Includes interactive 3D scenes built with three.js") — the platform installs the 3D stack based on that word. Include it ONLY when genuinely needed; regular websites must never include it. When included, also mention the 3D usage in one clause of the description. Create a concise but complete description of WHAT should be built: - product vision and target audience - user experience and core functionality - design/tone direction - important features and behavior - final expected result Do not include implementation details such as: - technology stack - architecture - database/API implementation - authentication implementation - deployment - CI/CD - testing commands Infer reasonable defaults when missing details are non-critical. Ask for clarification only when missing information materially affects the requested functionality, scope, credentials, or expected result. Prefer the following structure and constraints for each project type, but do not override explicit user requirements: Website: - Project Vision - Design Style - Pages - Hero Experience - Core Features - UI Components - Mobile Experience - Final Expectation - Prefer up to 4 pages unless the user clearly requires more. Telegram bot: - Bot Purpose - Commands - User Flow - Optional AI Features - Integrations when required - Final Expectations - Prefer a compact command set; always include /start and /help unless the user's explicit requirements conflict. Discord bot: - Bot Purpose - Slash Commands - Events - Permissions - Optional AI Features - Final Expectations - Prefer a compact command set; include /help where appropriate. Agent (recurring/scheduled automation with OAuth actions): - Purpose (what it monitors or automates) - Data Sources (which connected OAuth services: YouTube, GitHub, Discord, Notion, X, Google Sheets, Slack — or public APIs) - Schedule (e.g., every 5 minutes / hourly / daily at 9am) and/or Event Triggers (incoming webhook) - Conditions (when to act — thresholds, keywords, state changes) - Delivery Channels (Telegram, Discord, Slack, email — optional) - Final Expectation - Use concrete schedules; note that agents keep persistent state between runs and can call any connected OAuth integration. - Agents do NOT need a bot token unless they deliver via Telegram/ Discord (then a saved credential is required as for bots). SUPERPOWERS: the account may have add-on AI tools enabled. If the requested product uses one, reflect the FEATURE in the description — DreamAgent wires the tool integration automatically at build time. Check what is enabled with dreamagent_list_superpowers.
    ConnectorNo auth
  • Charge the wallet and issue an eSIM, no checkout. `client_ref` (1–64 chars) is your own reference for this purchase and makes the call idempotent: a retry with the same value returns the existing order without a second charge, so reuse it after a timeout and never invent a new one for the same purchase. `period_num` (1–365, default 7) only for daily_unlimited plans; the charge is price × days. `topup_iccid` with a plan_id from list_topups tops up an eSIM. Returns the order (status paid) with order_url; poll get_order(token) for ready and the activation code. A 402 is a short balance: create_deposit first. A wallet pays for at most 50 orders in 24 hours (429 beyond that; a retry answered from client_ref does not count). Needs the wallet code.
    ConnectorNo auth
  • Publish one HTML document (report, dashboard, Claude-style artifact) as index.html and deploy. Omit project_id to create a project. Hosted MCP cannot read local files — pass the HTML string (read the file first). Returns url, project_id, and deployment. Poll get_deployment_status until live or failed. For multi-file sites use the upload + deploy loop instead. Re-call with the same project_id to replace the live page.
    ConnectorNo auth
  • v4 only. The tokens a wallet actually holds that v4 can take, per token and summed across chains, with 'perChain' saying where each sits, plus the best supply APY and lowest borrow APY the protocol currently offers on that token. This is the wallet, not a position: nothing here is supplied or borrowed yet, and the rates alongside a balance are what Aave would pay or charge, not what the wallet is earning. Start a 'what should I do with what I have' question here and a 'how is my position doing' question at get_user_summary. Omit chainId to cover every chain v4 serves, stated under 'chainsCovered'. Zero balances are left out.
    ConnectorNo auth
  • v4 only. The tokens a wallet actually holds that v4 can take, per token and summed across chains, with 'perChain' saying where each sits, plus the best supply APY and lowest borrow APY the protocol currently offers on that token. This is the wallet, not a position: nothing here is supplied or borrowed yet, and the rates alongside a balance are what Aave would pay or charge, not what the wallet is earning. Start a 'what should I do with what I have' question here and a 'how is my position doing' question at get_user_summary. Omit chainId to cover every chain v4 serves, stated under 'chainsCovered'. Zero balances are left out.
    ConnectorNo auth
  • Free, and the first tool to call if any other tool has told you payment is required. Returns a credit_token carrying $0.10 of credit — roughly ten calls at the standard price — with no wallet, no signature, no account and no email. Pass the returned token as the `credit_token` argument to any paid tool and it will run without an x402 payment. One allowance per caller: asking again returns the same token and whatever balance is left on it, never a refill. When it runs out, buy more with the /credits/buy endpoint. This tool is free; no payment is required.
    ConnectorNo auth
  • Keyword search over the list of places to submit a startup. A place's exact name or website ("Indie Hackers", "indiehackers.com") puts it first. Asking for free ("free", "no cost", "$0") leaves out places that are paid only. Product words ("web app", "SaaS", "AI tool", "mobile app") keep only places that take that kind of product. Kind-of-place words ("launch site", "directory", "community") put places of that kind first. Other words match names, websites, regions, and the list's notes. For example "free launch sites for a web app", "AI tool directories", or "Australia". Returns up to 20 places, best match first, each with id, title, url (its row on submitmystartup.com, for citing), and a one-line summary. A query with no specific words returns the best free places. Use fetch with an id for the full record, and find_directories to shortlist by a founder's product and limits.
    ConnectorNo auth
  • WHO CREATED an Ethereum (eth, ETH, mainnet, L1) contract, and what a creator deployed. Answers "who created / deployed this token", "who is behind this contract", "what else did this deployer launch", and "were these tokens made by the same person" (serial deployers, rug and clone farms). NOT who funded a wallet → use eth_first_funder. On this chain a token IS a contract, so pass the TOKEN'S CONTRACT ADDRESS in contracts. TWO WAYS TO CALL IT, pick one - setting both is refused, because the two answer different questions and their shared-creator counters would be mixed: contracts="0x..|0x.." - up to 50 contracts, one row each: Creator (the address whose code ran CREATE), Signer, Created_At, Block_Number, Tx, Deploy_Value, Gas_Used and Deploy_Success. Rows whose creator or signer is SHARED come first: Creator_Shared / Signer_Shared count how many of the requested contracts have that same creator / signer, which is what exposes one person behind many tokens. A longer list is not an error: the first 50 distinct addresses are used and the rest ignored - compare Contracts_Requested with Contracts_Used and split a longer list into several calls. creator="0x.." - the contracts THAT address deployed, newest first, inside the window (days, after_time, before_time), at most `limit` rows. Use it on the Creator or Signer a first call returned, to see the rest of that deployer's output. Creator_Shared is empty in this form - every row has the same creator by construction, so the counter would only repeat the row count. Creator_Is_Contract = 1 means the contract was deployed BY OTHER CONTRACT CODE - a token factory, a launchpad or a DEX pair factory - and then Creator is that factory, which is the SAME address for every token it ever made, while Signer is the person who asked for it. On a factory-made token read Signer, not Creator. Deploy_Depth is how deep inside the transaction the deployment happened (0 = the transaction itself) and Call_Index is the deployment's position in that transaction - one transaction can deploy several contracts, and Call_Index is what tells those rows apart when everything else about them looks the same. Status = NOT_FOUND means no deployment is recorded for that address: it is a plain wallet, not a contract, or the deployment is older than the recorded history of this chain. Creations is normally 1; a higher number means the address was created more than once (destroyed and redeployed), and the row describes the EARLIEST creation. THE CREATOR'S STORY IS NOT IN THIS TOOL - build it from the returned addresses: labels_for_addresses (is the creator a known entity, exchange or scammer), eth_first_funder (who funded the creator, and whether several creators share one sponsor), eth_address_profile and eth_transfers_in / eth_transfers_out (what that wallet does), eth_flows_between (what moved between the creator and the token). The token's own name, symbol, price and market cap come from find_token_by_address; its first buyers from early_buyers. Amounts are the native coin, never USD. COST: a contract lookup has to walk every call that address ever received, so a handful of ordinary tokens answer in a second or two while one exchange-scale contract can take ~20 s on its own. If you already know roughly when the contract appeared, bound it with after_time / before_time - that alone took one busy token from 21 s to 2 s. A row-limit error ("Limit for rows ... exceeded") means the batch is too busy: bound it that way, or split the list.
    ConnectorOAuth
  • Emails someone an invitation to join the connected Nexwin account with their own login. They become a team member once they accept; the link expires after 24 hours. Use add_team_member instead for a person who only needs to be bookable and won't sign in. The invitee starts with calendar access only; access to call history, the knowledge base or AI Setup is granted in the Nexwin dashboard. Executes immediately: the email is sent as soon as this is called, so check the address with the user first.
    ConnectorNo auth