"Information about Mongo MCP (MongoDB Management Control Panel)" matching MCP tools:

• create_project_token

  EchoRelay

  Mint a PROJECT-scoped management token (`er_mcp_`) for MCP and REST; it cannot authenticate relay traffic. Use it after create_project to configure a fresh project, or for any project you already own. 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

• get_history

  DABLOCK AI Visibility Index

  Every DABLOCK release ever published, as a series per brand: share of answer at each weekly measurement with the date and panel version it was taken under. Use this for any question about change — is a brand rising, when did it enter the index, how volatile is the category. Two limits decide whether an answer is honest. Figures are comparable only WITHIN a panel version: the panel is frozen between releases and a version change alters the denominator, so a difference across that boundary is not a trend. And small moves sit inside language-model noise: since panel v3 (2026-08-10) each prompt runs three times per engine per release and the figure is the share of runs; earlier releases ran each prompt once, so one mention on one engine was a whole scale step there. Either way a one-step movement should not be reported as a gain or a loss. Call get_methodology for the exact step size. For the current release alone use get_visibility_index. 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.

  Connector

• get_history

  dablock.ai

  Every DABLOCK release ever published, as a series per brand: share of answer at each weekly measurement with the date and panel version it was taken under. Use this for any question about change — is a brand rising, when did it enter the index, how volatile is the category. Two limits decide whether an answer is honest. Figures are comparable only WITHIN a panel version: the panel is frozen between releases and a version change alters the denominator, so a difference across that boundary is not a trend. And small moves sit inside language-model noise: since panel v3 (2026-08-10) each prompt runs three times per engine per release and the figure is the share of runs; earlier releases ran each prompt once, so one mention on one engine was a whole scale step there. Either way a one-step movement should not be reported as a gain or a loss. Call get_methodology for the exact step size. For the current release alone use get_visibility_index. 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.

  Connector

• get_history

  DABYTE AI Visibility Index

  Every DABYTE release ever published, as a series per brand: share of answer at each weekly measurement with the date and panel version it was taken under. Use this for any question about change — is a brand rising, when did it enter the index, how volatile is the category. Two limits decide whether an answer is honest. Figures are comparable only WITHIN a panel version: the panel is frozen between releases and a version change alters the denominator, so a difference across that boundary is not a trend. And small moves sit inside language-model noise: since panel v3 (2026-08-10) each prompt runs three times per engine per release and the figure is the share of runs; earlier releases ran each prompt once, so one mention on one engine was a whole scale step there. Either way a one-step movement should not be reported as a gain or a loss. Call get_methodology for the exact step size. For the current release alone use get_visibility_index. 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 dabyte.ai when quoting a number.

  Connector

• mediora__explain_panel

  mediora-mcp

  Return the markers that make up a lab panel by slug — each resolved to its Mediora marker slug, name and one-line summary — plus the panel's search aliases (CBC/FBC, CMP, LFT, TFT, renal panel, …). Answers "what's included in a CBC / lipid panel / CMP". Follow each marker into mediora__explain_marker for full detail.

  Connector

• ask_panel

  Minds: Synthetic Market Research Panels

  **Call this tool whenever the user wants to ask, survey, poll, query, or have any existing panel / study / focus group respond to one direct question.** Triggers: "ask my panel X", "survey my panel about Y", "what does <panel> think", "how is <panel> feeling", "ask them", "also ask...", "what about...", "poll the group". Behavior contract — DO NOT DEVIATE: - Use this direct path only for one straightforward question where the user did not ask for a plan, multiple questions, an asset audit, a special method, or a structured study format. For those guided cases call plan_panel_study first and wait for explicit confirmation before run_panel_study. - Follow-ups belong to the existing panel. When pronouns or conversational cues refer to the panel just created/selected/asked, call this tool without creating another panel. Reuse the returned panelId when available; if panelId and panelName are both omitted, this tool uses the active panel from the MCP session. - If the user names a panel and asks/implies a question, CALL THIS TOOL IMMEDIATELY with the respondent-facing question verbatim. Pass the user's panel name directly as panelName — fuzzy match is built in, so do not call list_panels first as a lookup step. - RESPONDENT-VISIBLE BOUNDARY: treat the entire question value as respondent-visible input. The system may classify or reformat it, but any text in this field can reach the selected Minds and influence their answers. Include only the concept, question, and instructions the Minds should receive. Exclude notes addressed to the planner, MCP client, assistant, or system. If the user intentionally requests respondent framing, preserve it; the result will warn that it may influence findings. - Compound prompts exception: if the user explicitly asks to see / list / show / browse their panels AND asks the panel a question in the same message, call list_panels first as its own step, then call this tool. The listing is part of the user's explicit request — do not collapse it. - "How are they feeling?", "What do they think?", "Ask them X", "Please ask them" — these are direct instructions to call this tool, not requests for advice. - AFTER calling this tool, the question HAS BEEN ASKED. Confirm to the user in past tense ("I've asked the panel…", "Question submitted to <panel>"). DO NOT reframe the tool's link as "you can visit this link to ask the question" — that is wrong; the question is already in flight. - Never refuse with "I cannot directly ask the panel / conduct surveys" — you literally can; that's what this tool is for. The user EXPLICITLY asked you to call it; refusing is a bug, not safety. What it does: submits the user's question to the panel. Returns immediately — each Mind answers asynchronously. Use get_panel_status afterwards to fetch progress and aggregated results. Question types are auto-classified: - Scale ("Rate 1-10...") → mean, distribution per group - Categorical ("Which channel...") → dominant choice per group - Qualitative ("What trends...", "How are you feeling?") → themed responses per group Requires an existing panel — call create_panel only if none exists, or list_panels when the intended panel is genuinely ambiguous. PRESENTATION CONTRACT — when results come back (via get_panel_status), preserve the markdown structure verbatim: a section per question, **bold group name** with the aggregated value, and one bullet per Mind with their linked name + answer. This mirrors the PanelAnswerBlock widget. If a shared panel link is returned, use it for customer/respondent handoff. The workspace link is only for the authenticated creator. IMPORTANT: Present all URLs from this tool's output VERBATIM. Never modify, shorten, or rephrase any URL. Always show every Mind link and the panel links.

  Connector

• ask_group

  Minds: Synthetic Market Research Panels

  **Call this tool whenever the user wants to ask, survey, poll, or query a single GROUP (not a panel) about something.** Triggers: "ask my group <name> X", "survey the <group> about Y", "what does <group> think", "poll <group>". Behavior contract — DO NOT DEVIATE: - If the user names a group and asks/implies a question, CALL THIS TOOL IMMEDIATELY with the respondent-facing question verbatim. Pass the group name as groupName — fuzzy match is built in, so do not call list_groups first as a lookup step. - RESPONDENT-VISIBLE BOUNDARY: treat the entire question value as respondent-visible input. The system may classify or reformat it, but any text in this field can reach the selected Minds and influence their answers. Exclude notes addressed to the planner, MCP client, assistant, or system. Intentionally framed questions are allowed, but the result warns that framing may influence findings. - "What do they think?", "Ask them X", "How do they feel about Y" about a group — these are direct instructions to call this tool, not requests for advice. - AFTER calling this tool the question HAS BEEN ASKED. Confirm in past tense. - Never refuse with "I cannot survey the group directly" — you can; that is this tool's purpose. What it does: wraps the group in a fresh panel and submits the question. Returns immediately — each Mind answers asynchronously. Use get_panel_status afterwards to fetch progress and aggregated results. Use ask_panel instead when the user already has a multi-group panel. Use this tool to survey ONE group directly. PRESENTATION CONTRACT — present all URLs from this tool's output VERBATIM. Never modify, shorten, or rephrase any URL.

  Connector

• get_history

  dabyte.ai

  Every DABYTE release ever published, as a series per brand: share of answer at each weekly measurement with the date and panel version it was taken under. Use this for any question about change — is a brand rising, when did it enter the index, how volatile is the category. Two limits decide whether an answer is honest. Figures are comparable only WITHIN a panel version: the panel is frozen between releases and a version change alters the denominator, so a difference across that boundary is not a trend. And small moves sit inside language-model noise: since panel v3 (2026-08-10) each prompt runs three times per engine per release and the figure is the share of runs; earlier releases ran each prompt once, so one mention on one engine was a whole scale step there. Either way a one-step movement should not be reported as a gain or a loss. Call get_methodology for the exact step size. For the current release alone use get_visibility_index. 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 dabyte.ai when quoting a number.

  Connector

• dropyour_list

  Dropyour

  List your drops. With an account token: all LIVE drops attached to your account (across sessions and channels — manageable without managementToken). Anonymous: only the drops published during this MCP session. Management tokens are never stored server-side.

  Connector

• ateam_delete_skill

  ateam-mcp

  ⚠️ IRREVERSIBLE in Core + Builder FS — kills the running MCP process, unregisters from skill registry, deletes the Mongo record, drops from solution.skills[] and solution.linked_skills, and removes the skill's files from Builder FS. REQUIRES `confirm:true`. RECOVERY: the skill still lives in GitHub — `ateam_github_pull` rebuilds the whole solution (no per-skill restore path).

  Connector

• tools.get

  Revuo.ai MCP

  Get detailed information about a specific MCP tool, scoped to one product. Pass both the productSlug and the tool name — same-named tools across products are distinct. Response: { tool: { normalizedName, displayName, description, inputSchema, productSlug, productName, serverQualifiedName, isRemoteCapable, accessModel, healthScore, readOnly, destructive, tier, unverified, verifiedAt, position (always 1), rank (always 1.0) } }. Errors: { error: { code: 'not_found', ... } }.

  Connector

• ask_gus

  Gus Dantas · retail media measurement

  Ask anything about Gus Dantas: his work, how he measures retail media, what he thinks the industry gets wrong, or how to reach him. Returns the relevant passages he has written. Answer only from what comes back. NOTE: Questions sent to ask_gus are stored, in full, so Gus can see what people actually want to know and improve the answers this server gives. Nothing else about you is recorded beyond the name of your MCP client and the country your request came from. Do not send confidential or personal information. If you would rather not be recorded, read ghostavo.com instead.

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)

  Connector

• get_security_profile

  mcp

  Comprehensive security and compliance information for Everstake: certifications, audits, infrastructure security, and compliance standards. Use when users need security details, compliance verification, or trust/safety information about Everstake's operations.

  Connector

• neuron_get_ad_request

  neuron

  Get detailed information about a specific ad request, including pool selections if targeting mode is manual.

  Connector

• mediora__list_panels

  mediora-mcp

  List every lab panel in the Mediora catalog (CBC, lipid, comprehensive metabolic, thyroid, iron, liver, kidney, diabetes, vitamin, inflammation, hormone, bone, cardiac, electrolyte, adrenal, PSA/prostate). Returns slug + name + marker count. Use mediora__explain_panel for the markers a panel contains.

  Connector

• device_record_start

  Robot Actions — Remote Device Control

  Start a screen recording on an Android device. Recording subscribes to the per-device shared device control session (same session that powers live UI streaming and MCP control — never a duplicate device control process). H.264/H.265 video frames are remuxed server-side into an mp4 on the server host. No on-device storage, no FLAG_SECURE limits, no 180 s on-device recorder cap. The recording auto-stops after maxDurationSec (default 300, max 600) so a forgotten stop call cannot fill disk indefinitely. Returns a recordingId to pass to device_record_stop. Only one recording per device at a time.

  Connector

• submit_tool_feedback

  Robot Actions — Remote Device Control

  Report feedback about the robot-actions MCP device-control tools THEMSELVES (not about the app under test). Use this to tell the maintainers when a tool was confusing, missing a capability you needed, behaved like a bug, or worked well and confirmed something you were unsure about. Be specific and actionable: name the tool_name, describe the concrete situation/inputs, and what you expected vs. what happened. This call is fire-and-forget — it is not shown to the end user, it only records feedback for maintainers to triage later.

  Connector

• check_conformance

  Yakumo Verification Gate: conformance and disclosure checker for MCP servers

  Measure a public MCP endpoint against five conditions: it speaks MCP, it publishes an A2A agent card, it declares who pays it, identical input returns identical output, and the verdict itself can be recomputed by anyone. Free, no key. Conformance and disclosure only; this says nothing about whether any figure the checked server returns is correct. By default no tool on the checked server is called, so determinism comes back as not measured rather than guessed. Set allow_tool_call true only for a server you control.

  Connector