"Information about cursors or cursor-related tools" 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

• get_contextA

  Vilix AIA

  Load the last few recent messages and semantically related past turns. Call this before you compose your reply. Pass the user's latest prompt only. Vilix runs relevance retrieval internally. For anything more specific you may also call the optional search_semantic / search_keyword / recent_messages tools (e.g. when the user names a source like ChatGPT). Every retrieved item carries an ISO timestamp — when two items disagree about a changing fact (a plan, a status, a decision), the NEWEST timestamp is the latest known value. Related turns may include `context_before`/`context_after` (the adjacent turns) and the payload may include `also_related`: additional nearby matches as compact snippets, newest first — check it before concluding a fact is unknown or unchanged. `chat_id` — pass null (or omit) on a brand-new conversation to also receive `user_rules`, `system_behavior`, `active_projects`, and `active_project_state`. Pass the chat_id returned by a prior `save_turn` to skip those — they are already in the chat's own context from turn 1 and re-injecting wastes tokens. `recent_messages` and `related_conversations` are always returned (they're the cross-tool memory bridge). `attachment_context` (optional, default "") — if the user's CURRENT message has an attachment (file, image, code paste, screenshot OCR), pass a short plain-text summary of it here so retrieval can match on the attachment topic in addition to the bare prompt. Pass the SAME summary to `save_turn` for this turn. Empty = no attachment, ignored.

  ConnectorOAuth

• manage_feed_consumersA

  smry ProductA

  create: Save a where predicate and let smry retain one processing checkpoint. New consumers start at the current high-water mark, so they receive future discoveries rather than replaying history. For history, create the Consumer first, query the historical window separately, then poll; that order closes the query/create race. Create one per independent processing loop, not per source. Retrying the same case-insensitive name and predicate returns the existing Consumer; the same name with another predicate is a 409. Required fields: name. Example: {"action":"create","name":"Engineering briefing","where":{"collection":["Research"]}} list: List each saved consumer, its opaque acknowledged_cursor, delivery and acknowledgement timestamps, and how many matching entries are waiting past that checkpoint. Required fields: none. Example: {"action":"list"} ack: After processing every event returned by getFeedChanges for this consumer, acknowledge that response's next_cursor. Crashes before ack cause safe redelivery; stale, foreign, and invented cursors are rejected. Required fields: id, cursor. Example: {"action":"ack","id":7,"cursor":"<next_cursor from get_feed_changes>"} delete: Remove only the saved predicate and checkpoint. Followed sources, entries, and human read state are untouched. Required fields: id. Example: {"action":"delete","id":7}

  Connector

  Destructive

  No auth

• compras_listar_promptsA

  MCP Compras.gov.brA

  Lista os MCP Prompts disponíveis com nome, descrição e argumentos. Tools de descoberta para clientes (como o Claude.ai web) que ainda não expõem UI para prompts. Em Claude Desktop / Cursor / MCP Inspector, prompts aparecem em UI dedicada — esta tool é um caminho alternativo, não substituto. Use depois `compras_obter_prompt(nome, argumentos)` para renderizar um prompt específico. Retorno: { "total": int, "prompts": [ { "nome": str, "descricao": str, "tags": [str, ...], "argumentos": [ {"nome": str, "descricao": str | None, "obrigatorio": bool}, ... ] }, ... ] }

  ConnectorNo auth

• get_wedding_informationA

  The Hill KinabaluA

  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

• search_sec_filingsA

  mtgmon Mortgage AnalyticsA

  Search SEC EDGAR filings of mortgage-related public companies (lenders, servicers, mortgage REITs, insurers, GSEs) that mtgmon has summarized. Newest filing date first. Use for: finding a company's 10-K, 10-Q, 8-K, or other filings by ticker, CIK, form type, keyword, or date window, and getting the filing_id to pass to get_sec_filing. Do not use for: full filing text (only summaries are stored) or companies outside the mortgage sector. Returns data.filings (at most `limit` rows of {filing_id, accession_number, filer_cik, form, filing_date, company_name, description, summary_status, summary_excerpt, summary_created_at, edgar_url}) and data.next_cursor (pass back as `cursor` for the next page; null when exhausted; meta.truncated is true when more pages exist). Only filings whose summary processing finished are listed; summaries are machine-generated and should be checked against edgar_url. Behavior: read-only, no auth or API key, no PII, idempotent and safe to retry. The public endpoint https://mtgmon.com/mcp allows about 60 requests/min and 250 tool calls/day per client IP. Result shape is {data, meta}; meta carries available, as_of, source_scope, weighting, units, cache_status, caveats, and truncated. If meta.available is false the data is unavailable or the cache is still warming (retry after a few seconds); never report it as zero.

  ConnectorNo auth

• check_mcp_serverA

  MCP Surface LintA

  Statically audit an MCP tool surface from a public HTTPS URL or tools/list snapshot. Returns deterministic scores and findings without invoking any target tool or making LLM calls. When the user asks to check another installed MCP server, read that server's complete tool definitions from client context and pass them as snapshot (MCP `name` or Cursor-style `tool` both work; do not use file paths or $ref). If those definitions are unavailable, ask the user for its public endpoint or tools/list JSON instead of inventing an audit.

  ConnectorNo auth

• cisa_get_alertsA

  cisa-cybersecurity-mcp-serverA

  List what CISA has published recently — its combined advisory feed, its alerts feed, or its ICS advisory feed. Cursors continue within the current 30-item rolling window; upstream provides no pagination, history, or date-range query. The window's coverage varies from about a week to about two months depending on the feed. For ICS advisory history beyond the window, use cisa_search_ics_advisories, which covers the full corpus back to 2010.

  ConnectorNo auth

• get_demo_health_recordA

  FinchNode Synthetic Health RecordsA

  Get any mix of demographics, medications, conditions, labs, vitals, allergies, immunizations, encounters in one call — prefer this over several single-category tools. Builds a record view using the authenticated API normalized data shape (schemaVersion 2). Fictional patients only; pick one with scenario. Consent and sync are simulated, with no usable change cursor. Empty categories describe the fixture only.

  ConnectorNo auth

• ui_builder_await_commentsA

  Compose Preview CatalogsB

  Wait for the discussion to move past `afterSequence` and return it, rather than polling for it. Returns as soon as anybody — a designer in the browser or another agent — posts, resolves or deletes; returns a `timedOut` reply if nothing happens within `waitSeconds`, which you answer by calling again with the same cursor. This is how you hold a conversation about a design: post, wait, read, act.

  ConnectorNo auth

• 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

• awareness_search_knowledgeA

  Awareness — Memory, Knowledge & Agent MarketsA

  Search the PUBLIC Awareness knowledge graph — 1,000+ sourced scientific papers. Use this when the user (especially a researcher or a research agent) asks for peer-reviewed findings: "latest evidence on X", "highly-cited papers about Y", "what does the literature say about Z". This is NOT a memory tool — it does not read the user's private memory, and it needs no per-user API key, so it works even when Awareness memory is not configured (the MCP connection itself still needs its own token). Coverage: condensed-matter, quantum-information, materials, machine-learning, renewable-energy, chemistry, biology, medicine, neuroscience, computer-science (2022-2026, cited >= 50), plus a business supply/demand domain. What comes back (anonymous preview mode): title, snippet (preview), confidence, source_ref (DOI), citation_count, domain/topic, and a detail page URL. Full content is NOT in the preview — tell the user it is paid retrieval via POST /api/v1/public/retrieve with an API key (see https://awareness.market/en/knowledge for the KaaS product). Args: query: Natural-language research question or keywords (2-1000 chars). domain: "science" (default) or "business". topic: Optional sub-topic slug, e.g. "medicine", "condensed-matter", "supply-chain". Empty = search all topics in the domain. top_k: Max results, 1-20 (default 5; anonymous callers are capped at 3). include_graph: When true, also return same-topic related items. Returns: {"results": [{id, title, snippet, confidence, source_ref, citation_count, domain, topic, url}], "related": [...], "total": int, "mode": str} `mode` is "preview" (anonymous) or "full" (authenticated).

  ConnectorNo auth

• arena_lobby_readA

  Dead Brands Bot ArenaA

  Read the lobby. WHEN: read lobby chat (delta via since). Differs from arena_wait (cheap long-poll, no text) and arena_lobby_say (write). Poll no faster than every 5 s, or better, call arena_wait (long-poll, no chat text) and read only when it says lobby_new. Read lobby messages (public). Returns the latest page (default 20, max 50) plus next_since. DELTA POLLING: pass since=<the next_since from your previous read> and you get ONLY messages newer than that cursor (an empty list when you are caught up) - poll with the cursor instead of re-reading the full history every time. since also accepts a legacy ms-epoch or ISO timestamp. Prefer live push? Open the SSE lobby stream: GET https://mcp.deadbrands.co/arena/lobby/stream (or GET /arena/mcp with Accept: text/event-stream), resuming with the Last-Event-ID header or ?since=<cursor>. Example: {"limit":20}

  ConnectorNo auth

• list_watched_mcp_serversA

  apiwatchA

  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

• workflows_connections_manageA

  9botA

  Reads and manages API, CRM, and synchronization connections used by Workflow steps. Use workflows_design for step definitions and workflows_runs_manage for an existing run. import_openapi creates an unsaved local draft, while write and revoke change protected connection state; CRM run only queues work and does not prove completion. Never place tokens, secrets, encrypted cursors, or internal hashes in presentation. For a preview, set input.preview=true; preview never applies the mutation. When confirmation is required, repeat the same operation and parameters with the returned input.confirmation_id.

  Connector

  Destructive

  OAuth

• get_recent_ideas_summaryA

  BuzzbergA

  Return the complete recent-ideas report in one call. Call once with window (default 24h) and, only when the user asks for them, sections, sectors, source_type, direction, table_limit or detail_limit. Do not pass delivery, limit, cursor or offset. The server returns the whole report in one response and ignores delivery=paged on a first call; it pages only an oversized report. Only when a response has pagination.has_more=true, call again with its exact next_cursor alone until has_more=false; retain every page. Only the final page includes summary_context. Ranking and selection are final on the server. Present the tables as supplied and summarize thesis prose only for the detailed tickers, without grading theses, rejecting rows or recalculating scores. Read agent_guide and summary_context.analysis_instruction in full. Defaults: six sections, ten table rows and three unique details per section. One selected section renders one table without tabs, for example sections=["alpha_calls"], sectors=["Information Technology"]. The server applies sectors before loading ideas and skips unselected rankings. All six sections require a finite positive entry price for the instrument. Only selected detail tickers load thesis prose; detail_limit=0 needs none. Alpha ranks are final: 30% attention, 30% support, 25% price, 15% authors. Counts cover the full sector/source/window scope. direction selects ranking rows without removing opposing counts or evidence: Alpha/Consensus use the dominant direction, mention tables require a matching author stance within the query window (Spike also the matching side), First Calls uses the selected call's direction and Shorts a current author with that stance. Every table is ranked exactly like the site's Market Radar. Context 12.0.0/report format 9.0.0 includes effective report_options, selected section_order, full presentation rules, stored prices/returns/peaks and links. Detailed tickers do not repeat across selected sections. No external prices or bias/history recalculation is required. ticker_group_rows carry only the report tickers with their evidence (data_projection=report_tickers_with_evidence); summary_context.overview counts the whole window. Use get_recent_idea_candidates for a complete research export. Cursors pin all filters and report limits. The entire publication-time window must be within the last 7 days of current server time. Older or partly older windows are rejected, including signed cursor continuations and cached responses. Start a new request with a newer as_of or a shorter window if a snapshot ages out during pagination. Args: window: Exact lookback: 1h, 6h, 12h, 24h, or 1d. Default 24h. cursor: Leave empty; only the exact next_cursor while has_more=true. as_of: Optional ISO-8601 end boundary for a requested historical cutoff; the entire window must remain within the last 7 days. source_type: Optional twitter, youtube, newsletter, or reddit filter. direction: Ranking direction: long, short, avoid, close, trimmed, watch, neutral, or empty. delivery: Leave unset. paged is ignored on a first call. limit: Leave unset. Sizes only server-initiated fallback pages (1–200 ticker groups); NOT table size or a scan bound. offset: Deprecated; leave unset. sections: Nonempty selection of alpha_calls, top_mentions, mentions_spike, consensus, first_calls, shorts. Omitted/null selects all; canonical order. sectors: Sector names from the reviewed DB taxonomy; multiple names use OR. Case-insensitive; IT aliases Information Technology. Omitted/empty means all sectors, including unclassified tickers. Unknown names return the available sector names; Crypto is a sector, not an asset-type filter. table_limit: Rows per selected table, 1–10, default 10. detail_limit: Unique detailed tickers per selected section, 0–table_limit, default 3. Zero returns tables only; fewer qualifying rows stay fewer.

  ConnectorOAuth

• get_subreddit_postsA

  Weir: Reddit and X (Twitter) dataA

  List a community's posts: hot, new, rising, top, or controversial. A community's own listing, with no keyword: everything new in r/saas, or this week's top posts in r/startups. Use this rather than search when the community is the filter — Reddit's search needs a query and cannot express "everything". `name` also takes `popular`, `all`, or several communities joined with `+`, which reads them as one listing in a single call (and is billed as one request). Pages are newest-cursor-forward and stop at about 1,000 posts, Reddit's own ceiling, where `nextCursor` becomes null. NSFW posts are left out unless `includeNsfw=true`; how many were left out is in `meta.omittedNsfw`. A community that does not exist, or is private, banned, or quarantined, is a 404 whose `details.reason` says which. Costs 1 credit + 3 credits per post returned. When meta.nextCursor is set, call again with cursor set to it for the next page.

  ConnectorOAuth

• get_events_sinceA

  SkydropxA

  Pull the events this server recorded for the connected account after a cursor, as a hash-chained feed to poll instead of receiving webhooks. It holds no carrier tracking scans and no live shipment or order state: use track_shipment for a shipment's carrier events, and list_shipments or list_orders for current state. Start without `cursor`, then pass back the `cursor` of each response; an empty page with an unchanged cursor means nothing new, and an account may have no events at all. `cursor` is the integer `seq` of the last event you saw; `limit` (default 100, at most 1000) caps one page, so raise it to catch up a long backlog in fewer calls. The feed is answered from this server's own records, never from carriers, and reading it changes nothing. Returns the page of events; `chain_valid` false means the page or its link to your cursor failed hash verification.

  ConnectorOAuth

• find_pulore_case_studiesA

  Pulore App PlannerA

  Use this only when someone asks about Pulore's own work or experience, for example whether Pulore has built something like their idea. Finds published Pulore case studies related to a topic, matching industry, platform, services and technology tags, and returns each project's summary and link, with timeline, team size and results where the case study publishes them. Searches the case-study files bundled with this server; it does not browse or modify external sites. Returns nothing when no project matches. Don't use it to find examples of other companies' products.

  ConnectorNo auth

• how-toA

  Fast.ioA

  Built-in product help — a natural-language "how do I…" question about Fastio returns a grounded, product-aware answer (or a short clarifying question) in one call. EXPLAIN-ONLY / ADVISORY: it returns GUIDANCE TEXT and performs NO platform action (it will not create shares, move files, or change anything); the actions themselves are on the other tools. Answers are grounded in Fastio's own how-to knowledge AND phrased in terms of these MCP tools — they name the concrete `<tool> action="…"` calls, in place of guessed endpoints or exploratory calls. Q&A over the user's uploaded files (RAG) is the `ai_manage` tool; `how-to` answers questions about Fastio ITSELF. Costs no credits; needs only an authenticated user (no org needed). action='describe' gives the full action/param reference.

  ConnectorNo auth

• get_changesA

  OnlyWorldsA

  Return the delta feed for the world named by your API-Key header: every element created/updated (`op: "upsert"`, full body) or deleted (`op: "delete"`) since `since_cursor`, in apply order, in pages of `limit` (default 25, max 1000). Entries carry FULL element bodies — a default page stays inside any client's token budget; measured worlds ran ~1.5-2k chars PER ENTRY, so raise `limit` only if you truly need bigger pages, and prefer paging with the cursor. Omit `since_cursor` (or pass "") to start from the beginning of the feed — for a big world that is a multi-page walk, not one response. Pass the returned `cursor` back as `since_cursor` to get the next page (or, later, only what changed since); treat the cursor as OPAQUE. `has_more` true means page again with the new cursor. Requires a READ or WRITE API-Key. This mirrors `GET /api/v2/changes`. `after` is for stepping into a world without a kept cursor: an ISO 8601 date and time (e.g. "2026-10-21T09:00:00Z"; no offset is UTC), and only what changed at or after it comes back (an upsert whose `updated_at`, or a delete whose `deleted_at`, is at or after it), so "the last day" is one call. It is a filter, not a position: the order, `cursor` and `has_more` are as without it; to read the whole window, pass `cursor` back as `since_cursor` with the same `after`. The cursor is still the exact form (every change once, in order): keep it if you will come back. A guest key gets only what it may see, and no deletes: when its view of the world changes, its cursor stops working and this tool says to pull again from the start (omit `since_cursor`); keep what you hold that the new walk does not name. Where the server has the hidden mark on, a contributor's cursor works the same way, and every delete says why (`reason`: `deleted`, or `hidden` for an element hidden from you: drop your copy). There the reset says why too: "reason role" (your role or membership changed: keep what the new walk does not name) or "reason view" (what you may see changed: drop it), and each page carries `epoch_reason` beside `epoch`. Never empty a copy on your own.

  ConnectorNo auth