Skip to main content
Glama
812,527 tools. Updated 2026-11-20 19:09

"Using Command Line with MCP (Master Control Program)" matching MCP tools:

  • Transfer partner map. Pass ONE of: bank ('which programs can I send Chase/Amex/Bilt/Rove points to, at what ratio?'), program ('which banks feed Flying Blue and which airlines can it book?'), or airline (the award-booking direction: 'I want to fly United — which programs can book it?'). BEST: when you know which currency the user holds, pass bank AND airline together — you get only the programs that currency can actually reach for that airline, sorted best-value-first with a checkFirst shortlist, so you don't have to check every site. Includes alliances and per-program point valuations.
    ConnectorNo auth
  • Computes a personal angel number from a birth date using the Pythagorean Life Path as the base. Life Path 1-9 maps to the triple sequence (LP 4 → 444). Master numbers 11, 22, 33 map to 1111, 2222, 3333 respectively. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — confirm Life Path before calling. AFTER: None. INPUT CONTRACT: date: Birth date in YYYY-MM-DD format. Example: '1994-03-31' name (optional): Person's name for personalisation. DO NOT CONFUSE WITH: asterwise_get_angel_number_today — collective daily number from today's date, not birth date. asterwise_get_numerology_profile — full Pythagorean profile; this tool extracts only the Life Path → angel sequence mapping. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-angel-number-personal/
    ConnectorOAuth
  • 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
  • Validates a Python automation script that runs OUTSIDE the game, on three axes: Python syntax (using the real interpreter), Minecraft commands embedded in the script (against the official command index), and the shape of the /connect WebSocket message envelope. For behavior pack scripts use validate_script instead — Python does not run inside a pack. The embedded command check is the most valuable one: a command written from memory can look syntactically fine and still do nothing in the game. Only strings starting with / are treated as commands. If syntax could not be checked, syntaxChecked is false in the result; ok:true alone does not mean the syntax is valid.
    ConnectorNo auth
  • Submits an enquiry to Smoke Control Checker: NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token; show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Send my contact details to up to three stove installers, chosen by Smoke Control Checker, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
    ConnectorNo auth
  • Computes a personal angel number from a birth date using the Pythagorean Life Path as the base. Life Path 1-9 maps to the triple sequence (LP 4 → 444). Master numbers 11, 22, 33 map to 1111, 2222, 3333 respectively. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — confirm Life Path before calling. AFTER: None. INPUT CONTRACT: date: Birth date in YYYY-MM-DD format. Example: '1994-03-31' name (optional): Person's name for personalisation. DO NOT CONFUSE WITH: asterwise_get_angel_number_today — collective daily number from today's date, not birth date. asterwise_get_numerology_profile — full Pythagorean profile; this tool extracts only the Life Path → angel sequence mapping. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-angel-number-personal/
    ConnectorOAuth

Matching MCP Servers

Matching MCP Connectors

  • The phone network for AI: get a line, call other AIs turn by turn, read missed calls. Costs $0.

  • D.O Command: clients, tasks, agenda, WhatsApp conversations and reports for your service business.

  • The vocabulary list_components filters by: the category tree, the tags in use, the authors with a published control, or the hosts a control can run in, each with its slug and a count. Use it to turn a name a person used into a slug; it returns no controls, so pass the slug to list_components to see them. Not paged — categories come back as a full tree and authors as a full list, while tags are capped at the 500 most used.
    ConnectorNo auth
  • Run a shell command inside a running container instance on Cycle, over the instance's SSH gateway, and return the shell output. Use this for one-time setup that must run inside a container — e.g. initializing a MongoDB replica set with 'mongosh --eval "rs.initiate({...})"'. The instance must be RUNNING (start the container first). If the container has multiple instances, pass 'instance' (id or hostname); otherwise the sole instance is used. Containers reach each other by hostname over the environment's private network, so commands can reference sibling containers (e.g. mongo-1:27017). This executes an arbitrary command inside your container — it is powerful and mutating. Always call with preview:true first: it echoes back the exact command and target without making any connection, so the user can confirm it is what they intend (nothing is validated — the command may still fail when run). Confirm with the user, then call again without preview. Never run a command without explicit confirmation. Short-lived SSH credentials are generated for the run and expired immediately after. The command runs in an interactive shell; make destructive commands idempotent where possible.
    Connector
    Destructive
    API key
  • Set the absolute quantity of a basket line using its item_id from get_cart, not product_id. Zero removes the line; use add_cart_item to increment instead. Returns the refreshed basket; no order or payment. OAuth scopes: cart:write. Changes buyer or order state.
    Connector
    Destructive
    No auth
  • Use when get_program and search_programs do not find a brand's affiliate program: queues the brand's own program page for a maintainer to verify against the brand's published terms. Not instant: nothing is listed and no score exists until the terms are verified. A domain already listed returns its listingUrl instead; a domain already queued returns the existing submission. Send the brand's own program or partners page, never a network or review site. Never invent terms. Then call get_submission_status with the returned id.
    ConnectorNo auth
  • Proves whether this host can execute FinStat's signed HTTPS upload program. Call with workspace_tag and an idempotency_key to start: the result carries a short-lived nonce, an opaque check_id, and a PUT program for the host to execute with that exact nonce. Call again with the check_id to read the verdict; exact replay of the start is safe and returns the same probe. pending means proof may still arrive; capable means the upload was verified; incapable is declared only after expiry without proof. A transfer-service failure reports data_channel_unavailable, never incapable. The probe is temporary and never admitted. Not metered.
    ConnectorOAuth
  • Use this when the user wants to transcribe a LOCAL file (on their computer), not a public URL. Returns a short-lived link and a ready-to-run `curl` command. Run the command with the file path (you need shell access, e.g. in Claude Code, Cursor or Codex); it prints JSON with an `upload_url`. Then call `submit_transcript` with that printed `upload_url` as `audio_url` (not the link itself). The file goes to the user's private AssemblyAI storage, not a public host. Files up to 4.5 MB; the link expires in 10 minutes.
    ConnectorOAuth
  • Reads or changes who drives a connected remote browser: `agent` (your CDP connection) or `human` (a person in its live view, see spicrawl_browser_live_view). `status` reads it: poll it after sending a live-view link, and continue once `controller` is `agent` again. `takeover` hands control to the person before they ask (your input and navigation then fail with error -32001); `release` takes it back. The person can also take and give back control from the live view themselves.
    ConnectorAPI key
  • Reads or changes who drives a connected remote browser: `agent` (your CDP connection) or `human` (a person in its live view, see spicrawl_browser_live_view). `status` reads it: poll it after sending a live-view link, and continue once `controller` is `agent` again. `takeover` hands control to the person before they ask (your input and navigation then fail with error -32001); `release` takes it back. The person can also take and give back control from the live view themselves.
    ConnectorNo auth
  • Read an environment's logs: one deploy's build log, or a service's output. Use it to follow a deploy, or to find why a running service fails. ``source`` picks the log, and each source takes its own arguments. The tool refuses an argument that belongs to the other source. **source="deploy"** reads a deploy's status and its build log tail. Pass ``deploy_id``, as returned by deploy. The FIRST line of the reply states the outcome: ``deploy <id> — <status> (sha <sha>)`` with status one of queued | running | success | failed | superseded | cancelled. Read the status from that header — never grep the log text for 'deploy success'. While the status is queued or running, poll this tool again: the tail shows live progress. On failed, the reason is in the log. superseded: a newer deploy request for this environment replaced this one. ``superseded_by`` names it, so poll that id; the header reads ``deploy <id> — superseded by <id> (sha <sha>)``. Its log is empty, or ends where a control-plane restart paused it. cancelled: a database restore of the environment started before this deploy ran, so it never ran. The log's last line says so. Deploy again once the restore ends. The reply defaults to the last 16384 bytes of the log; a marker line reports how many earlier bytes were omitted. Page with ``offset`` (byte offset to read from, no default) and ``max_bytes`` (window size, up to 262144). This log covers the build and boot window only, and ends when the deploy finishes. Call this tool with source="runtime" for the running app's ongoing stdout/stderr. That source answers why a container crashed minutes after a successful deploy. For 'docker'-template services the log includes '[build] ...' lines: queue position while waiting, build duration, and the image size / plan-cap result. **source="runtime"** reads a running app's stdout/stderr — the log AFTER deploy. The deploy log only covers the build/boot window; this is the ongoing runtime output, and it survives the container: when a redeploy replaces a container the platform archives that container's log, so you can still read why the previous version crashed. In a project with several services, ``service`` picks the service whose newest container the reply shows. The reply always starts with a status header (state, exit code, whether it was OOM-killed, restart count, which container indices are readable). **Omit `command` for the header alone.** The header states whether the app crashed and how, and it starts nothing on the host. The header's first line names the container the reply shows, by index and short container id. The default is the newest container, which after a failed deploy is the crashed new one, not the one serving traffic. When a different container runs, a `running now: container #K` line names it; pass `container_index=K` to read the live app. When the host that ran a container does not answer, or no longer holds it (after a move), the header comes from the central log store: it says `source: central log store`, and its state is `unknown` when the platform has no record of how the container ended. A `command` works there too: it runs on the lines the central log store holds for that container. With a `command`, the platform copies the selected log to **`/log/app.log`** and runs your command in a throwaway Debian container with `/log` as the working directory (so a bare `app.log` works). One line per output line, prefixed with an RFC3339Nano timestamp; stdout and stderr are merged in the order the app emitted them. Available tools: `sh`, `bash`, `grep`, `sed`, `awk`, `tail`, `head`, `cut`, `tr`, `sort`, `uniq`, `wc`, `find`, `xargs`, `gzip`/`zcat`, `tac`, `nl`, `od`, `strings`, `base64`, `perl`, `python3`, `node`. There is **no `jq`, `rg` or `less`**. The container has **no network**, no access to your app or its data, and is destroyed afterwards. The command reads only that copy of the log, and nothing it writes outlives the call. Examples: command="tail -n 200 app.log" command="grep -i error app.log | tail -20" Runtime limits: the command is stopped after 30 s and its output is capped at ~256 KiB (pipe through `tail`/`head` to stay under). A read from the central log store keeps the newest 200,000 lines or 64 MiB of the container's log; when it drops older lines, the header says `older lines omitted`. Only stdout/stderr is captured — if your app writes its logs to a file inside the container, nothing will be here. Reference: https://docs.xhostd.com/mcp-tools#get_logs
    ConnectorOAuth
  • Create an order from the session cart (starts unpaid — PENDING_ARTWORK or PENDING_PAYMENT depending on the server). For a one-line cart, pass that line's `offer_id` alone. For a cart with several lines, pass `selections=[{line_id, offer_id}, ...]`, one per line, to order them together as one order with one item per line; a bare `offer_id` against such a cart is rejected (`MultiLineCartError`) rather than silently ordering just one line. Each item re-sends the sku + configuration its quote priced and binds the chosen offer; the server recomputes price, so no money is sent. Every `offer_id` must belong to the cart (`OfferNotFoundError` / `LineNotFoundError` otherwise — re-run `order_get_quote`). If RendReal refuses the chosen offer, the job fails with `OfferRefusedError` and no order is placed: quote again and let the customer choose. If RendReal refuses the order itself, the job fails with `OrderRefusedError`: the refusal is permanent, so offer a change to the setup or customer support, never a retry. Shipping and tax are filled by Stripe at checkout. Attach artwork per line: with `selections`, set each entry's `design_id` + `design_snapshot_id`; with a bare `offer_id`, pass the top-level `design_id` + `design_snapshot_id`. Both ids are required for a design to attach, and the snapshot must be the owned design's latest. Every line needs artwork — a design, or a finished artwork file uploaded via `order_get_artwork_upload_page` — before the order can be paid (`order_create_payment_link` enforces it). A line already ordered in this session is refused (`LineAlreadyOrderedError`) before any upstream order is placed, so the same still-quoted line can't be bought twice; `order_view_cart` marks such a line `in_checkout=true`. Start a new line to buy it again. If `catalog_configure_product` reported an Unmet Constraint for any selected line, the order is refused (`UnmetConstraintUnansweredError`; `detail.lines` lists every such line with its asks in `unmet`) until the customer answers for each listed line. Tell the customer, per line, what they asked for and what the option accepts. If they accept every listed line as configured, call again with `unmet_accepted=true`, which orders all the selected lines. If they want a change on any line, call `catalog_configure_product` with their answer for that line instead. Returns a job — poll until SUCCEEDED for the `order_id` and each line's `item_id`. Then get any missing artwork: design it against the order, or have the customer upload a finished file. Call `order_create_payment_link` only when the customer asks to pay. An item with `designable: false` cannot be designed here: for that item offer only the upload of a finished print file, never a design.
    Connector
    Destructive
    No auth
  • Proves whether this host can execute FinStat's signed HTTPS upload program. Call with workspace_tag and an idempotency_key to start: the result carries a short-lived nonce, an opaque check_id, and a PUT program for the host to execute with that exact nonce. Call again with the check_id to read the verdict; exact replay of the start is safe and returns the same probe. pending means proof may still arrive; capable means the upload was verified; incapable is declared only after expiry without proof. A transfer-service failure reports data_channel_unavailable, never incapable. The probe is temporary and never admitted. Not metered.
    ConnectorOAuth
  • Returns resource URLs/content in this response; it does NOT write any files. Each resource comes back with a ready `fetch` shell command — run it yourself to save the file to its `dest`. Use inline=true only when a `fetch` command could not reach the server; the content then arrives in this response and you must write it to `dest`. Pass `filename` (string) or `filenames` (array), plus `workspace_dir` (the mapping workflow's) so `dest` matches the workflow's paths; calling with neither filename returns the list of available resources (it does not fail). Available: sz_json_analyzer.py, sz_schema_generator.py, sz_verbatim_check.py, sz_routing_report.py, senzing_entity_specification.md, senzing_mapping_examples.md, identifier_crosswalk.json mapping_workflow and analyze_record already return each resource's `fetch` command — you do not need this tool to run them. If a previously-known fetch instruction stops working, call this tool again to obtain the current one.
    ConnectorNo auth
  • Search for upcoming public PGA Coach programs (clinics, camps, classes, and other group events) near a location (required). Use this tool when the user asks to find programs, clinics, camps, classes, or group events — not private one-on-one lessons. For private lesson coaches, use `search_golf_coaches` instead. Internal record identifiers (for example program `id` and coach `slug`) are for tool calls only and must never be shown or mentioned to the user. - Search results include program details plus the hosting coach and facility for each program. - The response also includes top-level `coaches` and `facilities` arrays summarizing the unique coaches and venues in the result set — always present those to the user. - Results are ordered by program start instant and filtered to the requested radius. - Discovery uses nearby PGA Coach profiles (nearest 20 in the radius), then loads up to 30 upcoming public programs per coach in a 180-day window in one batched GraphQL request. Facility coordinates still have to fall inside the radius. - Results are paginated. The pagination cursor carries the remaining nearby programs so additional pages do not repeat GraphQL discovery. Reuse that cursor with the original location and radius. - Direct golfers to the program URL to view details and register. Coach profile and booking URLs are also included when the golfer wants to learn more about the coach.
    ConnectorOAuth
  • Search NABarFinder — a human-verified directory of 1554 venues with real non-alcoholic (NA) drink programs across 70 cities in the US, UK, and beyond. All filters are optional and combine with AND; with no filters it returns the top-rated venues overall. Returns at most 25 venues (sorted by NA Program Strength descending, then name), each with name, slug, city, venue type, naProgramStrength (1–5; 5 = fully alcohol-free or a dedicated NA program, 1 = a few NA options), a one-line summary, and the canonical nabarfinder.com page URL for citing/linking. The response includes the total match count; if it exceeds the cap, narrow with filters. Use get_venue with a result's slug for the full record. Read-only.
    ConnectorNo auth
  • Store a SECRET for a graduated app (tier 4), bound to a host pattern. The value is encrypted at rest and NEVER readable back — by anyone, ever. The platform's egress membrane attaches it on outbound requests to the declared host, so your server code calls the API WITH NO KEY and never sees it. The host must be EXACTLY the one the code calls (api.example.com is not example.com; *.example.com covers subdomains, not example.com): with no matching secret the request leaves WITHOUT a key (the API usually answers 401); when the vault holds other secrets, the app's log (dropyour_logs) says so. The membrane sits ABOVE the socket: it does not terminate your TLS and injects no certificate authority into your sandbox — we attach a header, we never open your connection. `form` says HOW it is attached: bearer (default, Authorization: Bearer), header (X-Api-Key and friends), basic (key as username), or query (?api_key=). The form belongs to the secret, not to your code — changing how an API authenticates never means editing your app. Writing an existing name rotates it: omit `form` and the secret KEEPS the form it already has (give `form` only to change it; a new name defaults to bearer). dropyour_secrets_list shows each secret's form (type and field name, never the value). The value cannot contain control characters (line break, tab, NUL). Name: UPPERCASE_WITH_DIGITS (≤32). Host: lowercase domain, leading `*.` wildcard allowed. Value ≤ 4096 bytes, 16 secrets per app. Requires ownership (account token or managementToken). THIS TOOL TAKES THE VALUE AS A PARAMETER, SO IT PASSES THROUGH THIS CONVERSATION. When the value must not be seen here, do NOT ask the user to paste it: point them to a way that keeps it out. Either the app's page on dropyour.io (Settings, Secrets: a masked field), or one command they run themselves, the value read from their keychain or a file and sent as the request BODY: `curl -sS -X PUT --data-binary @- --config <account token header, read from the keychain> "https://dropyour.io/api/drops/<dropId>/secrets/<NAME>?host=<host>"` (optional `&form=basic`, `&form=header:X-Api-Key`, `&form=query:api_key`; without `form`, a replaced secret keeps its form). The exact command is at https://dropyour.io/en/docs/operate#secrets. Same vault, same rules; the response returns the name, host, date and form only. The account token is a secret too: it is read from the keychain in that same command, never pasted here, and passed through `--config`, never as a command-line argument.
    Connector
    Destructive
    No auth