Skip to main content
Glama
803,485 tools. Updated 2026-11-19 06:19

"A server for finding information on Biology and Pharmaceutical topics" 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
  • Apply a post-hoc triage verdict to a finding that was previously recorded via record_finding. Used by the /reply-to-code-review flow to persist whether a finding is TRUE / FALSE / UNCERTAIN and the FIX / DEFER / IGNORE action taken. The finding is located only by the exact `finding_id` returned by list_pr_findings, on ANY lifecycle status (open, fixed, or dismissed — so verdicts still apply after a PR is merged and findings were swept to dismissed). Only findings recorded into the data layer (the aictrl-dev MCP path) can receive a verdict. Idempotent: re-applying overwrites the prior verdict. A not_found response is an application error; call list_pr_findings to refresh stale IDs and do not treat the write as successful. `judged_at_sha` is required: send the full 40-hex commit SHA of the code you actually read. A SHA that is neither the review SHA nor a later commit of the same PR is rejected with validation_error. `reasoning` is required too (#5364): a verdict whose reasoning cannot be audited later is not worth storing. Each write appends to the finding's judgment history; a re-judge from the same run at the same commit updates that run's own row rather than appending a duplicate. A FALSE verdict on an OPEN finding of severity MINOR or NIT (medium/low/info) also dismisses it as a false positive, with your `reason` as the note; on MAJOR or BLOCKER (high/critical) it stays a suggestion a person confirms. The result reports `autoDismissed` (and `autoDismissReason` when false). A dismissal is not reopened by this tool; a person can restore the finding from the pull-request page.
    Connector
    Destructive
    API key
  • List security/safety findings for your workspace, most recent first. Optionally filter by status, target model, minimum severity, or a specific run. Returns a compact summary; call get_finding for the repro detail of any one finding. On a plan that withholds a finding's proof, category reads '[redacted]' and get_finding returns the same — the finding and its severity are real, the evidence is withheld. Paginated: 200 findings per page (max 200). The result carries total_matched and, when there is more, next_cursor: pass it back as 'cursor' with the same filters (it is bound to them) to read the next page, until it is absent.
    ConnectorOAuth
  • Get Lenny Zeltser's expert CTI writing guidelines. Topics include tone, words, structure, executive_summary, voice, articles, summary, brief (one-page brief section guidance), handoffs (cross-server routing), methodology (the three subsections), fields (per-field guidance), and CTI-specific topics: attribution (full Six Signals prose), confidence (ICD-203 ladder), pyramid_of_pain, six_signals (signals table only), and anti_patterns. The general writing topics (tone/words/structure/executive_summary) now defer to `get_security_writing_guidelines` for the canonical Five Elements rules; CTI-specific content lives in the other topics. Pair the 'fields' topic with field_id for single-field guidance. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.
    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
  • Search the PUBLIC Awareness knowledge graph — 1,000+ sourced scientific papers. Use this when the user (especially a researcher or a research agent) asks for peer-reviewed findings: "latest evidence on X", "highly-cited papers about Y", "what does the literature say about Z". This is NOT a memory tool — it does not read the user's private memory, and it needs no per-user API key, so it works even when Awareness memory is not configured (the MCP connection itself still needs its own token). Coverage: condensed-matter, quantum-information, materials, machine-learning, renewable-energy, chemistry, biology, medicine, neuroscience, computer-science (2022-2026, cited >= 50), plus a business supply/demand domain. What comes back (anonymous preview mode): title, snippet (preview), confidence, source_ref (DOI), citation_count, domain/topic, and a detail page URL. Full content is NOT in the preview — tell the user it is paid retrieval via POST /api/v1/public/retrieve with an API key (see https://awareness.market/en/knowledge for the KaaS product). Args: query: Natural-language research question or keywords (2-1000 chars). domain: "science" (default) or "business". topic: Optional sub-topic slug, e.g. "medicine", "condensed-matter", "supply-chain". Empty = search all topics in the domain. top_k: Max results, 1-20 (default 5; anonymous callers are capped at 3). include_graph: When true, also return same-topic related items. Returns: {"results": [{id, title, snippet, confidence, source_ref, citation_count, domain, topic, url}], "related": [...], "total": int, "mode": str} `mode` is "preview" (anonymous) or "full" (authenticated).
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides AI agents with real-time trending topics from Weibo, Baidu, Zhihu, Google Trends, and HackerNews/StackExchange community intel, enabling content and marketing agents to stay aware of current conversations before creating content.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables Claude Desktop, Claude Code, and autonomous AI agents to route messages into Telegram supergroup forum threads and manage topics by creating, editing, closing, reopening, and listing them with tag-to-thread mapping.
    1
    MIT

Matching MCP Connectors

  • The topics in a set of documents in one call, with each document's topic mixture. Nothing stored.

  • Trending topics from Weibo, Baidu, Zhihu & Google Trends for content and market research.

  • Create an accepted action from one Audit finding, as Create action on the Audit page does. Pass auditRunId and findingId from devtune_get_audit_findings; title defaults to the finding's remediation summary. Requires actions.write and a member who can manage actions. A finding already linked to an open action returns that action's actionId with created false, so a retry or a later audit of the same finding never makes a second one; its finding evidence is refreshed, and its title changes only when title is sent, while its description stays as stored. A refusal is a 409 and nothing is written: stale_audit_run (a newer completed audit of the same site exists, or the finding's action was already refreshed from a newer audit; retry with details.latestAuditRunId after reading its findings), finding_dismissed (restore it with devtune_restore_audit_finding), page_locked (an affected page is locked), acknowledgment_required (an affected page is high-stakes; retry with acknowledgeHighStakes true once a human has confirmed the change), action_not_open (the finding's action is archived, completed or out of the queue; details.actionId names it, restore or reopen it with devtune_change_action_status), retrieval_restriction_acknowledged (every affected page is acknowledged as an intentional restriction; reconsider them with devtune_reconsider_retrieval_restriction), or a crawler-access finding whose audit holds no retrieval evidence. Archive or restore the action with devtune_change_action_status.
    Connector
    Destructive
    API key
  • Remember something, with its sources and its knowledge time. Nothing is ever overwritten: saving a `factor_def` or `watchlist` under an existing key SUPERSEDES the previous version (both rows survive, so "what did I believe in June?" stays answerable), and saving identical content twice is a no-op rather than a duplicate. Args: kind: 'query' | 'factor_def' | 'watchlist' | 'finding' | 'note'. content: the thing to remember, as an object. key: the stable name — REQUIRED for 'factor_def' and 'watchlist' (that is what makes a definition reusable next session instead of re-invented). as_of: the knowledge time this memory is about. Recall can bound on it, which is what keeps a memory from leaking the future into a point-in-time question. source_query_ids: the `twmd_q_…` ids behind this. REQUIRED for 'finding' — a conclusion that cannot point at its data is not evidence, and will be refused. agent_id: optional label for which of your agents wrote this.
    ConnectorNo auth
  • Google Trends related topics for a keyword. Returns the topics and named entities associated with a keyword in a given country, as top topics scored 0-100 relative to each other and rising topics with percentage growth, each carrying its entity type. Google Trends topic discovery for market research and content planning. [$0.03/call]. Params — keyword: the search term; geo: ISO-3166 alpha-2 country code, e.g. US, GB, DE, JP (213 countries supported); timeframe: time window. Each response reports its own bucket size in `granularity`: past_30_days and past_90_days return a daily series, past_12_months and past_5_years weekly, windows under a day hourly (2004_present|past_12_months|past_30_days|past_4_hours|past_5_years|past_7_days|past_90_days|past_day|past_hour) Example params: {'keyword': 'bitcoin', 'geo': 'US'}
    ConnectorNo auth
  • Return curated information about Bad Kleinkirchheim and the house for a topic. Use for "what can we do there?" and house questions: house rules and services (self-catering, no breakfast, bread-roll service, no pets, baby cot/high chair on request, chip access), skiing (winter), hiking, biking and lakes (summer), thermal spas and the in-house sauna (wellness), golf incl. the free green fee and tee-time booking, families, workation, arrival. The Kärnten Card (summer only) and the free green fee are explained exactly. Not for prices or availability (check_availability) and not for apartment facts (get_apartment_details). Behaviour: read-only, static curated content from the property (no web search), instant; topics 'house' and 'wellness' also list the property's official house photos (sauna, steam bath, relaxation room …) — to show them, call render_house_photos, never a web image search (other businesses share the 'Prägant' name). Returns text plus structuredContent.topics (topic, lines), photos (kind, url, caption) and contact details.
    ConnectorNo auth
  • Paid ($0.008 USDC). List lookup for one address on any chain against OFAC SDN digital-currency entries, community scam-address blocklists and the Blockchain Fraud case registry. Use as a fast, cheap first gate on a counterparty address. For balances plus sanctions plus a summary on an EVM address use genesis402_wallet_brief. Returns whether any list matched, and for every list consulted its dataset name, fetch URL and entry count, plus an evidence hash. A hit means the address appears on a published list; absence from every list is not a clearance. Not a compliance decision, not a finding about any person, not legal advice. Payment: call once without payment_signature to get the exact price quote (nothing is charged or signed), then call again with the signed payment to receive the result and settlement details.
    ConnectorNo auth
  • explain_finding({"gap_id":"rls_disabled"}) Use after a check returns a finding id, such as rls_disabled or env_var_drift, to understand and fix that VibeRaven 1.10.0 finding. Returns detection scope, impact, fix guidance and coverage limits quoted from viberaven.dev with source links. Unknown ids return found: false and known ids. For a raw error without a finding id, use search_guides. Limits: explains published rules only; does not read your repo, database or Vercel project.
    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
  • ALL EVENT LOGS in one or more Arbitrum (arb, ARB, Arbitrum One, L2) transactions, including decoded arguments plus raw topics and data. Use after arbitrum_find_events identifies a transaction, or whenever a tx receipt's complete event payload is needed. NOT the value moved in a transaction → use arbitrum_tx_transfers. Accepts up to 50 transaction hashes separated by "|". `Parsed=0` means no ABI matched: Event, Signature and Arguments can then be empty, but Topic0, Topics and Data remain usable. Arguments are named objects with Name, Type, string Value and Indexed; integer values are decimal strings to avoid JSON-number precision loss; use raw Topics/Data for values wider than the decoded numeric fields. Argument names come from one known ABI for the Signature and can be another contract's wording - Topics and Data are the log's own. By default, reverted call-frame logs, removed logs and failed transactions are excluded; set only_successful=0 to inspect them with the returned status fields.
    ConnectorOAuth
  • ALL EVENT LOGS in one or more Arc (arc, ARC, Arc Network, Circle Arc) transactions, including decoded arguments plus raw topics and data. Use after arc_find_events identifies a transaction, or whenever a tx receipt's complete event payload is needed. Accepts up to 50 transaction hashes separated by "|". `Parsed=0` means no ABI matched: Event, Signature and Arguments can then be empty, but Topic0, Topics and Data remain usable. NOT the value moved in a transaction → use arc_tx_transfers. Arguments are named objects with Name, Type, string Value and Indexed; integer values are decimal strings to avoid JSON-number precision loss; use raw Topics/Data for values wider than the decoded numeric fields. Argument names come from one known ABI for the Signature and can be another contract's wording - Topics and Data are the log's own. By default, reverted call-frame logs, removed logs and failed transactions are excluded; set only_successful=0 to inspect them with the returned status fields.
    ConnectorOAuth
  • ALL EVENT LOGS in one or more Base (base, L2, Coinbase L2) transactions, including decoded arguments plus raw topics and data. Use after base_find_events identifies a transaction, or whenever a tx receipt's complete event payload is needed. Accepts up to 50 transaction hashes separated by "|". `Parsed=0` means no ABI matched: Event, Signature and Arguments can then be empty, but Topic0, Topics and Data remain usable. NOT the value moved in a transaction → use base_tx_transfers. Arguments are named objects with Name, Type, string Value and Indexed; integer values are decimal strings to avoid JSON-number precision loss; use raw Topics/Data for values wider than the decoded numeric fields. Argument names come from one known ABI for the Signature and can be another contract's wording - Topics and Data are the log's own. By default, reverted call-frame logs, removed logs and failed transactions are excluded; set only_successful=0 to inspect them with the returned status fields.
    ConnectorOAuth
  • ALL EVENT LOGS in one or more Ethereum (eth, ETH, mainnet, L1) transactions, including decoded arguments plus raw topics and data. Use after eth_find_events identifies a transaction, or whenever a tx receipt's complete event payload is needed. Accepts up to 50 transaction hashes separated by "|". `Parsed=0` means no ABI matched: Event, Signature and Arguments can then be empty, but Topic0, Topics and Data remain usable. NOT the value moved in a transaction → use eth_tx_transfers. Arguments are named objects with Name, Type, string Value and Indexed; integer values are decimal strings to avoid JSON-number precision loss; use raw Topics/Data for values wider than the decoded numeric fields. Argument names come from one known ABI for the Signature and can be another contract's wording - Topics and Data are the log's own. By default, reverted call-frame logs, removed logs and failed transactions are excluded; set only_successful=0 to inspect them, using TxSuccess / CallSuccess / Reverted / Removed to interpret each row.
    ConnectorOAuth
  • ALL EVENT LOGS in one or more Polygon (matic, POL, MATIC, PoS) transactions, including decoded arguments plus raw topics and data. Use after matic_find_events identifies a transaction, or whenever a tx receipt's complete event payload is needed. NOT the value moved in a transaction → use matic_tx_transfers. Accepts up to 50 transaction hashes separated by "|". `Parsed=0` means no ABI matched: Event, Signature and Arguments can then be empty, but Topic0, Topics and Data remain usable. Arguments are named objects with Name, Type, string Value and Indexed; integer values are decimal strings to avoid JSON-number precision loss; use raw Topics/Data for values wider than the decoded numeric fields. Argument names come from one known ABI for the Signature and can be another contract's wording - Topics and Data are the log's own. By default, reverted call-frame logs, removed logs and failed transactions are excluded; set only_successful=0 to inspect them with the returned status fields.
    ConnectorOAuth
  • ALL EVENT LOGS in one or more Robinhood (robinhood, rh, Robinhood Chain) transactions, including decoded arguments plus raw topics and data. Use after robinhood_find_events identifies a transaction, or whenever a tx receipt's complete event payload is needed. Accepts up to 50 transaction hashes separated by "|". NOT the value moved in a transaction → use robinhood_tx_transfers. `Parsed=0` means no ABI matched: Event, Signature and Arguments can then be empty, but Topic0, Topics and Data remain usable. Arguments are named objects with Name, Type, string Value and Indexed; integers are decimal strings to avoid JSON-number precision loss; use raw Topics/Data for values wider than the decoded numeric fields. Argument names come from one known ABI for the Signature and can be another contract's wording - Topics and Data are the log's own. By default, reverted call-frame logs, removed logs and failed transactions are excluded; set only_successful=0 to inspect them with the returned status fields.
    ConnectorOAuth
  • ALL EVENT LOGS in one or more Tron (trx, TRX, TRON) transactions, including decoded arguments plus raw topics and data. Use after tron_find_events identifies a transaction, or whenever a transaction's complete event payload is needed. Accepts up to 50 transaction hashes separated by "|". `Parsed=0` means no ABI matched: Event, Signature and Arguments can then be empty, but Topic0, Topics and Data remain usable. NOT the value moved in a transaction → use tron_tx_transfers. Address arguments are returned as Tron base58 addresses; integers remain decimal strings to avoid JSON-number precision loss; use raw Topics/Data for values wider than the decoded numeric fields. By default, reverted call-frame logs, removed logs and failed transactions are excluded; set only_successful=0 to inspect them with the returned status fields. Unlike EVM chains, LogIndex is populated on Tron and gives the event's ordinal in the whole transaction.
    ConnectorOAuth
  • 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