"A server for identifying bugs in the terminal related to cursor issues" matching MCP tools:

• leave_feedbackA

  AgentMarketplaceA

  Leave feedback about AgentMarketplace itself — bugs, confusing tools, feature requests. This is for feedback about the platform, not about a counterparty. There is no reputation or rating system here — that lives in AgentTrust. Args: access_token: AgentAuth bearer token (requires ``market.read``). message: Free-text feedback, up to 2000 characters. Returns: ``{"recorded": true}`` on success.

  ConnectorNo auth

• wsdot_get_ferry_terminalsA

  wsdot-mcp-serverA

  Returns all WSF ferry terminals with their numeric IDs, names, abbreviations, and coordinates. Call this first to resolve human-readable terminal names (e.g. "Bainbridge Island", "Seattle", "Kingston") to the numeric terminal IDs required by the schedule and space tools. The terminal list is small (20 terminals) and rarely changes.

  ConnectorNo auth

• publish_fileA

  LivePage · 活页A

  Publish an HTML / Markdown page or document straight to a WeChat-ready LivePage link; no terminal needed. Which upload route: terminal ⇒ SPACE CLI (create_cli_token first); no terminal and text files up to 2 MB in total ⇒ publish_file; anything else or unsure ⇒ create_upload_link. The link opens and forwards inside WeChat (links from WorkBuddy's built-in site publishing, `*.app.workbuddy.host`, cannot be opened inside WeChat); use this when the user wants it in WeChat. Use this when you have no terminal and the page is text files — HTML or Markdown pages and documents (no upload session to open first): pass the complete text content and the platform uploads it for you. Validation, content moderation (never released while moderation is unavailable), automatic release after approval or hold, and the result are exactly the same as finalize_upload. To add a version to existing pages pass proposal_id (find it with list_proposals first); to create new pages pass title (optional folder_id). One file: pass filename + content (.html / .htm / .md). When the page, styles and scripts are separate files, pass files: [{ path, content }] instead (one or the other): paths may include directories (e.g. css/style.css) and pages reference each other with relative paths; text files only (html / htm / md / css / js / mjs / json / svg / txt / csv), at most 50; the entry is manifest.entry, else index.html, else the only page. When a file is already at a public https URL (a cloud-drive public download link, a PDF link produced by another tool), pass { path, url } in files instead (e.g. [{ path: 'report.pdf', url: 'https://…' }]) and the platform fetches it — PDF, PPTX and images work: up to 50 MB each and 50 MB in total, at most 5 URLs, fetched within 30 seconds; only public addresses, and links that need a login cannot be fetched (fetch_failed, with fetch_* details in issues). UTF-8 text, up to 2 MB in total — anything larger is rejected with too_large and never truncated. The contents of images, PDF, PPTX and other binary files cannot be sent here: use a URL if there is one; otherwise without a terminal, use create_upload_link to give the user an upload page; with a terminal, use the SPACE CLI with create_cli_token. IMPORTANT: set hold=true whenever the user has not explicitly approved releasing this version, then give them the preview URL before publish_version. For a small edit (a typo fix) that should not notify anyone, pass quiet=true: workspace people and subscribers are not notified this time, and subscribers are notified on the next update. Keywords: publish · web page · webpage · link · share · share to WeChat · WeChat link · html · pdf · markdown · upload · LivePage · proposal.

  ConnectorAPI key

• get_setup_kitA

  NEXUS AGIA

  Return the optional setup kit for agents that run on the user's own machine (Claude Code, Cursor). The kit contains four hooks (recall at session start, recall on each prompt, sync of session recaps, and the inbox of messages from other agents), the settings.json block, a usage policy, and an idempotent bash script that installs them. With the hooks installed, memory is recalled and stored automatically. Without them, NEXUS only has what the agent stores through its tools. Calling this tool only returns the kit; nothing is installed until the script is run. Running it writes the hooks and the policy file on the user's machine, declares the hooks in the client's settings, and loads the policy into the agent's instructions (a line in CLAUDE.md for Claude Code, a .cursor/rules file for Cursor), so installing is the user's decision. It does not apply to chat clients (Claude web or desktop, ChatGPT). Side effect: on an OAuth connection, the call issues the hooks credential and embeds it in the script. This works once, because a secret that was already shown is not returned again. On a plain `nxa_` token connection it does not issue a credential, and an account owner must issue one. `steps` says which case applies. Args: formato: "script" (default) for the bash installer plus steps, or "files" for the same files as text, for clients without bash. It is ignored for Cursor. client: "claude-code" (default) or "cursor". Cursor gets a session-start hook and a turn-recap hook. It has no per-prompt recall, because Cursor's beforeSubmitPrompt cannot inject context.

  ConnectorAPI key

• request_terminal_accessA

  SynopticA

  Join the waitlist for early access to the Synoptic trading terminal (beta) for the signed-in account. Sets terminalAccessRequested, which get_me reports; repeating the call changes nothing. Does not grant access, open a support ticket or place trades. Use request_feature for other product requests.

  ConnectorNo auth

• arena_pingA

  Dead Brands Bot ArenaA

  Ping and auth check. WHEN: auth/connection smoke test (no game side effects). Differs from arena_get_state. Echo test: returns {status:"pong"} plus whether your auth (Bearer header, key arg, or guest_token) is valid. Use it first to separate connection/auth bugs from game bugs. Never echoes your key. Free, no side effects. Example: {"message":"hello"}

  ConnectorNo auth

• resolve_kb_idA

  fixflowA

  FIRST STEP in any troubleshooting workflow. Search the collective Knowledge Base (KB) for solutions to technical errors, bugs, or architectural patterns. Uses full-text search across titles, content, tags, and categories. Results are ranked by relevance and success rate. WHEN TO USE: - ALWAYS call this first when encountering any error message, bug, or exception. - Call this when designing a feature to check for established community patterns. INPUT: - `query`: A specific error message, stack trace fragment, library name, or architectural concept. - `category`: (Optional) Filter by category (e.g., 'devops', 'terminal', 'supabase'). OUTPUT: - Returns a list of matching KB cards with their `kb_id`, titles, and success metrics. - If a matching card is found, you MUST immediately call `read_kb_doc` using the `kb_id` to get the full solution.

  ConnectorNo auth

• wsdot_get_terminal_spaceA

  wsdot-mcp-serverA

  Returns real-time drive-up and reservable vehicle space available at WSF terminals for upcoming sailings. Use for "will I make the ferry?" or "how full is the next sailing?" questions. Optionally filter to a specific terminal by ID (use wsdot_get_ferry_terminals for the ID). driveUpSpaceCount is the key field — zero means the drive-up lane is full. Destinations are arrivingTerminalIds, not the itineraryLabel string: a sailing can serve several terminals, and those IDs are what wsdot_get_ferry_schedule accepts. Results are paged by terminal (default 5, max 20): offset/limit select whole terminals and totalCount counts matching terminals, not sailings — every sailing of a returned terminal is included, so page size varies with how many departures each terminal carries.

  ConnectorNo auth

• calculate_dcf_valueA

  Zyberno stock valuationA

  Runs a two-stage discounted cash flow on numbers you provide and returns the fair value per share, the margin of safety against the price you gave, and how much of the value sits in the terminal stage. Cash flow grows at your growth rate for the stage-one years, then forever at your terminal rate, with the terminal value from the Gordon Growth Model discounted back over the stage-one years. Use when the user wants to value a company under their own assumptions, test how sensitive a valuation is to the discount or growth rate, or check the arithmetic of a DCF they are building. Do not use it to look up what a company is worth on Zyberno's own assumptions, which is get_stock_valuation and uses a different, fade-based model; the two will not agree and are not meant to. This computes your assumptions, it does not endorse them. The output is arithmetic, and a two-stage DCF is highly sensitive to the discount and terminal rates, so treat a single result as one point rather than an answer.

  ConnectorNo auth

• create_support_ticketA

  BorealHostB

  Open a support ticket with the BorealHost team. Use this to escalate platform-side problems you cannot fix with the available tools (billing issues, infrastructure faults, API bugs). A human answers every ticket — poll get_support_ticket for updates. Requires: API key with write scope. Args: subject: Short summary (max 200 chars) message: Full description (max 20000 chars) category: Optional (e.g. "technical", "billing") site: Optional site slug the ticket concerns Returns: {"id", "subject", "status", "message": "Ticket created..."}

  ConnectorNo auth

• dreamagent_get_chat_statusA

  DreamAgent CloudA

  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

• 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

• ado_query_workitemsA

  ALM X++ MCP ServerA

  AZURE DEVOPS ONLY -- Query Work Items (Bugs, Tasks, FDDs, User Stories, CRs) in Azure DevOps. [~] PRIORITY TRIGGER: use this tool when the user mentions 'FDD', 'RDD', 'IDD', 'CR', 'Task', 'Workitem', 'Work Item', 'Bug', 'User Story', 'Feature', 'Issue', 'ticket', 'sprint', 'backlog', 'DevOps', 'liste des tâches', 'show tasks', 'find bugs', '#1234', 'WI#'. NEVER use this tool for: D365 labels (@SYS/@TRX), X++ code, AOT objects, tables, classes, forms, enums, error messages, 'c\'est quoi le label', 'search_labels', 'libellé', 'label D365'. For labels -> use search_labels. For D365 code -> use search_d365_code or get_object_details. Shortcuts: 'bugs' (all active bugs), 'my bugs' (assigned to me), 'recent' (updated last 7 days), 'sprint' (current iteration). Or pass any WIQL SELECT statement or a free-text title search. Use '*' with filters only. Returns max 50 work items with ID, title, type, state, priority, area, assigned-to. Requires DEVOPS_ORG_URL + DEVOPS_PAT env vars.

  ConnectorNo auth

• list_issuesA

  FlowseryA

  List issues the AI found while analyzing session recordings: bugs, broken flows, and UX problems, deduplicated across sessions and ranked by severity (or by last seen with sort recency). Each row has title, severity, status, sessions affected, and first/last seen; the response also carries site-wide open, in_progress, and resolved counts plus pagination.total. Start here for 'what is broken', then call get_issue with an id for occurrences, steps to replicate, and comments. Suspended issues are hidden unless status is suspended, so an issue that vanished was probably suspended, not deleted. On a free trial only the first 10 issues are listed and counted. Limit defaults to 100 (max 1000). Requires websiteId or domain with a workspace token.

  ConnectorOAuth

• list_my_issuesA

  BoardMarkA

  Open issues assigned to you in every project you can access, most recently updated first (D66 "My work"); on Sales & Billing projects also the unpaid installments of deals whose `owner` field is you (D130 (7)). With an agent account's token (D144): the issues assigned to the agent (`agt_…`), not to its owner. "What's on my plate?" — the issues assigned to you (the token's user) in EVERY project you can access, in one call, most recently updated first. Open issues only (not in a done-category status) unless `include_done: true`. Each item is an issue summary (`key`, `title`, `type`, `priority`, `status`, `assignee`, `points`, `sprint`, `version`, `updated_at`, …) plus `project_key` and `project_name`. Paginated with `cursor`/`next_cursor`. Use this instead of calling search_issues with `assignee=me` project by project; use search_issues when the user means one project or needs other filters. Call get_issue before changing any of these issues. Sales & Billing projects (D130): the installments (`type: subtask`, `parent` = the deal) of deals you own (`fields.owner`) are listed too, so an installment that is due or overdue on your deal shows here — read its `flags` (bill_due, due_soon, overdue).

  ConnectorOAuth

• auditA

  mcpA

  Perform comprehensive audit of a website URL. Fetches the URL content ONCE and provides a combined report with: - Classification: category, subcategory, language, sentiment, demographics - SEO Analysis: score, grade, issues, recommendations - EEAT Analysis: experience, expertise, authoritativeness, trustworthiness scores - AEO Analysis: AI answer engine optimization score, metrics, issues, signals (includes full Citation Readiness analysis in the nested 'citation' key) - Advertiser Matching: best-fit advertising networks with scores - Similar Sites: competitor/related sites from the same category This is more efficient than calling classify_url, analyze_seo, analyze_eeat, analyze_aeo, select_advertiser, and find_similar_sites separately as it only fetches the page once. Args: url: The website URL to audit (e.g., "https://example.com"). Returns: Comprehensive audit report with: - url: The analyzed URL - classification: Category, subcategory, language, sentiment, demographics - seo: Score, grade, issues, recommendations - eeat: EEAT score, grade, category scores, issues, signals - aeo: AEO score, grade, metrics, issues, signals (includes citation results) - advertisers: Matched advertising networks with scores - similar_sites: Related sites from the same category (up to 10) - cached: Whether result was from cache

  ConnectorNo auth

• get_xdala_session_start_resultA

  XGR MCP GatewayB

  Return terminal xDaLa session start result, lean result summary, and audit events. Read-only preparation/result lookup only; the MCP does not sign, submit, or execute, and users sign locally in Workbench/wallet/local signer. For completed handoffs, prefer result.results[].owner/sessionId/pid over XRC-729 contract owner facts when identifying the actual session owner/starter.

  ConnectorNo auth

• particle_podcast_list_relatedA

  particle-proA

  List the shows most related to a podcast, best first — "shows like this show". Each result carries the related show's slug, a calibrated score in (0,1], and a coarse band (strong: same beat and audience; moderate: overlapping subject or audience; weak: a loose connection) to branch on. Add `include: ["basis"]` to see WHY each pair is related: content similarity of recent episodes, shared topics, shared guests (named), same publisher, shared sponsors — use it to explain a recommendation or to keep only pairs related for the reason you care about (shared guests for booking, content for media planning). Related sets are precomputed per show from its transcripts, topic profile, guest roster, network and advertisers, restricted to the show's language. Only shows above a relatedness floor are listed, machine-generated and farmed feeds are never listed, and a publisher's duplicate feeds of one show appear once. An empty FIRST page is not an error: its `coverage` says whether the set is not computed yet, nothing cleared the floor, or the request's filters and the default policy removed everything; an empty page reached through a cursor is simply the end of the list. Not a topic browser: for shows that COVER a topic use `particle_podcast_resolve` with `topic_slug`. Not a guest lookup: for where a person has appeared use `particle_podcast_get_guest`. Not advertiser co-occurrence: use `particle_podcast_get_sponsors`. Every related show's slug feeds `particle_podcast_resolve`, `particle_podcast_list_episodes` and the other podcast tools; person slugs in the basis feed `particle_podcast_get_guest`, topic slugs feed `particle_podcast_resolve`'s `topic_slug`. For the five most related shows inline on a resolve, pass `include: ["related"]` to `particle_podcast_resolve` instead of calling this tool.

  ConnectorOAuth

• run_eventsA

  Mostly RightA

  Opens the run's event stream, collects up to max_events, and returns as soon as the run reaches a terminal event or wait_seconds elapses — whichever comes first. This is how you watch a build without polling. Example: {"run_id": "…", "from_seq": 0, "max_events": 50, "wait_seconds": 5}. Returns {events: [{seq, type, at, stage, message, rows, bytes, failure_code}], next_from_seq, run_status, terminal}. Call it again with from_seq set to next_from_seq to continue. wait_seconds is capped at 20 and max_events at 100; terminal true means the run is finished and there is nothing more to wait for.

  ConnectorNo auth

• create_uploadA

  ShapesodaA

  Creates a one-time upload link for a local image file (valid 10 minutes). Upload the file with the returned curl command, then pass upload_id to vectorize. Only for agents whose terminal can reach shapesoda.com (Claude Code, Cursor and similar); in Claude.ai and other chat apps the sandbox cannot upload there, so call open_editor instead.

  ConnectorNo auth

• pause_runA

  LiveGraphA

  Pause a run at the next step/hop boundary — resumable via resume_run, unlike cancel_run which is terminal. The in-flight model call finishes; a mid-tool-loop pause parks a checkpoint the resume continues in place, a between-hop pause parks the next hop before it starts. Requires editor access on the run's graph; already-parked or terminal runs error.

  ConnectorNo auth