Skip to main content
Glama
811,405 tools. Updated 2026-11-20 13:24

"Arch Linux package management tool with Wiki access and safety checks" matching MCP tools:

  • Adds one check to a finished research and returns the id of the new child research. Use it when the scan skipped a stage, when a person asks about one phrase in particular, or to rebuild the report after new checks. A niche scan already runs the usual checks by itself, so this tool is for what is missing. Checks added this way are free: they do not spend researches of the plan. Checks of a demand research (`kind`): - `competitors`: who holds the search results for a phrase of the research; pass the phrase in `phrase`. - `dynamics`: two years of demand history. - `appstore`: App Store apps for the phrase with ratings and freshness. - `wiki`, `radar`, `youtube`: public interest and community signals. - `paid`: paid search for the phrase and its strongest candidates: volume, advertiser competition, cost per click. - `insight`: a summary of the findings written by the language model. - `report`: the final niche report, written anew from the current data; needs a finished niche scan. Checks of a child research: - `fingerprint`: product sites found by a competitors check, with pricing and app links; the parent is that competitors check. - `reviews`: recent App Store reviews of the leaders; the parent is an App Store research. - `insight` also accepts a competitors check as the parent. The parent must be completed and belong to the account. The check runs in the background: poll get_research with the returned `id` every 20-30 seconds until `status` is `completed`. `insight` and `report` are rebuilt at most once an hour.
    ConnectorNo auth
  • Find RS3 Wiki sources for items, NPCs/monsters, quests and guides. Use get_wiki_page_content for reviewed text/page references, lookup_item for GE identities or get_item_details for catalogue records. query accepts raw Wiki syntax; the server URL-encodes it. "Abyssal demon" "drop" requires both phrases; intitle:"Cook's Assistant" focuses titles. prefix:Category:Weapons selects Wiki categories instead of articles. limit caps one relevance-ranked set, not an offset. No continuation cursor exists: refine the query for different matches. No matches returns an empty set; invalid queries or API failures return errors. Public reads require no credentials and are uncached. The shared HTTP budget defaults to 60 requests/IP/minute; honor 429 Retry-After.
    ConnectorNo auth
  • Arm (enabled: true) or disarm (enabled: false) auto-merge on one PR: it merges by itself through the full gated merge chain (CI, required checks, branch protection, CODEOWNERS, risk) once CI and every required check are green and no reviewer with write access has changes requested. Stays armed while anything is pending; `last_attempt.reason` says what it waits for. Arming is also the merge train's consent: on a repository with the train on, the train merges only armed PRs, so disarming holds the PR from it (an explicit merjax_merge_pr still merges). Requires write access and 'repo' scope. merge_method: 'merge' only. Returns {number, auto_merge}.
    ConnectorOAuth
  • Retrieve The Hill Kinabalu’s official public wedding venue and 2026/2027 package information, including capacity, event sizes, starting package prices, key inclusions, add-ons without prices, payment structures, and enquiry links. Use this when someone asks about weddings, wedding packages, the event venue, guest capacity, package pricing, or how to enquire. This tool does not check date availability or submit an enquiry.
    ConnectorNo auth
  • 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 management token's own grant (`read` is always included), expiry is mandatory (1–90 days, default 30, never "never"), and the minted management token (being project-scoped) can never mint management tokens itself. `spend` is human-granted only: no management token, of any scope, can mint one carrying it. Mint a spend-scoped token from the project's panel instead. Requires an ACCOUNT-scoped management token and the `config` scope. Returns the plaintext exactly once; only its hash is stored.
    ConnectorNo auth
  • Perform a Linux package vulnerability audit using SecDB. ## What this tool does Analyzes the installed packages of a Linux system-identified by OS and OS version-and returns vulnerability information plus a Markdown summary. The audit results are based exclusively on the package list provided by the user. ## When to use this tool Use this tool when the user wants to determine: - whether installed packages contain known vulnerabilities - whether a host, VM, container, or base image is affected by security advisories - which packages require patching or upgrading If the user does not know the valid values for `os` or `version`, first call the `linux_os` tool to retrieve the exact supported combinations. ## Inputs - **os**: Linux distribution identifier supported by SecDB (use `linux_os` to obtain allowed values). - **version**: OS version or codename corresponding to the selected distribution, exactly as returned by `linux_os` (for example `focal`, not `20.04`). Any other value is rejected with the list of supported values. - **packages**: list of installed packages, **one per line**, generated using the appropriate system command: ### For RPM-based distributions (RHEL, CentOS, Rocky, Alma, SUSE) rpm -qa --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' ### For DEB-based distributions (Ubuntu, Debian) dpkg-query -W -f='${Package} ${Version} ${Architecture}\n' ### For Alpine Linux apk list -I ### For Slackware ls -1 /var/log/packages/ The raw output of these commands can be passed directly as the `packages` input (one package per line). ... python3 3.12.3-0ubuntu2.1 amd64 systemd 255.4-1ubuntu8.10 amd64 tmux 3.4-1ubuntu0.1 amd64 ... ## Outputs - **report**: structured objects describing the advisories affecting the audited packages. Packages without known vulnerabilities are not listed. - **summary**: Markdown summary including vulnerable packages, total CVEs, and severity breakdown. ## LLM usage guidelines - Never guess whether a package is vulnerable-always call this tool for Linux audits. - If `os` or `version` is unclear or missing, call `linux_os` and ask the user to choose a valid combination. - Normalize the package list to “one entry per line” if the user provides unstructured output. - The `summary` is already Markdown and can be shown directly. - Use `report` when deeper technical analysis is required.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    Arch MCP provides three main capabilities: * Access to Arch Wiki, AUR packages, official repos, and installed packages * Search, analyze, and securely install packages with built-in 50+ safety checks * Guided workflows for troubleshooting, security audits, and dependency analysis
    22
    62
    GPL 3.0
  • A
    license
    A
    quality
    B
    maintenance
    Detects breaking changes in a TypeScript library's public API and recommends the semver bump, comparing two npm releases, git refs or a working tree. Each finding is graded proven or review-only.
    2
    2
    341 npm
    1
    MIT

Matching MCP Connectors

  • 20 DevOps/Linux MCP tools: Docker, systemd, seccomp, K8s, Terraform, Nginx, CI, cron, bash.

  • Knowledge base for AI agents: search, read, tasks; write, correct, report outcomes via /mcp/write.

  • Analyze text for writing style issues: weasel words, passive voice, duplicate words, long sentences, nominalizations, hedging, filler adverbs, and research-cited AI tells. Read-only and stateless — text is analyzed in memory on the hosted server and never stored. Returns a plain-text report with each issue's line and column, the matched text, surrounding context, and the reason for AI tells; texts over 100,000 characters return an error message. This hosted server has no filesystem access — the wsc-mcp npm package adds a check_file tool for local files. It only reports issues — to auto-remove duplicate words, follow up with fix_duplicates.
    ConnectorNo auth
  • Map the full dependency tree of an npm package and identify CRITICAL supply chain risks at every level. Unlike auditing a flat list of packages, this tool traverses the dependency graph — showing not just your direct dependencies but also what your dependencies depend on. Hidden CRITICAL packages (sole publisher + >10M weekly downloads) often lurk 1-2 levels deep. Risk flags: - CRITICAL: single npm publisher + >10M weekly downloads — sole point of failure for a massive attack surface - HIGH: sole publisher + >1M/wk, OR new package (<1yr) with high adoption - WARN: no release in 12+ months (potential abandonware) depth=1 (default): root package + all direct dependencies depth=2: also traverses one more level for any CRITICAL/HIGH direct deps (reveals hidden exposure) Examples: - audit_dependency_tree("express") — see all of Express's deps and their risk scores - audit_dependency_tree("langchain", 2) — reveal transitive CRITICAL deps 2 levels deep - audit_dependency_tree("@anthropic-ai/sdk") — audit Anthropic SDK full tree Use this when someone asks: - "What am I really depending on?" - "Are my dependencies' dependencies safe?" - "Show me the full supply chain risk for package X"
    ConnectorNo auth
  • List the full eDiscovery Decoder MCP surface — every tool, prompt, and resource, plus the suggested demo flow and safety boundaries — with an example prompt for each. Call this first when you are unsure which tool fits the user's question, or when tool-search shows only a partial list.
    ConnectorNo auth
  • Analyze text for writing style issues: weasel words, passive voice, duplicate words, long sentences, nominalizations, hedging, filler adverbs, and research-cited AI tells. Read-only and stateless — text is analyzed in memory on the hosted server and never stored. Returns a plain-text report with each issue's line and column, the matched text, surrounding context, and the reason for AI tells; texts over 100,000 characters return an error message. This hosted server has no filesystem access — the wsc-mcp npm package adds a check_file tool for local files. It only reports issues — to auto-remove duplicate words, follow up with fix_duplicates.
    ConnectorNo auth
  • Draft and publish a news article. Open to anyone with a Datronis account — the personal access token is for rate-limiting and audit, not permission-gating. Always drafted in English first; an automated safety classifier must return "green" (not political, not likely to be seen as controversial or divisive) before the article goes live. A "flagged" result creates the article unpublished and returns the reasons — use resubmit_news with revised content to try again; there is no way to force-publish a flagged article. Publishes English-only unless target_locales is given.
    ConnectorNo auth
  • Return the durable work queue for Research Bounties created by this exact Bearer agent key. Call after funding, whenever the agent starts or resumes, when the controller receives a RigorLoop alert, or at an operator-approved interval while work remains active. Each item includes funding, applications, assignment, result state, and the next recommended tool call. Do not assume email access; stop routine checks after completion or cancellation.
    ConnectorNo auth
  • List all toolsets (tool groups) with slug, tool count and whether they are visible in this session. Core toolsets are always visible; enable others with enable_toolset. Full-access API keys see every tool; scoped keys and OAuth sessions automatically see every tool their scopes or role allow. Hidden tools stay callable — enabling only affects what tools/list advertises.
    ConnectorAPI key
  • PAID. Obtain a signed endpoint observation you can retain and share. First call with the exact URL, TTL and optional task audience for a quote. Retry through this SAME MCP tool with x402/payment request metadata, or the schema-visible x402_payment argument when metadata is unavailable. No separate HTTP connection, account or human checkout is needed for x402. A funded api_key instead spends sandbox credits, never money. Returns evidence v2 with exact requested URL/audience binding, checksum, salted observation commitment, Merkle path and signed checkpoint. Complete issuance precedes charging; an issuance failure never bills. Same completed x402 purchase recovers its saved result without new probes or another charge. Sandbox credit calls are separate purchases, not idempotent payment retries. Verify offline with /sdk/agentguild_verify.py or .mjs, or use the free guild_evidence_verify tool. An issuer signature proves origin/integrity, not observation truth, independent time or endpoint safety. Free guild_preflight remains available for live checks without the portable bundle.
    ConnectorNo auth
  • Connect the user's existing POKEKA account or check its current access permissions. Use when the user explicitly asks to connect, sign in, or check their POKEKA account access (连接账号、登录、查看账号权限). Requires POKEKA OAuth; if not connected, return the account-linking challenge and retry after authorization. Public card and market queries do not require this tool. Returns the existing access tier and connection-management link, never credentials or personal identifiers. Does not purchase or change a plan. Calls update token activity and may record internal usage statistics.
    ConnectorNo auth
  • Inspect the authenticated account's live-data grants, rate limit and feed health. Call before consuming data or after an access error. Bearer key required; no data credits consumed. Returns unexpired grants (remaining=-1 means Unlimited), http_rate_limit shared across account keys, and source health. An empty grants list means no unexpired package; a grant can still have zero credits. Key-specific budgets are managed in the dashboard and are not in this response. Use get_trading_usage for swap volume, get_trading_config for swap policy, and get_payment_instructions to create a data-package invoice.
    ConnectorAPI key
  • Inspect the authenticated account's live-data grants, rate limit and feed health. Call before consuming data or after an access error. Bearer key required; no data credits consumed. Returns unexpired grants (remaining=-1 means Unlimited), http_rate_limit shared across account keys, and source health. An empty grants list means no unexpired package; a grant can still have zero credits. Key-specific budgets are managed in the dashboard and are not in this response. Use get_trading_usage for swap volume, get_trading_config for swap policy, and get_payment_instructions to create a data-package invoice.
    ConnectorNo auth
  • List the public MCP servers whose tools apiwatch checks every 6 hours (tools/list only, no login, no tool calls), with each one's status (answering, needs a login, not reachable), tool count, last check and last observed change. Use it to see which servers mcp_server_changes can answer about. Returns no tool descriptions.
    ConnectorNo auth
  • Create an outgoing webhook subscription for the current workspace. Every delivery is signed with HMAC-SHA256 of the raw body using the webhook secret, sent as `X-Webhook-Signature-256: sha256=<hex>`. Pass your own `secret`, or omit it and this tool generates one and returns it as `secret` in the result. SAVE THE SECRET IMMEDIATELY: pm_get_webhook / pm_list_webhooks never return it; to rotate it, pass a new `secret` to pm_update_webhook. Event types: Project Management events are dash-cased (e.g. "task-created", "task-status-changed", "comment-added"); wiki (Codexum) events are dotted and start with "wiki." (e.g. "wiki.page.published", "wiki.comment.added"); feature-request (Roadmarq) events start with "feedback." (e.g. "feedback.request.created", "feedback.bug.created"). Call pm_list_webhook_event_types for the full list with each type's product and allowed scopes. An unscoped webhook may mix products. Optionally narrow delivery to one entity with scopeType plus scopeEntityIdentifier: SPACE / FOLDER / TASK_LIST / TASK (identifier), WIKI_SPACE (space key), WIKI_PAGE (page id; covers its descendants), FEEDBACK_BOARD (board slug or id; stored and listed as the board UUID), FEEDBACK_REQUEST / FEEDBACK_BUG (short key such as "FR-12", or id); omit both for workspace-wide delivery. A scoped webhook may only list event types of its scope's product. Wiki and feature-request events need the API key to hold that product's read scope, and every delivery is re-checked: an event is sent only while the webhook creator can still see the item. Security bugs are not delivered to webhooks created with an API key: includeSecurityBugs can only be turned on by a workspace admin signed in as a person. Envelope: {version, id, type, timestamp, workspaceIdentifier, source ("pm" | "codexum" | "roadmarq"), eventId (stable across webhooks and replays; use it to de-duplicate), data}. Payloads are thin: no content bodies, comment text or emails. Retries fire at +0s / +1min / +5min (3 attempts total) and treat both 4xx and 5xx as failures. The URL must be publicly reachable: Dutify refuses private, loopback, link-local, CGNAT and IPv6 ULA addresses, localhost, bare hostnames and *.svc / *.cluster.local names (400 WEBHOOK_URL_NOT_ALLOWED) at create, update and resume, and re-checks it on every attempt. Redirects are not followed; http:// is accepted for public addresses. API-key scope: `webhooks:write`.
    ConnectorNo auth
  • Create an outgoing webhook subscription for the current workspace. Every delivery is signed with HMAC-SHA256 of the raw body using the webhook secret, sent as `X-Webhook-Signature-256: sha256=<hex>`. Pass your own `secret`, or omit it and this tool generates one and returns it as `secret` in the result. SAVE THE SECRET IMMEDIATELY: pm_get_webhook / pm_list_webhooks never return it; to rotate it, pass a new `secret` to pm_update_webhook. Event types: Project Management events are dash-cased (e.g. "task-created", "task-status-changed", "comment-added"); wiki (Codexum) events are dotted and start with "wiki." (e.g. "wiki.page.published", "wiki.comment.added"); feature-request (Roadmarq) events start with "feedback." (e.g. "feedback.request.created", "feedback.bug.created"). Call pm_list_webhook_event_types for the full list with each type's product and allowed scopes. An unscoped webhook may mix products. Optionally narrow delivery to one entity with scopeType plus scopeEntityIdentifier: SPACE / FOLDER / TASK_LIST / TASK (identifier), WIKI_SPACE (space key), WIKI_PAGE (page id; covers its descendants), FEEDBACK_BOARD (board slug or id; stored and listed as the board UUID), FEEDBACK_REQUEST / FEEDBACK_BUG (short key such as "FR-12", or id); omit both for workspace-wide delivery. A scoped webhook may only list event types of its scope's product. Wiki and feature-request events need the API key to hold that product's read scope, and every delivery is re-checked: an event is sent only while the webhook creator can still see the item. Security bugs are not delivered to webhooks created with an API key: includeSecurityBugs can only be turned on by a workspace admin signed in as a person. Envelope: {version, id, type, timestamp, workspaceIdentifier, source ("pm" | "codexum" | "roadmarq"), eventId (stable across webhooks and replays; use it to de-duplicate), data}. Payloads are thin: no content bodies, comment text or emails. Retries fire at +0s / +1min / +5min (3 attempts total) and treat both 4xx and 5xx as failures. The URL must be publicly reachable: Dutify refuses private, loopback, link-local, CGNAT and IPv6 ULA addresses, localhost, bare hostnames and *.svc / *.cluster.local names (400 WEBHOOK_URL_NOT_ALLOWED) at create, update and resume, and re-checks it on every attempt. Redirects are not followed; http:// is accepted for public addresses. API-key scope: `webhooks:write`.
    ConnectorNo auth
  • WHAT: Runs the Fairquery Apify Actor osv-dependency-vulnerability-check: parses package.json, package-lock.json (v1-v3), requirements.txt or go.mod (or a package list), checks OSV, and returns per-package max severity/CVSS, fixed versions, a recommended upgrade version and one row per vulnerability (deduped aliases). WHEN: Only for manifests, severity filtering or fix recommendations: full project audits from a pasted manifest, CI-style reports; for a few exact versions use osv_query_packages (free). WHEN NOT: Quick checks of a few exact versions (osv_query_packages, free) or one advisory (osv_get_vulnerability, free). COST: Paid, billed to YOUR Apify account via your APIFY_TOKEN: $0.50 per 1,000 packages + $1.50 per 1,000 vulnerabilities found (+ $0.05 per 1,000 runs). Use minSeverity="HIGH" to cut vuln rows. lodash+django (2 pkgs, 41 vulns) ~ $0.06. RETURNS: Paged rows type="package" (vulnerable, vuln_count, max_severity, fixed_versions, recommended_version), type="vulnerability" (id, cve_ids, severity, cvss_score, fixed_versions, osv_url) or type="error". Tool errors: INPUT_EMPTY, APIFY_TOKEN_MISSING, APIFY_TOKEN_INVALID, APIFY_PAYMENT_REQUIRED, APIFY_ACTOR_RUN_FAILED, APIFY_TIMEOUT. BEHAVIOR: Called from this Fairquery-hosted Worker, which forwards your input and Apify token to Apify and waits 20 s (APIFY_TIMEOUT if the run has not finished). This Worker's code is designed not to store them. The Actor in your account queries OSV.dev. Up to 1000 packages or a 2,000,000-char manifest. PARAMETERS: packages or manifestText = input (one required); manifestType = format, default auto-detect; minSeverity = only report at/above ALL|LOW|MEDIUM|HIGH|CRITICAL (default ALL); includeDevDependencies (default true); limit = page size (default 100, max 1000); offset = items to skip for paging (default 0). EXAMPLE: {"manifestText":"django==3.2.0\nrequests==2.19.0","minSeverity":"HIGH"}
    ConnectorNo auth