"Information about pages or the term 'page'" matching MCP tools:

• smithsonian_browse_categoryA

  smithsonian-mcp-serverA

  Browse Smithsonian objects within one exact category — a single museum (mode "museum"), culture, indexed date term (mode "period"), object type (mode "medium"), or subject term (mode "topic"). The value must be an exact indexed category term, not free text: resolve museum, culture, period, and topic vocabulary with smithsonian_list_terms first (object_type is not enumerable there — harvest it from smithsonian_search_objects results, and treat each casing as its own category, since a harvested object_type covers only the casing it was written in). Returns the category total count, a page of matching objects, and a museum breakdown of that page; page the full category with start and rows. For open-ended or topic discovery, start with smithsonian_search_objects instead.

  ConnectorNo auth

• search_shop_policies_and_faqsA

  okun-koneosaA

  Search Okun Koneosa's shop policies and terms. Covers delivery terms, privacy policy, terms of service, the consumer right of withdrawal / returns, and company information. Use this instead of guessing when the customer asks about delivery times, shipping costs, returns, warranty or how their data is handled. Args: query: Finnish keyword, e.g. "palautus", "toimitusaika", "takuu", "toimituskulut". Leave empty to list all sections. limit: Maximum sections to return (1-20, default 5). Returns: JSON with: - sections: each with page, page_title, heading, content and url - total: how many sections matched - query: the term that was searched Notes: - Content is split by heading, so you get the relevant paragraph rather than a whole page. Always cite the `url` so the customer can read the full terms. - These are the shop's own terms. They do not override Finnish consumer law.

  ConnectorNo auth

• web_extractA

  x402 BazaarA

  Up to 5 pages in one call — including the JavaScript ones — Pass up to 5 URLs (comma-separated) and get each page back as clean text with its title. Renders pages that build their content in the browser, which a plain server-side fetch cannot read at all — so it covers the SPAs, dashboards and app pages that url-extract deliberately refuses. Returns partial success: pages that fail come back in a `failed` list with the reason, and a call where every URL fails is not charged. For a single static page, url-extract is cheaper. Required input: urls. Priced $0.01 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No wallet or API key required.

  ConnectorNo auth

• get_output_pageA

  ALM X++ MCP ServerA

  Retrieve the NEXT page of a previously PAGINATED tool output. When a tool result is too large for a single response, it is split losslessly into ordered pages — the footer of each page gives you a `token` and the next `page` number. Call this tool with that token to read the continuation; nothing is dropped, so you can walk every page in order and reconstruct the full result. Pages are cached only briefly (the last few large results). If the token is unknown or expired, re-run the original tool to regenerate it.

  ConnectorNo auth

• share_pagesA

  twocentsA

  Publish a multi-page set — an entry page plus the pages it links to — into one room as a single atomic operation. Either the whole set lands or nothing changes, so a reviewer never opens a page whose links point at pages that were never stored. Use this instead of calling share_page N times whenever you have more than one page. Note the ceiling: a room is a review set, not a host — it holds 200 pages and 6 MB total. For a large generated corpus, share the entry points a human would actually read and link out to the rest; nobody pins notes on four hundred pages. If the pages are already files on disk, prefer the uploader — it reads them from the folder instead of making you emit every byte: curl -fsSL <origin>/agent.mjs -o .twocents/agent.mjs && FBL_ROOM=<room> node .twocents/agent.mjs --publish <dir>

  ConnectorNo auth

• merge-designsA

  CanvaA

  Perform structural page operations on Canva designs: combine pages from multiple designs, insert pages, reorder pages, or delete entire pages. This tool can: 1. Create a new design by combining pages from one or more existing designs 2. Insert pages from one design into another existing design 3. Move or reorder pages within a design 4. Delete (remove) entire pages from a design Use this tool (NOT start-editing-transaction) when the user wants to: - Delete or remove one or more pages/slides from a design - Reorder or rearrange pages/slides within a design - Combine, merge, or stitch together multiple designs - Copy or insert pages from one design into another Do NOT use this tool for editing content within pages (text, images, etc.) — use start-editing-transaction for that. CRITICAL: You MUST ALWAYS ask the user for explicit confirmation before calling this tool, regardless of the operation type. Show them a summary of exactly what will change and ask "Would you like me to proceed?" Wait for their clear approval, then call this tool immediately. MANDATORY DELETE CONFIRMATION: If ANY operation in the list is a delete_pages operation, you MUST follow this protocol with NO exceptions — regardless of whether the pages are empty, have content, or any other condition: 1. Show a summary of ALL operations, marking each deletion as: "⚠️ Delete page(s) [X] — CANNOT BE UNDONE" 2. Tell the user: "To proceed, please type exactly: I approve the deletion" 3. ONLY call this tool if the user types the EXACT phrase "I approve the deletion" — do NOT accept any variation such as "yes", "ok", "approve", "I approve", "go ahead", "delete them", or any other paraphrase 4. If the user types anything other than the exact phrase, ask them again to type it exactly For insert_pages and move_pages only (no deletes), a simple "Would you like me to proceed?" confirmation is sufficient. Operations are applied sequentially. Page numbers are 1-based and evaluated at the time each operation runs. The tool automatically polls for job completion and returns the final result.

  Connector

  Destructive

  OAuth

• query-docsA

  ClearPolicyA

  Read or search ClearPolicy documentation pages via a sandboxed virtual filesystem (rg, cat, head, tree, ls, etc.). Prefer search-docs for conceptual questions; use this when you need exact page content, keyword/regex matches, or docs structure. Paths are documentation pages (e.g. /guides/reminders.mdx), not the customer organization.

  ConnectorOAuth

• submit_feedbackA

  ContinueOps Public MCPA

  Report that a public ContinueOps page or MCP tool response is incorrect, outdated, incomplete or confusing, so the team can fix it. Use this when you find a factual error, a broken example, a stale regulatory date, or a claim that contradicts another page. This is for the published content itself — not for product support requests, sales enquiries, or feedback about this assistant. Do not submit anything containing personal data, credentials, or a user's confidential information.

  ConnectorNo auth

• getRedditPostWithCommentsByIdA

  Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ)A

  Get Reddit post by ID with its comments. Returns both the post data and comments in a single response. FAST (default, omit responseType or responseType="fast"): Returns post and up to 300 comments directly (use limit param to reduce, e.g. limit=5). Auto API fallback for fresh data. Results include guidance for full mode. PAGING (responseType="paging"): Async paginated results (100 comments/page), returns operationId for polling via checkOperationStatus. Supports pageNumber/tableName for subsequent pages. RESPONSE STRUCTURE: Returns { results: { post: {...}, comments: [...] }, count, guidance }. PAGING MODE DETAILS: FIRST CALL: Omit pageNumber and tableName. Creates cached table for comments, returns page 1 with post data and pagination metadata. SUBSEQUENT PAGES: Use tableName from first response with pageNumber (2, 3, etc.) to fetch additional comment pages. Post data is NOT returned on subsequent pages. FIELD SELECTION: Use postFields for post data optimization, commentFields for comment data optimization. First searches database for both post and comments, then external API if data is stale or missing. This is a safe, read-only tool for analyzing searchable information.

  ConnectorOAuth

• list_pagesA

  California Justice WatchA

  Return the canonical list of pages on cajusticewatch.com — slug, URL, label, and purpose. Use this when the user asks about features/pages/tools of the site, OR when you need to recommend a page, OR before saying "I do not have access to X" — the page may actually exist.

  ConnectorNo auth

• extractA

  SofyaA

  Fetch a webpage and extract specific information using AI. Use this when you need structured data from a page (e.g. pricing, specs, contact info) rather than the raw content. Costs 10 credits. If the page has no usable text (empty or JavaScript-rendered body), the model is NOT called: content comes back empty and usage.low_content is true, rather than a fabricated answer. Gate on usage.low_content (or usage.content_chars) to detect pages you cannot ground on. Returns: content (the extracted text), url, credits_used, credits_remaining, usage (input_tokens, output_tokens, content_chars, low_content). Args: url: The URL to extract from prompt: What information to extract (e.g. "list all pricing tiers with features" or "extract the author name and publication date")

  ConnectorNo auth

• get_security_infoA

  Fluentive MCPA

  Returns Fluentive's security, privacy, and compliance information. Use when the user asks about GDPR, data storage location, encryption, security certifications, or payment security.

  ConnectorNo auth

• search_n_topA

  docsA

  Search across the nTop knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about nTop, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. `head -200 /api-reference/create-customer.mdx`).

  ConnectorNo auth

• view_transcriptionA

  Open ArchivesB

  Open one or more transcribed document pages in an interactive deep-zoom viewer with the transcription text alongside. Pass page identifiers returned by search_transcriptions / browse_transcriptions (form <ISIL>_<archive>_<page>, e.g. NL-SdmGA_1504889_11). Optionally highlight a term in the transcript. Hosts without MCP Apps support receive a text summary plus inline preview images.

  ConnectorNo auth

• ask_siteA

  agentready-mcpA

  Query any website's documentation and get cited, multi-page answers in natural language. Use ask_site when you need: (1) answers that synthesize information across multiple pages of a site, (2) documentation from JS-rendered sites (React, Next.js, Vue SPAs) where web_fetch returns empty or partial HTML, (3) citations linking back to the exact source pages, (4) faster results than fetching and reading individual pages one by one. For sites not yet indexed, ask_site auto-crawls and answers in ~60s — no separate submit_site call needed.

  ConnectorNo auth

• edit_pageA

  simplepagesA

  Change an existing landing page by describing what to change in plain language (e.g. "change the headline to X", "add a pricing section", "make the hero button say Book now"). Edits the page's current content in place and saves it to the draft. The change is not published until you publish separately. Works for both standalone pages and pages inside a site. Use get_page / list_pages / list_sites to find the page id.

  ConnectorOAuth

• create_siteA

  simplepagesA

  Create a new multi-page website in the workspace. The site starts empty: use add_page_to_site to build its pages, starting with the home page (slug "index"). To make a single standalone landing page instead, use create_page — that does not need a site.

  ConnectorOAuth

• searchA

  Vascue Public Knowledge SearchA

  Hybrid keyword + semantic search over the public pages of vascue.io: healthcare-operations guides, the AI front desk for clinics, provider-side insurance-claims automation, Cliniko and Nookal integration, security and compliance pages, case studies, pricing and blog posts. Use it to answer questions about what Vascue offers, how its products work and what it has published. One topic per call; cite the returned page URL for every excerpt you use. Returns a JSON text payload: result.chunks[] ordered by relevance, each with text (a Markdown excerpt), score (0-1, higher is better) and item.metadata.url (the canonical https://www.vascue.io/... page). Off-topic queries still return the nearest chunks, so treat scores below about 0.5 as weak evidence and say so when the site does not cover a topic. Read-only and idempotent; no authentication; 60 requests per minute per client. Public content only: never send patient information, claim documents, clinic credentials or booking requests. It cannot book appointments or look up clinic data.

  ConnectorNo auth

• searchA

  Vascue Public Knowledge SearchA

  Hybrid keyword + semantic search over the public pages of vascue.io: healthcare-operations guides, the AI front desk for clinics, provider-side insurance-claims automation, Cliniko and Nookal integration, security and compliance pages, case studies, pricing and blog posts. Use it to answer questions about what Vascue offers, how its products work and what it has published. One topic per call; cite the returned page URL for every excerpt you use. Returns a JSON text payload: result.chunks[] ordered by relevance, each with text (a Markdown excerpt), score (0-1, higher is better) and item.metadata.url (the canonical https://www.vascue.io/... page). Off-topic queries still return the nearest chunks, so treat scores below about 0.5 as weak evidence and say so when the site does not cover a topic. Read-only and idempotent; no authentication; 60 requests per minute per client. Public content only: never send patient information, claim documents, clinic credentials or booking requests. It cannot book appointments or look up clinic data.

  ConnectorNo auth

• list_monitored_pagesA

  Inclusify AccessibilityA

  Use this whenever a scan-backed answer came back empty or thin and you need to know whether that means 'clean' or 'never checked'. It is the only tool that says whether monitoring is actually working: a page failing every night, throttled, or a whole storefront behind a password produces no data and reads exactly like a site with nothing wrong. The monitored-page inventory for a website: which URLs are watched, which are paused, when each was last scanned, its last score, and which pages are failing, unreachable, throttled or overdue. Also reports how many of the plan's audited-page slots are in use. Read-only from stored state: it loads nothing, costs no page allowance, adds and removes no pages, and shows the last recorded attempt rather than the live state of the site. Monitoring runs about every 20h per page, so a page scanned a few hours ago being "due" is normal, not a fault.

  ConnectorAPI key

• add_monitored_pagesA

  Inclusify AccessibilityA

  Use this when a page that matters is not being watched at all — a checkout, an account area, a campaign landing page missing from list_monitored_pages — and should be checked from now on. WRITES to this website's Inclusify configuration — never to the site itself: adds URLs to the set of pages scanned on the daily monitoring rotation. Add-only: it never removes, pauses or edits a page; those stay in the Inclusify panel. Idempotent: a URL already monitored is reported back as alreadyMonitored, not duplicated and not an error. Every URL must be on the website's own domain(s); up to 20 per call. All-or-nothing against the plan's audited-page allowance: if the batch would not fit (paused pages hold their slots too), nothing is added and the response says what would. Loads no page and costs no page allowance. New pages are picked up by the scan worker's continuous queue — never-scanned pages first, then a re-scan roughly every 20h — not instantly; for an immediate answer use start_crawl or a live check tool.

  ConnectorAPI key