"A server for running Kubernetes with Cursor integration" matching MCP tools:

• biorxiv_list_recentA

  biorxiv-mcp-serverA

  List preprints posted or revised within a date interval, optionally scoped to one server or a subject category. Returns 30 preprints per page (fixed by the API); pass `cursor` as an integer offset (0, 30, 60, …) to step through additional pages. Abstracts are omitted by default to keep the page small — pass include_abstract: true for the whole page, or call biorxiv_get_preprint (up to 10 DOIs per call) for a few. When server="both" (default), per-server pagination state is returned separately — use each server's `cursor` field for independent advancement. One server failing under server="both" does not abort the call: the other server's page is still returned and the failed one is named in `failed[]`, marking the result set as partial rather than complete. Every attempted server failing is a different case and does abort the call, with a retryable upstream_unavailable (or rate_limited) error — an empty page would otherwise be indistinguishable from an interval that genuinely holds nothing. Call biorxiv_list_categories for valid category strings; a server that answers a category filter with its unfiltered listing is left out with a notice, and invalid_category is raised when no server applied it. `funder` limits the listing to bioRxiv preprints funded by that organization, given its ROR ID; an ID api.biorxiv.org has no funder record for raises invalid_funder rather than returning an empty page.

  ConnectorNo auth

• get_new_sinceA

  Horizon AI IntelligenceA

  Incremental poll: raw item-level AI news added since a cursor, oldest→newest, with a nextCursor for your next call — use this for "what's new since I last checked"; for the curated once-daily synthesis use get_daily_briefing. Omit cursor for the latest items plus a cursor to start polling from. Titles + links + topics (bodies and higher limits are on the paid tier).

  ConnectorNo auth

• pingA

  Nordic Financial MCPA

  Connectivity check that confirms the Nordic MCP server process is responding. Use this at the start of a session to verify the server is reachable before making other calls. Do not use as a proxy for database health — the server can respond while the Qdrant vector database is temporarily unavailable. To confirm data availability, call search_filings directly. Returns: A greeting string: "Hello {name}! Nordic MCP server is running."

  ConnectorNo auth

• get_statusA

  TracklutionA

  Connectivity check only — does NOT return any analytics data. Pings every connected Tracklution server and reports reachable / unreachable. USE WHEN: - The user reports the integration "isn't working" and you need to isolate network vs. data issues. - You want to confirm a freshly-added server is online before running real queries. For any data question (counts, events, sessions), skip this and go straight to get_summary or get_report.

  ConnectorOAuth

• tflogsA

  InsideOut (Riley)A

  MONITORING: Fetch Terraform deployment logs with pagination Fetches logs from a running or completed Terraform deployment job. For **completed jobs**: uses REST endpoint for instant retrieval (supports `tail` for server-side filtering). For **running jobs**: streams via SSE with timeout-based pagination. **PAGINATION** (running jobs only): Use `last_event_id` from the response to fetch more: 1. First call: `tflogs(session_id='...')` → get logs + `last_event_id` 2. Next call: `tflogs(session_id='...', last_event_id='...')` → get NEW logs only 3. Repeat until `complete: true` in response **RESPONSE FIELDS**: - `logs`: Array of log messages collected - `last_event_id`: Pass this back to get more logs (pagination cursor, SSE only) - `complete`: true if job finished, false if more logs may be available - `total_logs`: total log entries before tail truncation REQUIRES: session_id from convoopen response (format: sess_v2_...). OPTIONAL: job_id to target a specific deployment (use tfruns to discover IDs), timeout (default 50s, max 55s), last_event_id (for pagination), tail (return only last N entries) ⚠️ CONTEXT WARNING: Deploy logs can be hundreds of lines. Use tail: 50 for completed jobs to avoid blowing up the context window.

  ConnectorNo auth

• tflogsA

  InsideOut (Riley)A

  MONITORING: Fetch Terraform deployment logs with pagination Fetches logs from a running or completed Terraform deployment job. For **completed jobs**: uses REST endpoint for instant retrieval (supports `tail` for server-side filtering). For **running jobs**: streams via SSE with timeout-based pagination. **PAGINATION** (running jobs only): Use `last_event_id` from the response to fetch more: 1. First call: `tflogs(session_id='...')` → get logs + `last_event_id` 2. Next call: `tflogs(session_id='...', last_event_id='...')` → get NEW logs only 3. Repeat until `complete: true` in response **RESPONSE FIELDS**: - `logs`: Array of log messages collected - `last_event_id`: Pass this back to get more logs (pagination cursor, SSE only) - `complete`: true if job finished, false if more logs may be available - `total_logs`: total log entries before tail truncation REQUIRES: session_id from convoopen response (format: sess_v2_...). OPTIONAL: job_id to target a specific deployment (use tfruns to discover IDs), timeout (default 50s, max 55s), last_event_id (for pagination), tail (return only last N entries) ⚠️ CONTEXT WARNING: Deploy logs can be hundreds of lines. Use tail: 50 for completed jobs to avoid blowing up the context window.

  ConnectorNo auth

• dreamagent_get_chat_statusA

  DreamAgentA

  Check the progress and final status of a specific AI development session using its session key. Use this to monitor an asynchronous edit until it completes, fails, or is cancelled — keep checking until a terminal state. The session key comes from dreamagent_chat or dreamagent_list_sessions and is an identifier, not a secret. Returns (actual fields): 'active=', 'run_status=', 'next_after=' (cursor for the next check), optional 'new_output:' (text produced since the last check), then either "Still working — poll again" or a terminal 'done=true' line: finished (with the final output tail), 'the edit was NOT started: <reason>' (rejected early, e.g. HTTP 402 insufficient credits), or 'stream error' (the connection to the run broke — the server-side run may still have finished; verify with dreamagent_get_edit_progress). run_status values: queued | running | cancel_requested | completed | failed | cancelled | interrupted | unknown.

  ConnectorNo auth

• verify_integrationA

  Alter OnboardingA

  Return a copy-pasteable recipe to VERIFY an integration works: `first-call` (code↔design, an audit row, correct attribution) or `per-user-isolation` (a multi-user/broker server runs two users under different credentials and rejects cross-user access). Guidance only — you run the commands.

  ConnectorNo auth

• bank_accountsA

  Inferventis — Financial Data, News & Web MCPA

  Retrieves bank account details and recent transaction history via a connected bank API integration. Returns a list of transactions for the specified account, or for all linked accounts when no account ID is provided. Use bank_accounts when an agent needs to inspect account balances, review recent spending, categorise transactions, or reconcile records against a specific bank account. Prefer open_banking_transactions when the integration uses a PSD2 Open Banking provider (TrueLayer) covering 300+ UK and European banks — open_banking_transactions returns richer transaction metadata including merchant names, categories, and running balances. Prefer stripe_payments when the source of payments is a Stripe merchant account rather than a retail bank account. This tool requires a valid bank API credential to be configured on the server.

  ConnectorNo auth

• bank_accountsA

  Inferventis MCP ServerA

  Retrieves bank account details and recent transaction history via a connected bank API integration. Returns a list of transactions for the specified account, or for all linked accounts when no account ID is provided. Use bank_accounts when an agent needs to inspect account balances, review recent spending, categorise transactions, or reconcile records against a specific bank account. Prefer open_banking_transactions when the integration uses a PSD2 Open Banking provider (TrueLayer) covering 300+ UK and European banks — open_banking_transactions returns richer transaction metadata including merchant names, categories, and running balances. Prefer stripe_payments when the source of payments is a Stripe merchant account rather than a retail bank account. This tool requires a valid bank API credential to be configured on the server.

  ConnectorNo auth

• colony_get_my_actionsA

  The ColonyB

  What have I actually committed? Your own recent writes, newest first. The outbound counterpart to ``colony_get_delta``, which deliberately omits your own authored rows. Use this to reconcile after losing context — a process that died after the server accepted a write, a fresh run with nothing inherited, or two sessions running at once. It reads your actual posts, comments and messages rather than a separate log, so it cannot disagree with what exists. **Bodies are not returned.** They run to 50 000 characters and this is a list. Each row carries ``resource_id`` to fetch the content, and ``body_hash`` — sha256 of the stored body — so you can check the server holds the text you think it does without transferring it. Scoped to you by construction; reading it marks nothing as read. ``count`` is how many actions this response holds; ``has_more`` is true when older actions remain (pass ``next_cursor`` as ``cursor``). Requires authentication.

  ConnectorNo auth

• colony_get_my_actionsA

  mcp-serverA

  What have I actually committed? Your own recent writes, newest first. The outbound counterpart to ``colony_get_delta``, which deliberately omits your own authored rows. Use this to reconcile after losing context — a process that died after the server accepted a write, a fresh run with nothing inherited, or two sessions running at once. It reads your actual posts, comments and messages rather than a separate log, so it cannot disagree with what exists. **Bodies are not returned.** They run to 50 000 characters and this is a list. Each row carries ``resource_id`` to fetch the content, and ``body_hash`` — sha256 of the stored body — so you can check the server holds the text you think it does without transferring it. Scoped to you by construction; reading it marks nothing as read. ``count`` is how many actions this response holds; ``has_more`` is true when older actions remain (pass ``next_cursor`` as ``cursor``). Requires authentication.

  ConnectorNo auth

• foresea_check_runA

  Foresea ForecastingA

  Call this after foresea_analyze_market timed out or errored with a message naming a client_run_key -- the research it started may still be running server-side. Returns {"status": "running", ...} if it's not done yet (call again in a bit), or the full report once it is. Do not call this speculatively; only use the client_run_key a prior foresea_analyze_market call actually gave you. Example: client_run_key="a1b2c3..." → {status:"running", id:"agent_run_..."} or the full report once complete.

  ConnectorNo auth

• get_integration_guideA

  The BridgeA

  Read the Bridge integration guide for a topic — the supported, opinionated way to consume Bridge from application code. Call this BEFORE writing or changing app code that reads a feature flag, renders billing or team UI, or wires authentication, and before hand-rolling anything against the SDK: the SDKs ship declarative surfaces for these cases (components, route guards, decorators) and reimplementing them against SDK internals is the most common integration mistake. Per-framework topics (framework REQUIRED): integration (first-time setup) | auth | feature-flags | billing | team | branding. Framework-agnostic MASTER topics (framework is IGNORED — omit it): master, the end-to-end auth integration prompt served by `bridge guide`, which orchestrates project discovery and then routes to the per-framework guides; flags-master and billing-master, the same orchestration for a flags-only or billing-only integration; mechanisms, how limits, upgrades and customization work; orientation, what Bridge does (the same map get_started returns); fit-together, how roles, plans, limits and flags fit together; integration-success, the message to show the developer when an integration is done. Before setting up flags, roles, plans or limits, read topic=fit-together. Start at topic=master when integrating Bridge into a project for the first time. framework: svelte | react | angular | nextjs | nestjs | express — pass the one the target app actually uses; this server cannot detect it. Returns the guide as markdown plus its source URL. Guidance is a default, not a mandate — follow the user's stated preference when it differs.

  ConnectorOAuth

• set_hostnameA

  EQVPS — VPS and code sandboxes for AI agentsA

  Set the VPS hostname (valid DNS name). Applied immediately inside the running server via the guest agent (Linux: hostnamectl + the 127.0.1.1 line in /etc/hosts; Windows: renamed, takes effect after a reboot — the response then has `reboot_required: true`). The server must be running with its guest agent active; otherwise the call fails with 409 `agent_unavailable` and nothing is changed. Your password, SSH host keys and files are not touched. Requires: token, server running. Typical error: 409 agent_unavailable → start the server / wait for boot.

  ConnectorNo auth

• avizo_docsA

  avizo-mcpA

  Without arguments: lists every documentation page on avizo.ro/docs (quickstart, alert cadence, hierarchical escalation, SmartBill integration, API reference, troubleshooting) with slug and description. With {slug}: returns that page as markdown — the exact content the site renders. For programmatic integration read {slug: "api-reference"}.

  ConnectorNo auth

• count_recordsA

  Taproot: AT Protocol MCPA

  Count the total records in an account's collection (e.g. how many likes a user has given). Scans server-side so you don't page manually. AT Protocol has no cheap exact count, so for very large collections this returns exact:false with a lower-bound count and a cursor,call again with that cursor and ADD the counts to keep going.

  ConnectorNo auth

• ni_services_reserveA

  Northside Intelligence WebMCPA

  Reserve a Northside Intelligence service project with a non-refundable deposit of 20% of that service's lowest price: intelligence audit $410, personal intelligence setup $50, workflow integration $1,010, custom web design $1,370, tailored intelligence server $5,140. The buyer's card is saved and the balance is charged when the service is complete; final price is confirmed after scoping. Returns a checkout_url and order_id; after payment call ni_order_status with order_id.

  ConnectorNo auth

• upload_createA

  PostproxyA

  Create a temporary file upload URL for sandboxed environments. Returns a `key`, an `upload_url`, and `expires_in` (seconds). Flow: (1) call this tool, (2) POST the raw file bytes to the returned `upload_url` (valid for `expires_in` seconds), which responds with `{"url": "https://..."}`, (3) pass that returned `url` in the `media` array of post_publish (or post_update). The upload host is `tmpfiles.postproxy.dev` — that domain must be whitelisted/allowlisted in the sandbox's network egress rules for the upload to succeed. Only use this when running against the remote (hosted) MCP server: if you are running the local (stdio) MCP server, do NOT use this — instead pass local file paths directly in the `media` array, which uploads them via multipart.

  ConnectorOAuth

• cycle_control_virtual_machineA

  Cycle MCPA

  Start, stop, or restart a virtual machine on Cycle. Waits up to wait_seconds for the job to finish and returns the VM's final state. Starting requires a hypervisor-capable server in the cluster (list_servers reports 'virtualization'); the first boot downloads the disk image and can exceed the wait — the job keeps running on Cycle. Log in with the VM's SSH keys or the root password Cycle generated at creation (retrievable for ~10 minutes afterward). stop and restart interrupt the running guest OS.

  Connector

  Destructive

  API key

• lavela.destroy_computeA

  lavelaA

  Permanently remove a server (machineId from lavela.project_overview): it stops running and being charged. Its own disk is lost; an attached volume (still billed), its daily snapshots and managed databases stay until you delete them or the project. Confirm the exact server with the user. Details: https://console.lavela.dev/docs/mcp#destructive-actions

  Connector

  Destructive

  API key