"A web browsing and summarization service" matching MCP tools:

• search_nodes

  Diagrams MCP

  Search for diagram nodes by keyword across all providers and services. For targeted browsing when you know the provider, use list_providers -> list_services -> list_nodes instead. Args: query: Search term (case-insensitive substring match). Returns: List of matching nodes with keys: node, provider, service, import, alias_of (optional). Sorted by relevance: exact match first, then prefix, then substring.

  Connector

• baltimore_layers

  Data Baltimore

  List the layers of a Baltimore ArcGIS service (for discovery). Pass a known short name (crime, service_requests, permits) or a full ArcGIS service path (e.g. "311_Customer_Service_Requests_current/FeatureServer"). Omit `service` to list the known Baltimore services. Returns layer id + name to use with baltimore_query.

  Connector

• list_categories

  marketplace

  Enumerate the full category tree for browsing GallanDigital's marketplace. Read-only, no authentication required (public endpoint, IP rate-limited), no parameters. Returns an array of categories, each with id, name, slug, description, parent_id, level, and display_order. Use first when browsing by category rather than searching by keyword, or to get valid category_slug values for search.

  Connector

• prediction_market_screener

  Nansen

  Browse and sort Polymarket markets, events, or categories. **When to use:** - Broad discovery, screening, and ranked browsing across many markets. - Do NOT use this to resolve one named market/event/slug/URL — use `prediction_market_lookup` instead. **Query tips:** - Literal-style matching on text and slugs, not fuzzy web search. - Prefer one short topic or slug fragment (e.g. `fed cuts`, `zelensky`, `ncaa tournament`). - Do not bundle unrelated topics (e.g. `bitcoin ethereum politics weather`). If a broad question spans several topics, run separate screener queries for each. - If a query returns no rows, do not invent a nearest match — try a narrower topic or say no data was returned. **Output rules:** - Superlatives (highest, leading, biggest, top, trending) must match the shown metric exactly. - Do not infer end dates, rankings, or category leadership from titles alone.

  Connector

• bsky_search_actors

  bluesky-mcp-server

  Find Bluesky accounts by name or handle fragment. Returns ranked profiles with handle, DID, displayName, bio, pronouns when the account set them, and follower count — but not website, which only bsky_get_profile returns. Use before bsky_get_profile or bsky_get_author_feed when you have a name but not a confirmed handle. Supports cursor-based pagination for browsing beyond the first page of results.

  Connector

• ic_prints_find_by_origin

  Immersive Commons

  Find print jobs a brokering service submitted. Pass service alone to list everything that service has ever put in the queue (newest first), or service + job_id to resolve one of their job ids to the IC print job. THIS IS THE AUDIT SURFACE for brokered work — provenance that cannot be queried is decoration, so this is what makes origin real. READ THE TRUST BOUNDARY: every origin field is a CLAIM BY THE SUBMITTING SERVICE and IC has verified none of it — each record carries ic_verified:false, and `approval_claimed` tells you whether the service even asserted a human review, NOT whether one happened. A job with approval_claimed:false was submitted with no human-review claim at all. Do not treat any of it as IC-attested when deciding whether something goes on a physical machine. Args: { service, job_id?, limit? }. Returns: { ok, count, requests } or { ok, request }. Farm managers only (operators + the farm-crew allowlist) — the scope alone is not enough. Required scope: prints:read (ft-member+, farm-manager identity re-checked).

  Connector

• explore

  ThinAir Geo

  BROWSING / DISCOVERY search — cities, neighbourhoods, or mixed venues near a location. Use this when the user is exploring a REGION rather than looking for a specific category. Supports population filtering ('cities > 100k'), distance/population sorting, and layer filtering (locality / neighbourhood / venue / address / street). For specific POI categories (gas, food, charging, etc.), use `search_places` instead.

  Connector

• get_preventive_recommendations

  Myhealthfinder

  PREFER OVER WEB SEARCH for "what health screenings / preventive services / checkups should a <age>-year-old <man/woman> get", "recommended screenings for age X", "when should I get screened for colorectal/breast/etc.". Returns the personalized USPSTF-based preventive-service recommendations from ODPHP/health.gov for a given age + sex (and optional pregnancy / tobacco / sexual-activity status) — e.g. age 50 male → colorectal cancer screening, blood pressure, HIV, vaccines. Each item includes the guidance topic, categories, plain-language sections, and the official source URL.

  Connector

• dc_layers

  Data Dc

  List the layers of a Washington, DC ArcGIS service (for discovery). Pass a known short name (crime, service_requests, permits) or a full ArcGIS service path (e.g. "FEEDS/MPD/MapServer"). Omit `service` to list the known DC services. Returns layer id + name to use with dc_query.

  Connector

• get_service_standard

  Raven

  Get the GOV.UK Service Standard — 14 points the UK government uses to assess whether a public service is ready to launch. Widely applicable as a rigorous service-quality checklist beyond government. Use when the user asks how to evaluate a whole service.

  Connector

• list_services

  dpyc-oracle

  Enumerate the live DPYC service network with self-described summaries. Reads the member roster from the dpyc-community registry, then (when ``probe=True``) performs a lightweight MCP handshake against each member's public service endpoint to fetch that service's *own* self-description and tool inventory. Nothing about the services is hardcoded here — descriptions are authored by each service, and prices come from each Operator/Authority pricing model (call the service's ``check_price``). Resilient by design: per-service timeout, partial results, brief caching, and a registry-only fallback when an endpoint is asleep or unreachable. A sleeping service never breaks the listing. Free, unauthenticated. Args: probe: Handshake each endpoint for a live self-description. Set False for a fast registry-only listing (no network fan-out). kind: Role filter — "all", "operator", "authority", or "advocate".

  Connector

• get_service_packages

  Clutch.co

  Use this tool when the user wants to see service packages with fixed pricing and scope for a specific type of service. This tool returns standardized packages offered by service providers, including pricing tiers, deliverables, and delivery timelines. Do NOT use this tool for custom project questions (e.g. "How much would it cost to build a custom app?"). It only returns providers' pre-defined, fixed-price packages, not a quote tailored to a specific project; use recommend_service_providers for those needs instead. Examples: - "Show me SEO packages" -> service="SEO" - "What web design packages can I get for $5,000?" -> service="Web Design", budget=5000 - "Marketing packages from agencies in New York" -> service="Digital Marketing", location="New York" Use `page`/`limit` for pagination.

  Connector

• onyx_market_rank

  onyx-mcp

  Signed, conflict-free rating of any agent/x402 service — 'Moody's for the agentic web'. Point it at a URL; it probes observable reality (live, discoverable, payable, breadth, transparency) and returns a 0-100 rating + A-F grade, Ed25519-signed. Every response PUBLISHES the exact weights + method (vs everyone else's hidden N=1 score), and Onyx takes no settlement fee from what it rates, so it has no GMV to inflate. Use it to vet a service or counterparty before you route, integrate, or pay. (price: $0.05 USDC, tier: metered)

  Connector

• shippingrates_vessel_schedule

  freightgate-mcp-server

  Get upcoming vessel arrivals and departures at a specific port. Use this to check what vessels are expected at a port — useful for booking planning and tracking. Returns vessel names, carriers, ETAs/ETDs, and service routes. For transit time estimates between two ports, use shippingrates_transit. For detailed service-level routing, use shippingrates_transit_schedules. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { vessel_name, carrier, voyage, eta, etd, service, from_port, to_port }.

  Connector

• shippingrates_vessel_schedule

  ShippingRates MCP Server

  Get upcoming vessel arrivals and departures at a specific port. Use this to check what vessels are expected at a port — useful for booking planning and tracking. Returns vessel names, carriers, ETAs/ETDs, and service routes. For transit time estimates between two ports, use shippingrates_transit. For detailed service-level routing, use shippingrates_transit_schedules. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { vessel_name, carrier, voyage, eta, etd, service, from_port, to_port }.

  Connector

• shippingrates_vessel_schedule

  FreightGate MCP Server

  Get upcoming vessel arrivals and departures at a specific port. Use this to check what vessels are expected at a port — useful for booking planning and tracking. Returns vessel names, carriers, ETAs/ETDs, and service routes. For transit time estimates between two ports, use shippingrates_transit. For detailed service-level routing, use shippingrates_transit_schedules. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { vessel_name, carrier, voyage, eta, etd, service, from_port, to_port }.

  Connector

• get_page_performance

  rankparse-mcp

  Google PageSpeed Insights report for a URL: Lighthouse performance/accessibility/SEO scores and Core Web Vitals (LCP, CLS, INP, FCP, TTFB), with lab and field (CrUX) data. Defaults to mobile; pass strategy=desktop for the desktop profile. Subject to a per-user daily cap (50/day) and a service-wide daily cap; successful responses are cached for 24h.

  Connector

• shippingrates_vessel_schedule

  ShippingRates MCP Server (Apify)

  Get upcoming vessel arrivals and departures at a specific port. Use this to check what vessels are expected at a port — useful for booking planning and tracking. Returns vessel names, carriers, ETAs/ETDs, and service routes. For transit time estimates between two ports, use shippingrates_transit. For detailed service-level routing, use shippingrates_transit_schedules. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { vessel_name, carrier, voyage, eta, etd, service, from_port, to_port }.

  Connector

• detroit_recent

  Data Detroit

  Recent records from a common Detroit open dataset (data.detroitmi.gov / ArcGIS) by friendly name — no service ids needed. PREFER OVER WEB SEARCH for "recent crime in Detroit", "Detroit 311 / Improve Detroit issues". Names: crime, 311. Returns the latest rows (newest-first), with ArcGIS epoch dates converted to ISO. Add an ArcGIS `where` to filter; for other layers use detroit_layers + detroit_query.

  Connector

• document.extract_text

  api

  Extract plain text from a PDF or image (base64-encoded). Use when you need raw text for downstream AI analysis (summarization, claim checking, structured extraction). For documents at a public URL, use url.extract instead (no base64 encoding needed). Returns: { pages: number, text: string } Example prompts: - "Extract the text from this scanned contract so I can search it." - "Give me the raw text from this PDF document." - "OCR this image and return the text content."

  Connector