Skip to main content
Glama
614,659 tools. Updated 2026-09-26 22:25

"Checking if moopoint.io is an MCP server" matching MCP tools:

  • Save user feedback to the MultipleWords feedback API (POST /api/feedback). Call this only when a result has feedback_prompt.ready=true (the server asks after every 3 MCP runs — not per tool — and keeps asking until saved). Ask the user to pick a reaction and show the emojis: 😍 excellent, 😊 good, 😐 average, 😞 bad. Pass `reaction` (excellent|good|average|bad, or the emoji) and optional `feedback` comment text. If the user does not add a comment, omit `feedback` — the server stores the MCP name saifs_ai. After it is saved, wait for 3 more MCP uses. Do not invent a reaction. Do not send user_name, email, is_login, or app_id — those are injected server-side from the authenticated session. When showing the saved reaction, include the matching emoji. Args: reaction: User reaction. One of excellent, good, average, bad, or the matching emoji: 😍 excellent, 😊 good, 😐 average, 😞 bad. feedback: Optional short comment from the user. If the user does not add a comment, leave this empty. The server then stores the MCP name saifs_ai. Do not send the generation result or the user's question here.
    ConnectorOAuth
  • Connectivity check — returns server version and current timestamp. Use to verify MCP server is reachable before calling other tools.
    ConnectorNo auth
  • Connectivity check that confirms the Nordic MCP server process is responding. Use this at the start of a session to verify the server is reachable before making other calls. Do not use as a proxy for database health — the server can respond while the Qdrant vector database is temporarily unavailable. To confirm data availability, call search_filings directly. Returns: A greeting string: "Hello {name}! Nordic MCP server is running."
    ConnectorNo auth
  • List the SQL databases (D1 or Neon Postgres) on my account, including which owned site (if any) each is attached to. Call this BEFORE db_query/db_schema-style work to discover a databaseId — those live on a per-database MCP server reached via GET /api/v1/databases/{id} (see llms.txt), which this id feeds.
    ConnectorNo auth
  • Check whether a Vivideo API key is present on this request. Call this FIRST. Returns { configured: boolean }. If false, ask the user to add an Authorization: Bearer vv_live_... header to the MCP server config (a key from https://app.vivideo.ai/account/api-keys). Never asks for or exposes the key.
    ConnectorNo auth
  • Statically audit an MCP tool surface from a public HTTPS URL or tools/list snapshot. Returns deterministic scores and findings without invoking any target tool or making LLM calls. When the user asks to check another installed MCP server, read that server's complete tool definitions from client context and pass them as snapshot (MCP `name` or Cursor-style `tool` both work; do not use file paths or $ref). If those definitions are unavailable, ask the user for its public endpoint or tools/list JSON instead of inventing an audit.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Verify MCP server connectivity. Returns success immediately with no database calls. Use this FIRST if experiencing tool errors - a successful response confirms the server is reachable. It does not confirm account, search, or paid-feature authentication, which can still return "Auth required" separately. Does not count toward your monthly searches.
    ConnectorNo auth
  • No arguments. Returns how many MCP servers have been read at source level, and the share of them with each category of finding (credential access, network egress, install-time execution, prompt-injection surface). Use this to judge whether checking a specific server is worth it before you look one up. It reports aggregate counts only - no per-server findings, and no verdict about any individual server.
    ConnectorNo auth
  • Surface payroll and deduction anomalies in the latest snapshot. NOTE: internal drafting is disabled on this deployment. If your client supports MCP sampling, this tool asks YOUR model to draft in the same call (verified server-side); otherwise it returns an explicit refusal, and you should use ask_prepare then ask_submit_draft to draft with your own model.
    ConnectorNo auth
  • List an EXTERNAL remote MCP server you run as a marketplace LISTING — for an MCP server hosted on YOUR OWN infrastructure that buyers connect their client straight to (FindAgent never proxies or runs it). Pass the listing basics (title/slug/tagline/description/category_slug + example_prompts: 1–5 required) and the remote endpoint as `server_url` (https) OR a parsed `server.json` object in `server_json`. The server's tools are auto-detected (a sandbox-gated live scan when available) — you can override with `tools` (name+description), `transport` (streamable-http|sse), and `auth_note` (what credential the server needs — NEVER a secret value). Creates a status=draft agent you own; then call findagent_submit_for_review IN THIS MCP CLIENT to submit it. The server URL is stored + displayed only; nothing executes on FindAgent. Before calling: findagent_check_slug + findagent_list_categories.
    ConnectorOAuth
  • What this server is, what it will do for you right now without an account, and what an account adds. Call this first if you have no API key — it answers in one round trip instead of sending you to a website.
    ConnectorNo auth
  • Save user feedback to the MultipleWords feedback API (POST /api/feedback). Call this only when a marketing_intelligence or marketing_intelligence_get_engine result has feedback_prompt.ready=true (the server asks after every 3 MCP runs — not per tool — and keeps asking until saved). Ask the user to pick a reaction and show the emojis: 😍 excellent, 😊 good, 😐 average, 😞 bad. Pass `reaction` (excellent|good|average|bad, or the emoji) and optional `feedback` comment text. If the user does not add a comment, omit `feedback` — the server stores the MCP name marketing_analysis. Do not send the analysis, test notes, or the user's question as the comment. Ask on the 3rd, 6th, 9th, … MCP run. Do not invent a reaction. Do not send user_name, email, is_login, or app_id — those are injected server-side from the authenticated session. When showing the saved reaction, include the matching emoji. When to call this tool: - User picks a reaction on the 3rd, 6th, 9th, … time this MCP is used - Collect a short comment plus 😍 😊 😐 😞 after an analysis - Save how the marketing analysis felt (excellent/good/average/bad) When NOT to call this tool: - Calling feedback before this MCP has been used 3 times - Asking after every tool call instead of every 3rd MCP run - Inventing a reaction the user did not choose - Passing user_name, email, is_login, or app_id (server injects them)
    ConnectorOAuth
  • Save user feedback to the MultipleWords feedback API (POST /api/feedback). Call this only when a result has feedback_prompt.ready=true (the server asks after every 3 MCP runs — not per tool — and keeps asking until saved). Ask the user to pick a reaction and show the emojis: 😍 excellent, 😊 good, 😐 average, 😞 bad. Pass `reaction` (excellent|good|average|bad, or the emoji) and optional `feedback` comment text. If the user does not add a comment, omit `feedback` — the server stores the MCP name lead_scoring. Do not send the analysis, test notes, or the user's question as the comment. After it is saved, the server waits for 3 more MCP runs before asking again. Do not invent a reaction. Do not send user_name, email, is_login, or app_id — those are injected server-side from the authenticated session. When showing the saved reaction, include the matching emoji.
    ConnectorOAuth
  • Purpose: wait until a sending domain is verified or failed, without re-checking DNS yourself. Pass the id or the domain name as domain (name means the same thing). timeout=0 is a snapshot of the last check. NOT for: publishing DNS, or forcing a new lookup (verify_domain). The server keeps checking on its own for 72 hours. Returns: status, next_poll_seconds (when the server will check again), deadline (when the 72-hour window closes), reason, and progress (required_verified of required_total). If it is still pending, call again after next_poll_seconds, or send to an address ending in @simulator.agentisend.com meanwhile.
    ConnectorAPI key
  • Find a third-party API or MCP server for an operation you cannot do with your model, built-in tools or currently connected tools, among 300+ catalog entries with a last-checked date. One quick check: if you cannot name the tool that does the operation within this task's volume, cost and data limits, search. Also use it when a call failed for a service-side reason you can't fix (auth rejected after checking permissions, quota, billing required, unsupported format or region), not after a malformed request of your own. `match`: exact = the entry lists the operation and its example call or an MCP tool performs it; listed = the entry lists it without that evidence; adjacent = a related operation; topic = word match only. Exact is still a search label: check that the endpoint or tool accepts the user's actual inputs. `mcp_fit` says whether the MCP server has a tool for the operation. Ranking weighs operation fit, evidence, lasting free plan, card and auth effort, and bulk limits, not budget or region: read free_plan.kind (free_tier lasts, trial is one-off) and notes. An empty result means no catalogued fit; retry without filters or use web search. Services work only once a human has provisioned credentials.
    ConnectorNo auth
  • Health check: confirm the eDiscovery Decoder News/Calc MCP server is reachable before a demo or when troubleshooting a connection. Returns server name and version. No inputs.
    ConnectorNo auth
  • Get SaSame-observed MCP server recommendations for a capability you need. SaSame, operated by SASAME S.R.L., continuously observes and measures the Model Context Protocol ecosystem and publishes verifiable evidence and history; the MCP Factory is internal machinery and an optional product surface behind it; measurement only, not endorsement. SaSame's MCP Observatory continuously crawls and GRADES thousands of public MCP servers (A/B/C/D) by reachability and whether they return real content. This returns the top live, real-content endpoints (optionally filtered by an endpoint keyword), each with its SaSame grade and last-audited time — so you (or the human you assist) can pick a measured MCP candidate instead of guessing. Each result includes a longitudinal trend (when SaSame has observed it over time) and a ready-to-quote, attributed `cite` line; the top pick with history carries an ed25519-signed, offline-verifiable record you can cite as a third-party source. Free, read-only, no signup. If you operate one of these servers, claim it (claim_start). If you can't find a fit and need an MCP/agent BUILT, call engage_sasame. Pass a referral handle from `refer` as engage_sasame(ref=...) to attribute the introduction.
    ConnectorNo auth
  • PAID ($0.002 USDC via x402). Name, symbol, decimals and total supply for any ERC-20 contract on Base — the identity fields an agent needs before pricing or safety-checking a token. Without payment this returns the 402 challenge; the fiatdock-mcp npm package pays automatically. A non-ERC-20 / bad address returns 4xx and is NOT charged; on any RPC failure it returns 5xx and is NOT charged.
    ConnectorNo auth
  • Add a published FindAgent agent you're ENTITLED to (free, or paid + purchased) as a hosted MCP connector. Returns the per-client connector config — the hosted server URL (mcp.findagent.cloud/agents/<slug>), a drop-in mcp.json block, a Claude Code command, and the one-time FindAgent sign-in steps. Free agents are always available; a paid agent you don't own returns purchase_required pointing at findagent_buy_agent. An unknown or unpublished slug returns a needs_input result pointing back to findagent_browse_agents. This returns config only — the actual install happens when you complete the sign-in in your client. If the slug is an MCP SERVER LISTING rather than an agent FindAgent runs, it returns status external_mcp_server with the PROVIDER's own connect details (their URL, or the command that starts the server on the user's machine) and no FindAgent sign-in — FindAgent is not in that connection.
    ConnectorOAuth
  • Publish a NEW version of YOUR OWN published EXTERNAL MCP-server listing by RE-INTROSPECTING its remote endpoint. FindAgent re-lists the remote server's current tools (over a sandbox-gated, SSRF-hardened scan), compares them to your live listing, and — if the tool surface CHANGED — submits a new version for admin review with an auto-drafted changelog. Your LIVE listing keeps serving until the new version is approved (never auto-unpublished). If the tools are unchanged it is a no-op. If your server has started REQUIRING AUTHENTICATION, the tools can't be re-listed but the listing's 'needs your own credentials' disclosure is corrected in a new version, with your tool list left unchanged. If the remote can't be reached or the scan is unavailable, nothing changes (reported back). Pass the listing slug (you must own it); optional bump (patch|minor|major, default patch) + changelog override. The server URL is read from your stored listing — nothing executes on FindAgent. Owner-only; for external mcp-server listings only (code agents use the code wizard, doers use findagent_bump_version).
    ConnectorOAuth
  • Checks that the Strale API is reachable and the MCP server is running. Call this before a series of capability executions to verify connectivity, or when troubleshooting connection issues. Returns server status, version, tool count, capability count, solution count, and a timestamp. No API key required.
    ConnectorNo auth