Skip to main content
Glama
822,085 tools. Updated 2026-11-22 20:04

"A server for finding research information and resources" matching MCP tools:

  • Returns the plain-language meaning and step-by-step fix for one Malinois finding. Use it while helping the user fix an issue reported by scan_app, or when they ask what a finding means. Pass the rule_id exactly as scan_app returned it. Read-only, no network, instant.
    ConnectorNo auth
  • Maps only stable Tier1 finding identifiers to approved Tier1 services and public resources. Call after a Tier1 score or email-domain check. Do not submit prose, URLs, customer information, or invented identifiers. This tool performs no arbitrary fetching, makes no contact request, changes nothing, and stores nothing.
    ConnectorNo auth
  • Delete ONE AI package resource of a video in one language (eBook, mind map or quiz) — cannot be undone: its content, PDF, images and the published file are removed, also for legacy resources. Same as the dashboard's Remove. Refused while it is still generating (checked before deleting; if that check fails nothing is deleted). Other languages and resources stay. To remove a failed generation card use panda_delete_ai_workflow.
    Connector
    Destructive
    No auth
  • Uninstall a release and remove the resources it created, including volume data. Use it, not delete_resource, for anything install_template created. Provide the release `name`.
    Connector
    Destructive
    OAuth
  • Purpose: ChatGPT-connector-standard discovery search over OneQAZ's live surface — tools, resources, and the latest score-ranked combined signals across crypto / kr_stock / us_stock. Returns result ids consumable by the `fetch` tool. Triggers: ChatGPT connectors and Deep Research call this automatically for any user query routed to OneQAZ ("bitcoin signal", "prediction accuracy", "korean stocks today", ...). Other AI clients may use it as a keyword starting point when unsure which tool/resource to call. When to call: first step of connector-style discovery. MCP-native clients can instead browse tools/list + resources/list directly. Prerequisites: none. Next steps: pass any result id to `fetch` for the full document. Caveats: corpus is rebuilt at most every 10 minutes (tool/resource catalog + top-20 signals by |score| per market). Ticker / company-name queries (BTC, NVDA, 삼성전자) resolve to `signal:{market}:{symbol}` first; market words (S&P, KOSPI, crypto) surface that market's resources. Every result id is fetchable. Empty results come with a `note` explaining coverage. Output: {results: [{id, title, url}], disclaimer, is_investment_advice, data_classification} — flat envelope, OpenAI fixed shape. Output nature: Observed signal state computed from live market prices each cycle. signal_score is an internal ranking score, not a probability; bias is its sign. Context for the user's question, not investment advice.
    ConnectorNo auth
  • Search 500+ quantum computing job listings using natural language. Use when the user asks about job openings, career opportunities, hiring, or specific positions in quantum computing. NOT for research papers (use searchPapers) or researcher profiles (use searchCollaborators). Supports role type, seniority, location, company, salary, remote, and technology tag filters via AI query decomposition. Limitations: quantum computing jobs only, last 90 days, max 20 results. Promoted listings appear first (marked). After finding jobs, suggest getJobDetails for full info. Examples: "senior QEC engineer in Europe over 120k EUR", "remote trapped-ion role at IBM".
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Your saved places, trips and travel plans — see them, plan days, and add to them from your AI.

  • Search the FAA handbooks, advisory circulars and Airman Certification Standards (ACS) used for pilot training, and read any page in full with its figures, charts and tables. Every result links back to the exact page so answers can be cited. Free, public, no API key.

  • For research and citation lookups (deep research): free-text search of live Northern Cyprus (KKTC/TRNC) property listings on Evlek, in Turkish, English, Russian, German or Arabic. Returns matching listings as id/title/url, newest first (sale and rent as two groups when the query names neither). The answer language follows the language of the query. OpenAI deep-research compatible format, for research and citation clients. Use when: the caller only has a free-text query ("2+1 apartment in Kyrenia under 150000 pounds", "EVL-100464"). Not for: structured filters, paging or choosing the answer language.
    ConnectorNo auth
  • Use for general web research (company info, news, job portals). For LinkedIn profiles use search_linkedin_people; to read one company's own site use read_company_website. General-purpose Google search — returns organic results for any query. Unlike search_google_xray (LinkedIn-only), this searches the entire web. Useful for finding job postings on portals (jobs.cz, prace.cz, profesia.sk, indeed.com), company info, news, or any other web content. Results are NOT saved to contacts — use this for research and discovery. Capped at 4 calls per minute to protect the Serper/Google budget.
    ConnectorAPI key
  • Free-text search across every public resource family on The Holistic Care (blog articles, mindfulness games, free guided practices, research summaries, glossary terms, public PanchaVikas resources, and podcast episodes). Use this as the general entry point when a request doesn't clearly belong to one specific family — e.g. 'Find something about breathing for anxiety' or 'What has THC published about nondual awareness?'. `resource_type`, `category`, `audience`, `skill`, and `age` are applied as a post-filter over the text search results (the underlying search endpoint only supports free-text query natively), so a narrow combination of filters plus a rare query term can legitimately return few or zero results even if matching resources exist outside the searched batch — for a guaranteed, fully server-side filtered result within one resource family, prefer find_mindfulness_games, find_guided_practices, search_mindfulness_research, lookup_mindfulness_term, or find_podcast_episodes instead.
    ConnectorNo auth
  • Runs the full art-direction review of a project: collisions (frame by frame for films), angles, floating versus resting devices, text overlap, cropping and contrast, composition and color. Use it while building to see every finding, including warnings edit_scene saves anyway; use finish once at the end for the final check, and render_preview to look at the result. Read-only. Every finding has a severity and a fix with ready-to-send edit_scene ops. Returns the findings, errors first, and whether the scene passes.
    ConnectorAPI key
  • Search the web with SERP, AI synthesis, or both. Returns, by mode: serp the organic results (title, url, snippet, position, and the displayed link, date and sitelinks where Google shows them) with the page's People also ask questions, related searches, answer box, top stories and knowledge graph; ai a written answer with the URLs it cites; deep both. Use for current facts, news and finding pages. To read one page in full use scrape; for a report built from many sources use research. Cost: serp 1 credit, ai 2 credits, deep 3 credits, charged only when a call succeeds.
    ConnectorNo auth
  • Runs the full art-direction review of a project: collisions (frame by frame for films), angles, floating versus resting devices, text overlap, cropping and contrast, composition and color. Use it while building to see every finding, including warnings edit_scene saves anyway; use finish once at the end for the final check, and render_preview to look at the result. Read-only. Every finding has a severity and a fix with ready-to-send edit_scene ops. Returns the findings, errors first, and whether the scene passes.
    ConnectorAPI key
  • ACCOUNT REQUIRED (free, sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead, it works on every tier. Grounded multi-source research across Pipeworx's 2015 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call, this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 7,565 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx, it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass, so multi-step questions resolve in one call. Every finding carries a `hop` field and a citation_uri, a resolvable pipeworx:// record URI, present only when the source emits one that resources/read can actually serve, so a citation you get back is always fetchable. "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).
    ConnectorNo auth
  • Set the status of one alert of the isMalicious inbox (an id from list_alerts): ACKNOWLEDGED (seen; still listed by default), RESOLVED (handled; no longer listed by default) or OPEN (new again). Reversible: any status can be set again. A CVE alert (cve.finding) follows its vulnerability finding, for the whole organization: ACKNOWLEDGED acknowledges an open finding, RESOLVED marks a finding not yet closed as patched, OPEN reopens it, and every member's copy of the alert follows; the answer names the finding under `finding`, and the alert's status is the one the API returns (ack_finding sets NOT_AFFECTED or SNOOZED). Scope: the inbox of the user the key belongs to, which for an organization API key is the organization owner's; an alert of another inbox reads as not found. Costs no request of the monthly quota.
    ConnectorNo auth
  • Report whether one finding is fixed, according to yof's latest finished check; it does not run a new check. After a fix, run yof_check first, wait for it to finish, then call this; use yof_findings to get finding ids. Returns finding_id, rule, status, fixed, fixed_at, last_seen, last_check and why; a risk you accepted shows status accepted and fixed false.
    ConnectorNo auth
  • Check whether a change the user made THEMSELVES (not a one-click fix; for example after a Doktor AI fix draft) resolved one Service Doctor finding. Call only when the user explicitly asks to check a change they made: every call runs Service Doctor and records the result. Pass the finding code exactly as Service Doctor returned it and changedAtUtc, the UTC time the user started the change: within the last 7 days and not in the future. Ask the user when they made the change if they did not say; never invent it. Komuta waits for a successful deploy that started after changedAtUtc, then checks the finding and user impact (errors and p95 latency in the traffic after that deploy, compared with the 24 hours before the change when that had enough traffic). verification.configuration is always NotApplicable because Komuta did not make the change. summaryCode: Verified only when the deploy, the finding and user impact all pass; AwaitingDeployment (no deploy finished after the change yet); DeploymentFailed (the deploy after the change failed or is unhealthy); RiskStillPresent; RiskClosedImpactUnproven (finding gone but too little traffic, say plainly this is not a verification); ImpactRegressed; ObservingImpact (tell the user impactReadyAtUtc instead of suggesting to retry soon); RiskUnassessed (Komuta cannot prove from its recent decisions that this finding was present, for example cost findings, findings below Watch, or older ones; do not call it fixed). Returns: { findingCode, verification: { configuration, deployment, risk, impact, summaryCode, requestCount, minimumRequestCount, errorRatePercent, baselineErrorRatePercent, p95LatencyMs, baselineP95LatencyMs, observedFromUtc, observedToUtc, impactReadyAtUtc } }. Show user: what was confirmed and what was not, facet by facet, in plain words, and the change time you used; never call anything but Verified verified. Never show user: serviceId and other internal identifiers. Sends: the service id, the finding code and the change time; the backend runs Service Doctor and enforces access.
    ConnectorOAuth
  • Confirm or reject one Spec score finding, or take the mark back. A finding is what the scoring model said fails a check, about one item or, for consistency, a pair or group of requirements; projects_spec_score gives its id as `finding` on the check's `failing` items (items with the same id are one finding). `mark`: confirmed (it is real), rejected (it is not: it counts as passed and moves to the check's `dismissed`), or null. `note`: why, shown next to it. The mark holds until the item is judged again after an edit. Counts from the project itself (a missing attribute or link) have no id: they are facts. Quality attributes are set per characteristic with projects_spec_score_settings instead. Returns the score as it now stands. Uses no AI and no credits.
    ConnectorOAuth
  • Real-time web search via Tavily for current events, fact-checking, and research. Use search_depth='advanced' for complex queries (higher quality, higher cost) and topic='news' or 'finance' for headlines or market information. Use when: Choose when the task needs current, external, or factual information not available from on-chain or local data — e.g. news, prices, documentation, or fact-checking. Limitations: Returns web snippets, not raw page bodies; results depend on Tavily coverage. Advanced depth costs more. Not a substitute for on-chain tools like get_token_price. Alternatives: get_token_price, http_fetch
    ConnectorNo auth
  • Read a single research author by author UUID. Use this tool when a user wants profile details for a specific research author returned by another research tool. The response includes author metadata, biography fields, profile URL, and visible sectors associated with the author. Missing, inactive, non-author, and hidden-sector-only authors return a generic not-found error.
    ConnectorNo auth
  • Get one judge's source-attributed birth details, education, and professional and judicial careers using the canonical profile URL from find_judges. Use for biographical questions rather than courtroom practice. Birth information is year-only for judicial privacy; age is null. Preserves provenance and source check dates. Missing biography fields mean unavailable information, not a failed lookup.
    ConnectorNo auth
  • Verdicts from the overnight factor search on YOUR namespace — including the rejections. The rejections are returned deliberately. A research log that keeps only the winners is the highlight reel overfitting lives in, and the acceptance RATE is the number that tells you whether the anti-overfitting gate is doing its job: a search that accepts most of what it tries has a broken gate, not a talent for finding alpha. Every verdict carries the trial count it was judged against, so it can be re-checked. `coverage.missing` names hypotheses that were proposed but never judged because a cost ceiling was reached — those are UNTESTED, not rejected. An accepted factor is a FINDING with a run_id, not an allocation. Nothing here trades. Args: limit: how many verdicts to return, newest first (max 100).
    ConnectorNo auth