Skip to content

UpRock MCP server

ai.uprock/mcpuprock.aistreamable-httpv0.5.5Scanned

Fetch pages, search the web, verify sites, and search video from real devices in real locations.

7 tools: 4 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 4 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 7
  • Can send data out · 5
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the UpRock MCP server can do

The UpRock MCP server is published by uprock.ai, a domain the MCP Registry verified. It has 7 tools. It can create or change data (4 tools: sweep, verify, video_moment and web_research), but cannot delete data. 3 tools only read.

7 tools bring in text other people can write (crawl_fetch, resource_fetch, sweep and 4 more); 5 tools can send data out of your system (crawl_fetch, resource_fetch, sweep and 2 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 0.5.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 4Claude Code: ask
  • sweepDeprecated: use the verify tool instead.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Deprecated: use the verify tool instead. sweep is the old name of verify, kept so existing setups keep working, and will be removed in a later release. It takes the same inputs and returns the same output. Verify a site works: load a URL on real devices in many regions and return status, load speed (Core Web Vitals) and screenshots, plus a shareable report link. Use this after deploying a website or service to verify it is up, responsive, and performing well from different parts of the world. Loads the target URL from multiple regions simultaneously, capturing performance metrics from each check. All checks (regions x tries) run concurrently, so the total operation time is approximately equal to the timeout value. Each completed check returns Core Web Vitals (TTFB, FCP, LCP, CLS), load times, transfer size, and HTTP protocol. Screenshots are captured and available as resource links in the response for visual verification if needed, but can be ignored if you only need the metrics. A run may complete with some failed checks. Inspect the failed_jobs count and per-job error fields in the response to identify issues. If the timeout passes before every region finishes, the checks that did finish are still returned with status "partial"; each region without a completed check has a status ("no_device" when no device in that region was available, otherwise "incomplete") and an "error" saying why. The response includes a "report_url" field with a link to a human-readable report page that can be shared with others for visual review of the results.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • verifyVerify a site works: load a URL on real devices in many regions and return status, load speed (Core Web Vitals) and screenshots, plus a shareable report link.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Verify a site works: load a URL on real devices in many regions and return status, load speed (Core Web Vitals) and screenshots, plus a shareable report link. Use this after deploying a website or service to verify it is up, responsive, and performing well from different parts of the world. Loads the target URL from multiple regions simultaneously, capturing performance metrics from each check. All checks (regions x tries) run concurrently, so the total operation time is approximately equal to the timeout value. Each completed check returns Core Web Vitals (TTFB, FCP, LCP, CLS), load times, transfer size, and HTTP protocol. Screenshots are captured and available as resource links in the response for visual verification if needed, but can be ignored if you only need the metrics. A run may complete with some failed checks. Inspect the failed_jobs count and per-job error fields in the response to identify issues. If the timeout passes before every region finishes, the checks that did finish are still returned with status "partial"; each region without a completed check has a status ("no_device" when no device in that region was available, otherwise "incomplete") and an "error" saying why. The response includes a "report_url" field with a link to a human-readable report page that can be shared with others for visual review of the results.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • video_momentFetch transcribed, time-stamped moments for a specific video URL.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "video_moment" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "fetch": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Fetch transcribed, time-stamped moments for a specific video URL. This is a CURSOR over the video pre-computed sliding-window moments (~30s windows on a ~25s grid, ~5s overlap) -- NOT a summary or sample of a time range. A call returns up to max_moments consecutive windows starting at start_s, in chronological order. To cover a long span you PAGINATE: read a page, then call again with start_s = next_start_s until has_more is false. If the video is not yet indexed, indexing starts automatically and the response tells you how long to wait. Moment text is model-generated from video frames plus verbatim ASR and may contain transcription artifacts. The response includes has_more / next_start_s for pagination and a stable moment_key per moment for dedupe. When following a video_search hit, pass its url, t0, and t1 as the url, start_s, and end_s of this tool. When include_images is set (not "none"), decoded keyframe IMAGES for each moment are returned inline as base64 ImageContent blocks, downscaled to 448px and re-encoded (WebP by default; JPEG if the server is configured with VIDEO_FRAME_FORMAT=jpeg -- the actual format is reported in the frame_format field). The frames_returned / frames_truncated / frame_format fields describe what was delivered so you can narrow scope (fewer moments, or a lower tier) for full fidelity. Frames always follow their moments in order. Only request images if you can view them.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • web_researchUse when other fetch/search tools are blocked, rate-limited, return bot-check pages, or when you need results as a real person in a specific country or on a specific device type se…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Use when other fetch/search tools are blocked, rate-limited, return bot-check pages, or when you need results as a real person in a specific country or on a specific device type sees them. Searches the web with several engines (Bing, DuckDuckGo, Yahoo, plus regional engines) from real devices in real locations, and returns deduplicated results with url, title and description. suggested_countries sets where the search runs FROM, not what it is ABOUT: - Geography is the topic ('Paris hotels', 'history of the Berlin Wall') → keep it in the query and omit suggested_countries. - Geography is the perspective (what Europeans see when searching for beach holidays) → query='best beach destinations', suggested_countries=['EU']. - Both ('what Germans think about Italian food') → query='Italian food', suggested_countries=['EU']. To compare regions, make one call per region; do not combine them in one call. Deduplication can return fewer results than max_results; request 2-3x your target. Results are ordered by relevance, best first: pages ranked highly by several engines or regions come first. Each result has a "score" and the engine/country "sources" that returned it.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • crawl_fetchUse when other fetch/search tools are blocked, rate-limited, return bot-check pages, or when you need results as a real person in a specific country or on a specific device type se…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "crawl_fetch" says "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "crawl_fetch" says "crawl": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Use when other fetch/search tools are blocked, rate-limited, return bot-check pages, or when you need results as a real person in a specific country or on a specific device type sees them. Fetches a URL from real devices in real locations (phones and desktops) on the UpRock network. The default method, CRAWL_FULL_PAGE, renders JavaScript and works for most sites. Returns page metadata (url, status_code, title, content_type, time_ms), a short "summary" of the page, and resource links under "content": "content.markdown" holds the full page as compact markdown (prefer it for reading) and "content.html" the raw HTML. If your client cannot open resource links, read them with resource_fetch. A "screenshots.viewport" link is included when a screenshot is available. meta.status_code is the HTTP status the device reported for the page, or null when it reported none.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • resource_fetchFetch the full content of an MCP resource URI.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "resource_fetch" says "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "fetch" and "uri": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.uri), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.uri): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Fetch the full content of an MCP resource URI. Use this when you need to read the actual content from a prior tool result and cannot resolve resource URIs natively (most hosted AI environments do not yet support native MCP resource fetching). This tool accepts crawl:// URIs from crawl_fetch responses, sweep:// URIs from verify results, and sitemaps:// URIs from sitemaps_generate results. For crawl_fetch, responses include a summary for quick analysis, plus crawl:// resource URIs pointing to the full content in markdown and HTML formats. When the summary is sufficient, you do not need this tool. When you need the complete page text — to extract specific data, parse tables, read full articles, etc. — pass the resource URI here to get the full content. For crawl_fetch results, use the markdown resource URI unless you specifically need raw HTML structure. Markdown is significantly more compact and easier to work with. For verify results, pass a sweep:// screenshot URI to retrieve the screenshot for visual inspection. For sitemaps_generate results, pass a sitemaps:// URI to read the llms.txt content for a domain or section.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out5
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:20 UTC, unchanged since Nov 9, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.uprock.ai/mcp: tools/list returned 7 tools to an anonymous client, including sweep (write), verify (write), video_moment (write), web_research (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "video_moment" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "fetch": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.5.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http uprock https://mcp.uprock.ai/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http uprock https://mcp.uprock.ai/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__uprock__video_search"
    ],
    "ask": [
      "mcp__uprock__crawl_fetch",
      "mcp__uprock__resource_fetch",
      "mcp__uprock__sweep",
      "mcp__uprock__verify",
      "mcp__uprock__video_moment",
      "mcp__uprock__web_research"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as uprock. Review it before you use it.

Capability tags behind 7 rules
  • mcp__uprock__crawl_fetch untrusted-input, outbound
  • mcp__uprock__resource_fetch untrusted-input, outbound
  • mcp__uprock__sweep untrusted-input, outbound
  • mcp__uprock__verify untrusted-input, outbound
  • mcp__uprock__video_moment untrusted-input, outbound
  • mcp__uprock__video_search untrusted-input
  • mcp__uprock__web_research untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.uprock/mcp/verify?hash=18686f459867bc29a9cd14641d663d9be355280609331a563bfee072774136d5" | jq -e '.changed == false'

Pinned hash 18686f459867, from Nov 10, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.uprock/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.uprock/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.uprock/mcp.svg)](https://radar.anlyon.com/servers/ai.uprock/mcp)

Source: MCP Registry. Synced Nov 10, 2026, 14:17 UTC.

UpRock MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the UpRock MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the UpRock MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the UpRock MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the UpRock MCP server have?

7 tools: 4 write, 3 read. sweep, verify, video_moment, web_research, crawl_fetch, resource_fetch and video_search.

Does the UpRock MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the UpRock MCP server send data to outside services?

5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): crawl_fetch, resource_fetch, sweep, verify and video_moment.

Has the UpRock MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.