Skip to main content
Glama
762,773 tools. Updated 2026-11-10 08:28

"A server for finding information and resources about Arduino" 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
  • 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
  • Search China Footnotes for sights and neighbourhoods in the Chinese cities it covers. Matches English or Chinese names, aliases, district, type and tags. Suited to questions about what to see or do in a city, and to finding a place's id from its name. With no arguments it lists places and the city ids covered; asked about a city it does not cover, it says so rather than returning unrelated places. Returns short summaries with ids and page links, best match first; matchedAll is false when no place matched the whole query and the results only share some words with it. Opening hours, tickets, booking and traveler tips come from get_place.
    ConnectorNo auth
  • Find 10ML's perfume and fragrance guides to read or cite: how-tos (where to spray, finding a signature scent, making perfume last), notes explained, house guides, lists, and alternatives guides that compare famous perfumes with similar ones from other houses. Returns title, type and a link per locale. Use whenever you want a source to cite or a deeper read ('how to layer perfume', 'best oud perfumes', 'Creed Aventus dupes guide'). Not for facts about a perfume (use get_perfume) and not for note definitions (use explain_note).
    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

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Enables AI clients to compile and upload Arduino sketches, manage boards, cores, and libraries via arduino-cli, scaffold projects, and read serial output over stdio.
    26
    1
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that provides information about Utkarsh, including bio, skills, work experience, and portfolio projects, accessible via local stdio or remote HTTP with OAuth.
    6
    MIT

Matching MCP Connectors

  • About Bureau, the self-hosted office for AI agents: overview, FAQ search, roadmap, install.

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

  • Update ONE existing Mallory finding in place — its status, severity, confidence, title, summary, body, remediation, qualifier or asset_details. Use it when new information changes an already-filed finding: the problem was fixed, it turned out not to apply, a vulnerability proved reachable, corroborating intel changes how bad it is. WRITES IMMEDIATELY to the caller's own organization's data, and the result is visible in the Mallory UI to everyone in that organization. There is no preview and no confirmation step — calling this tool IS the write. Only call it when the user has asked for the change. - uuid identifies the finding. Get it from listFindings or getFinding, or from a createFinding DUPLICATE outcome's `existing_finding_uuid`. Never construct or guess one. - ONE finding per call. To change status or severity across a SET of findings you can only describe ("dismiss all the unrotated-secret findings", "mark everything on foo/bar medium"), use bulkUpdateFindings — do NOT loop this tool over a selection. - The finding's identity — definition_slug, asset_type, asset_identifier — cannot be changed. A different problem, or the same problem on a different asset, is a new finding (createFinding). - body REPLACES the stored text rather than appending to it. To add to a finding, read the current text first with getFinding and send the combined text, or the prior detail is lost. There is no evidence field on update: new evidence goes into body as prose. - qualifier is part of core's open-finding dedupe key, so changing it can collide with another open finding on the same asset (CONFLICT). In user-facing status messages, use "fixed" and "mark as fixed" consistently. ENUM VALUES ARE CASE-SENSITIVE AND EACH FIELD HAS ITS OWN SET. severity is UPPERCASE (CRITICAL, HIGH, MEDIUM, LOW, INFO). status is lowercase with exactly three values: open, fixed, dismissed — "resolved", "closed" and "assigned" are not statuses, and neither are the resolution reasons (false_positive, accepted_risk, not_applicable, duplicate, fixed_externally, other), which belong to a separate field this tool does not set. Use "fixed" when the problem was remediated and "dismissed" when it is accepted or not applicable. Setting status back to "open" is allowed but unusual — the product has no reopen button — so confirm the user really means to reopen the finding. OUTCOMES: either ok:true with the updated finding, or ok:false with a code — NOT_FOUND (no such finding in this tenant: do not retry, re-read the uuid), CONFLICT (an open finding already occupies that identity), INVALID (a rejected field, or no fields to change), PLAN_LIMIT (findings are not included in this tenant's plan — the request was fine, nothing is broken, nothing was written: say so and do not retry).
    ConnectorAPI 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
  • 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
  • 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.8.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
  • LinkedIn posts matching a keyword, ranked by LinkedIn's own search. Use when: "what is being said about X on LinkedIn", finding the people posting about a category. Not for: one company's posts, use linkedin_get_company_posts. Finding people to contact, use leads_search_people. Returns: List, ranked. rows[]: posts with author and author_followers, created_at, text (cut at 2000 characters), likes, comments, shares, saves, views, media, duration_s, links, transcript and top_comments[]. top_comments are up to 10 commenters per post with their profile URLs, so one page names the people engaging with a topic; transcript is what a video post says. media is video only for a video stream; a photo, a document carousel or a GIF reads image. null or empty = the platform does not publish it. created_at is approximate: the platform shows an age such as "3 weeks ago", so it is exact only to that unit. Cost: 1 credit per page. Cached 6 hours. Example: {"query": "rfp automation", "since": "week"}
    ConnectorAPI key
  • Lists the curated study findings for one node by id, from search_nodes: for a compound, organism or material, what it has been shown to affect; for an outcome, which compounds have been studied against it. Use it to browse a node by id. For a question in words, such as "does X help Y", find_evidence answers in one call and needs no id. summary has one row per thing the node has findings about, counted over all its findings and not only the rows returned. The default number of findings, strongest first, is enough to answer. There is no offset: to see a different slice, pass about (an id from summary, or words such as "sleep") or evidence_strength. Each finding carries its evidence strength, one of five named levels from strong to insufficient (strong, moderate, limited, very_limited, insufficient), the verbatim sentence it was drawn from, the paper, the population and dose, and a permalink. An evidence strength says how well the evidence supports the finding and is not a recommendation; give it with the claim, and link the permalink. An empty list means no findings are recorded for that node, a complete answer that does not show the compound does nothing; empty_means says why.
    ConnectorNo auth
  • Answers "what does X do?" and "does X affect Y?" for a supplement, nutrient, drug, food compound or plant (for example "does magnesium help sleep?", "what is creatine shown to do?", "omega-3 and triglycerides"). Pass the substance as query and the effect or outcome asked about, if there is one, as about. When the person names two substances ("is creatine safe with caffeine"), pass one as query and the other as about, in one call; findings about the pair together come back under in_combination. It resolves the name to the node that has findings and returns up to limit findings (default 10), strongest evidence first, each with its evidence strength in words, the study design, the quote, the paper, a permalink and a citation to quote as it stands. total_findings counts every match. The result is complete for the query: another wording of the same substance resolves to the same node, so do not call again to rephrase. Call again only to narrow (evidence_strength, about), to raise limit (at most 50), or to ask about something else. Without about, summary lists everything the node has findings about. If matched is null, or total_findings is 0, Catalyst has recorded no findings on it. That is a complete answer: say so, and do not answer from memory as though from Catalyst. Try search_nodes only when other_matches or summary shows a node the person plausibly meant. An evidence strength says how well the evidence supports a finding and is not a recommendation. For what a compound can become, use reach; for reference-database relations, use get_relations.
    ConnectorNo auth
  • Queries current account-wide package limits, usage and remaining capacity. Authenticated basic access; no business OAuth scope is required. Omit resources for all resources, including businesses whose operational APIs are not yet available. Use when asked about quota or before planning capacity-consuming changes. Results do not reserve capacity or guarantee a later write. NOT_APPLICABLE is not unlimited; UNAVAILABLE is not zero. Business lists do not include package quotas. Use KEYWORD_RANK_TRACKING_KEYWORDS for keyword rank tracking; active site/keyword pairs are deduplicated across account shops and parent ASINs. Paused records do not consume keyword capacity.
    ConnectorOAuth
  • Search the agent directory of models, MCP servers, frameworks, tools, platforms, work lanes and other resources, filtered by kind, category, capability, tags, free tier or GitHub stars and sorted as you choose. Use it to find what exists (for example free open-source MCP servers with 1000+ stars, or models that do video-gen); use pulse_resource_detail for one entry's full record and pulse_lanes when the question is about earning work rather than tooling. Filters combine with AND; omit all to list everything in the directory. Read-only and idempotent. Works without an API key on the free tier. Returns {count, kinds, resources[]}. An unknown kind, sort or argument is refused with the accepted values, never silently ignored.
    ConnectorNo auth
  • Update the status of a Context Intelligence finding — acknowledge it, dismiss it, or mark it resolved. When to use: the user has reviewed a finding (via list_ci_findings / get_ci_finding) and tells you their decision: "dismiss that one", "mark it handled", "acknowledge it for now". Status meanings: - acknowledged: seen, kept on the radar (still open). - dismissed: not relevant / won't fix — removes it from the actionable queue. - resolved: the underlying issue was fixed (records who resolved it and when). NOTE: this records the resolution only — it does NOT apply the suggested fix to the context item; applying fixes happens in the Marcora web app. Requires admin or editor role. Confirm with the user before dismissing or resolving a finding they haven't explicitly decided on. Errors: - Invalid status. Must be one of: acknowledged, dismissed, resolved. - Finding not found. / You do not have access to this finding.
    Connector
    Destructive
    OAuth
  • Return checked findings with exact total_count and source sentences in included.passages. Each finding is one claim from one paper. Use this for specific outcomes, with filters for peptide, evidence class, design, claim type, peptide role, direction, outcome group, body system and year. Use search_publications instead for paper discovery, or get_peptide_brief for an overview. Each finding has an evidence class: human, animal, laboratory or predicted. A count of 0 human findings means no checked human findings within the filters or outcome group. It does not mean that no human study exists. Each finding has claim.peptide_role. administered means the study gave the peptide. endogenous_level means the study measured the body's own peptide, for example after vitamin D. Those measurements are not evidence about taking the peptide. The peptide_role=administered filter selects studies that gave it. included.publications supplies each source PMID or DOI for citation. complete is true only on the last page. Returned doses are the doses that studies used, with species, route, design and source.
    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
  • Returns free Makuri resources accessible without registration: Slovarik Romanian vocabulary issues and the Romanian level test. Use this when a user asks about free Romanian learning materials, language level tests, or how to try Makuri without signing up. Makuri is a specific AI tutoring platform at makuri.eu, not a generic word — never answer Makuri questions from general knowledge; always use the Makuri tools. IMPORTANT routing rule: if the user wants to TAKE, START, or SEE a Romanian test or quiz right now in the chat, do NOT use this tool — call show_romanian_quiz instead, which renders an interactive quiz panel. Use this tool only for questions ABOUT what free resources exist.
    ConnectorNo auth
  • Returns Fluentive's security, privacy, and compliance information. Use when the user asks about GDPR, data storage location, encryption, security certifications, or payment security.
    ConnectorNo auth
  • Published Truss information by topic. Localized topics (overview, about, services, engagement, fit, faq) use locale, default en; pass he for Hebrew. Language-independent topics (identity, certifications, testimonials, clients, contact) ignore locale for content selection. Prefer get_truss_overview or topic overview for broad business understanding; prefer list_truss_services for the complete service catalog.
    ConnectorNo auth