"A tool for performing Git actions" matching MCP tools:

• get_xgr_starter_gas_optionsA

  XGR MCP GatewayB

  Check whether free native XGR starter gas is available for a low-balance EVM address. Use this before deployments, session starts, contract calls or other on-chain actions when the address lacks gas. Returns the fixed 1 XGR grant policy and the tool to call next.

  ConnectorNo auth

• get_sales_recommendationsA

  Meta CouncilA

  The caller's prioritized next-best sales actions: interested leads to convert, open deals gone stale enough to need a follow-up, and overdue tasks — each with a rationale and the exact governed tool to run next (convert_lead_to_deal / log_deal_activity / complete_sales_task) plus its arguments. Read-only; ranks the caller's own CRM data (overdue > convert > follow-up). Nothing is executed or sent — approve an item by calling the named write tool. Requires authentication.

  ConnectorNo auth

• input.send_actionsA

  GlasswarpA

  PREFERRED multi-step tool: run 1–10 predictable UI actions in one call (input.click_target, input.click_xy, input.type_text, input.send_keys, input.drag, input.scroll). Side effects: all actions execute on the remote desktop; fails fast before sending if any action is invalid. observe_after defaults true (verification observe: text+targets; set observe_image=true for JPEG). Do not batch across unpredictable waits (page loads, installers, modals) — single-step those. Prefer this over chaining solo click/type/keys tools.

  Connector

  Destructive

  No auth

• linkedin_analyticsA

  YouSpotA

  The user's LinkedIn post analytics from LinkedIn's own API (their connected account) — impressions, unique members reached, reactions, comments, and reshares. Use for questions like 'how many impressions did I get last month?' or 'how are my posts performing?'. Omit dates for lifetime totals; pass start_date/end_date for a window; set daily=true (with one specific metric) for a per-day series to describe trends. Numbers are live from LinkedIn, unlike get_my_linkedin_posts whose per-post counts come from a periodic sync.

  ConnectorNo auth

• observe_factA

  SeenRelayA

  After independently performing a source-backed validation, deposit the observed result for later CHECKs. Returns accepted=true when a new observation is stored or deduplicated=true for a recognized retry/recent duplicate. Never OBSERVE hearsay. Optional Ed25519 proof establishes key possession and continuity, not truth or real-world independence.

  ConnectorNo auth

• linux_osA

  ZEN SecDBA

  List supported Linux operating systems and their corresponding versions for use with the `linux_audit` tool. ## What this tool does Returns an array of supported OS/version pairs, each in the form: {"os":"name", "versions":["version or codename"]} This allows the LLM and the user to know exactly which inputs are valid for the `linux_audit` tool. ## When to use this tool Use this tool when: - the user does not know which OS names or versions are supported - the user provides unclear or ambiguous OS information - you need to validate `os`/`version` before performing a Linux audit This tool should typically be called **before `linux_audit`** whenever parameters are uncertain. ## Inputs This tool does not require any input. ## Outputs Returns an array of objects: - **os**: supported Linux distribution identifier - **versions**: corresponding list of supported release or codename Example: [ {"os": "ubuntu", "versions": ["noble","focal"]}, {"os": "debian", "versions": ["bookworm","sid"]}, {"os": "redhat", "version": ["redhat-9.0"]} ] ## LLM usage guidelines - Use this tool to validate or suggest correct OS/version combinations before calling `linux_audit`. - If the user provides invalid or misspelled OS names, retrieve the official list here and ask them to select one. - Do not guess operating system identifiers-always rely on this tool to confirm correctness.

  ConnectorNo auth

• get_policy_eventsA

  Silicon AnalystsA

  Trade-Policy Timeline — the dated log of semiconductor trade-policy actions (export controls, entity listings, license policies, tariffs, subsidies, retaliation) anchored to GOVERNMENT PRIMARY documents (Federal Register / BIS, USTR, MOFCOM, METI, EU, Netherlands…), back to the Oct 2022 BIS advanced-computing rule. Each row: jurisdiction, agency, event_type, title, published/effective dates, affected_entities, node_threshold, a document reference (e.g. Federal Register cite), source URL, verbatim quote. USE THIS for: "what export-control rule changed in December 2024?", building a policy timeline, "which actions named SMIC?", grounding a geopolitics/supply analysis in the actual published action. DO NOT USE for: analysis/commentary on policy (use get_market_intelligence); rumored or anticipated actions (only PUBLISHED actions are recorded). Filters: jurisdiction (us|china|japan|netherlands|korea|taiwan|eu|uk|other), agency (BIS|USTR|MOFCOM|METI|EU-COM…), event_type. Latest slice for all tiers; full history Pro (never a 403). Cite as "Silicon Analysts — Trade-Policy Timeline".

  ConnectorNo auth

• leave_pilgrim_noteA

  Manekami — digital shrine & omikujiA

  Leave a transparent AI-labeled pilgrim note on the Manekami shrine wall after performing a ritual. Notes are moderated before appearing publicly. Keep it short, honest, and clear that this is ritual/entertainment, not a performance promise.

  ConnectorNo auth

• restore_versionA

  WebSlopA

  DESTRUCTIVE: Restore an app to a previous version using git reset --hard. This permanently overwrites all current files with the state from the specified commit — any changes made after that commit will be lost and CANNOT be recovered. You MUST confirm with the user before calling this tool. Use list_versions to show the user available versions first.

  ConnectorNo auth

• workspaceA

  Fast.ioA

  Workspace management: list/details/update/delete, archive, members, notes, quickshares, share import, import toggle. NOTE: metadata actions MOVED — the workspace metadata vocabulary → `metadata` tool; node-level metadata → `storage` tool. There are no `metadata-*` actions on this tool. Call action='describe' for the full action/param reference. Destructive: delete (workspace + all files). ⚠️ intelligence COSTS CREDITS (10/page) — only enable on explicit user request; toggle is rate-limited. Verbosity (detail param): list/available/members/list-shares default to terse (compact rows). details defaults to full (drill-down). Pass an explicit detail='standard'|'full' to override.

  Connector

  Destructive

  No auth

• artifact-get_git_tokenA

  Anima MCP ServerA

  Get git access to an EXISTING artifact, for local development with a real git client. Use this when you HAVE a working shell with git and outbound network access AND the job suits a local checkout — a large refactor, running or testing the project, branches, or history rewriting. For ordinary reading and editing of an artifact’s files, prefer artifact-explore and artifact-edit: they need no shell, no git and no network of your own, and they change the same repository. An artifact is a real git repository. Pass the sessionId — the id of an existing artifact (e.g. the last path segment of a .../chat/<sessionId> URL, like "mr25vsjppVtbMx") — and this returns a gitRemoteUrl plus the authenticated principal’s commitAuthor. After cloning, apply the returned `git config user.name` and `user.email` instructions before committing; then edit files, commit, and `git push` — pushing updates the live artifact. The gitRemoteUrl holds a short-lived access token scoped to this one artifact (read-only or read-write, depending on your access). Tokens CANNOT be renewed: on a "token expired" git error, call this tool again for a fresh gitRemoteUrl and run `git remote set-url origin <new gitRemoteUrl>`, then retry. If a git command instead fails because the host cannot resolve or reach the server (DNS, proxy or firewall errors), do NOT retry it — that environment has no route to the git remote, so use artifact-edit instead. Treat the gitRemoteUrl as a secret. To rename an artifact or change its visibility, use artifact-update_metadata.

  ConnectorOAuth

• mesh-audit-external-postureA

  MeshMarketB

  Mesh Audit — External Posture — Consent-gated, READ-ONLY external posture report — informational only, not a formal audit or warranty. From an authorization-to-test for a host you own, it observes over HTTPS what the internet already sees: security headers, software banners, and exposed /.env //.git/admin surfaces. Always names what it did NOT check; internal targets refused. Input: {consent_id, asset} via /api/audit/consent. (6 MESH/call, a tool · audit)

  ConnectorNo auth

• memoryA

  ContextStreamB

  Persistent memory storage — docs, runbooks, specs, ADRs, RFCs, decisions, lessons, preferences, tasks, todos, knowledge nodes, transcripts. NOT for codebase/file search. ⚠️ FINDING A DOC, RUNBOOK, SPEC, OR ARCHITECTURE NOTE? USE THIS TOOL — NOT `find`, `ls`, `grep`, or filesystem searches. ContextStream docs/runbooks/specs/decisions/lessons live ONLY in this tool's storage (Postgres + indexes), NEVER on disk under ~/.claude, /tmp, or the project tree. If the user mentions 'the doc on X', 'our runbook for Y', 'the design spec', 'the ADR/RFC', 'a postmortem', 'the architecture note', 'why we decided Z' — go through: · memory(action="search", query="…") — hybrid across docs + nodes (try this first when unsure) · memory(action="list_docs", query="…") then memory(action="get_doc", doc_id="<id-or-title>") · memory(action="decisions", query="…") for past architectural decisions · session(action="recall", query="…") if it might be in past-session transcripts Falling back to filesystem tools to find a ContextStream doc is wrong — the doc is not on disk. Codebase / source / files? Use the `search` tool, not memory. Plans? Use session(action="capture_plan") instead of memory(action="create_event", event_type="plan"). Plan tasks should be created with plan_id, plan_step_id, priority/status, and detailed descriptions. DISTINCT FROM (don't use memory for these): · entity(kind=ticket|handoff|incident|release|experiment|goal|key_result|sprint|review|risk|backlog_view) — structured taxonomy entities with their own status timelines and per-kind fields. When the user says 'create a ticket', 'file a bug', 'create a handoff', 'log an incident', 'track this release' — that's `entity`, not memory(create_task). · session(action=capture_lesson|capture|recall|capture_plan) — lessons / decisions / snapshots / plans tied to the current session. · capsule(...) — portable context bundles for cross-agent handoffs. This tool's `create_task` is a lightweight project-tracking todo with priority/status — NOT a 'ticket'. This tool's `create_task` should include plan_id and plan_step_id when the task belongs to a plan. This tool's `create_doc(doc_type=runbook)` is a versioned markdown doc — NOT a 'handoff'. Node actions: create_node, get_node, update_node, delete_node, list_nodes, supersede_node (node_id accepts an id or lookup text; ambiguous text returns a [CANDIDATES] list). Query actions: search (searches memory nodes and relevant docs together, not code), decisions (typed envelope: query, category, sort=recency|relevance, status=active|superseded|disputed|verified|all, since, offset, limit), timeline, summary. Decision actions: create_decision (title, content, rationale, alternatives, scope, confidence, supersedes, category, tags), decision_action (decision_id or lookup text + decision_action=supersede|dispute|verify|invalidate|choose_successor, successor_id, reason). Event actions: create_event, get_event, update_event, delete_event, list_events, distill_event, import_batch. Task actions: create_task, get_task, update_task, delete_task, list_tasks, reorder_tasks. Todo actions: create_todo, list_todos, get_todo, update_todo, delete_todo, complete_todo. Diagram actions: create_diagram, list_diagrams, get_diagram, update_diagram, delete_diagram (diagram_type values: flowchart, sequence, class, er, gantt, mindmap, pie, other — use sequence for API/request flows and er for data models). Doc actions: create_doc, list_docs, get_doc, update_doc, delete_doc, create_roadmap (doc_type values: roadmap, spec, runbook, adr, rfc, postmortem, retro, release_notes, playbook, prd, user_story, persona, interview, design_spec, critique, glossary, oncall_schedule, slo, q_and_a, changelog, style_guide, general — `get_doc` accepts ID or natural-language title query). Transcript actions: list_transcripts, get_transcript, search_transcripts, search_archive, delete_transcript. `search_archive` queries the cold storage tier for transcripts past the hot-retention window (remote/hosted deployments only). Team actions: team_tasks, team_todos, team_diagrams, team_docs.

  Connector

  Destructive

  OAuth

• aicom_creditsA

  aicomglobalA

  FREE. Check your aicomglobal credit balance and how to fund + spend it. Credit is a closed-loop prepaid balance for paying IN-BAND (over /a2a or /mcp, where x402 can't ride the transport): settle the per-call actions (aicom_verdict / aicom_x402_route / aicom_attest) from the balance by passing pay_with:'credits' — the signed artifact returns IN the tool call, no wallet, no chain, no 402. FUND IT AUTONOMOUSLY: GET /credits/x402/starter for a nonce, then POST {nonce} and settle $5 USDC over x402 yourself — no human, no card. (Or your principal may fund by card at its discretion: POST /credits/checkout {pack}.) Credit is prepaid, closed-loop, non-transferable and non-refundable — spendable only on aicomglobal's own actions.

  ConnectorNo auth

• get_top_hedge_fund_managersA

  TipRanksA

  Returns top-performing hedge fund managers ranked by success rate and returns. Args: num: Number of managers to return (default 10, max 100 — the upstream returns 100 for anything higher)

  ConnectorNo auth

• check_upgrade_safetyA

  Breaking Changes & Migration DataA

  Given a package and the version you are upgrading TO, return a concise checklist an agent can act on: the count of breaking changes, the highest-risk removals, whether automated codemods exist, and the recommended upgrade path. Use before performing an upgrade.

  ConnectorNo auth

• list_actionsA

  noticedB

  Every OPEN follow-up / action across your WHOLE network in one call, each attached to the person it belongs to — ordered like /home (soonest remind_at first, undated last). scope:'team' returns consent-gated open actions across a Team, attributed to their owner; pass team_id when you belong to more than one. Pass goal_id to keep only Actions for confirmed people in that Goal; a Team sweep requires a Goal owned by the selected Team. Use this to sweep all your to-dos (e.g. "what are all my open actions?") instead of calling get_person per person. Pass undated:true to see only the open-ended ones (no remind_at). Optionally scope to one person_id or cap the count with limit. Read-only — for one person's actions use get_person → relationship.actions.

  ConnectorNo auth

• my_booksA

  bookstore4agentsB

  Author dashboard: list every book the authenticated account has authored, with status (draft/published), current version, sales count (active entitlements), and gross revenue. This is the only way to see how a published book is performing without scraping the public catalog.

  ConnectorNo auth

• get_campaign_performanceA

  Trillboards DOOH AdvertisingB

  Get detailed performance metrics for a campaign. WHEN TO USE: - Monitoring active campaign performance - Reviewing completed campaign results - Getting per-screen impression breakdowns RETURNS: - campaign_id, name, status, budget, dates - performance: impressions, spend_estimate_usd, avg_cpm, unique_screens, avg_latency_ms - screen_breakdown: per-screen impressions and CPM EXAMPLE: User: "How is my NYC retail campaign performing?" get_campaign_performance({ campaign_id: "550e8400-e29b-41d4-a716-446655440000" })

  ConnectorNo auth

• get_content_recommendationsA

  Trillboards DOOH AdvertisingB

  Get best-performing content recommendations for a venue type and optional time context. WHEN TO USE: - Deciding what content to schedule at a specific venue type - Finding content that drives the highest audience engagement at a location - Optimizing content rotation by daypart (morning, afternoon, evening, overnight) - Content programming decisions based on performance data RETURNS: - data: Array of recommended content ranked by performance score - videoId, title, contentCategory, durationSeconds - totalPlays, uniqueScreens - avgAttention (0-1), avgDwellMs - performanceScore (composite of attention, replay density, dwell time) - meta: { count, venue_type, daypart, limit } Performance score formula: attention(40%) + replay_density(30%) + dwell_time(30%) EXAMPLE: User: "What content works best in bars during the evening?" get_content_recommendations({ venue_type: "bar", daypart: "evening", limit: 10 }) User: "Best performing content for transit screens" get_content_recommendations({ venue_type: "transit", limit: 20 })

  ConnectorNo auth

• searchA

  OutageDeckA

  Search everything OutageDeck tracks: cloud and SaaS providers, and their incident history. Returns citable results with stable ids for the fetch tool. Use for open questions like "who had outages last week" or "find the GitHub Actions incident"; use get_provider_status when the question is simply whether one named vendor is down right now.

  ConnectorNo auth