String Web Access MCP server
ai.usestring/web-accessusestring.aistreamable-httpv1.4.2Scanned
Search the web, fetch any URL and map a site as clean, LLM-ready Markdown.
4 tools: 3 can delete or cancel things and 1 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- 4 findings
Sign-in required, OAuth metadata published. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the String Web Access MCP server can do
The String Web Access MCP server is published by usestring.ai, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (3 tools: web_access_fetch, web_access_request and web_access_sitemap). 1 tool only reads.
4 tools bring in text other people can write (web_access_fetch, web_access_request, web_access_search and 1 more).
The fixed checks matched 4 findings (long-description and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint asks for sign-in and publishes OAuth metadata.
Last scanned Nov 16, 2026, version 1.4.2.
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.
4 tools
Deletes or cancels 3Claude Code: deny
web_access_fetchFetch a caller-specified HTTP(S) URL and get clean, LLM-ready Markdown back.Reads text others write2 findings
Why it is in this group
- The name "web_access_fetch" says "fetch": a word for reading.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "web_access_fetch" says "fetch" and "web": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "fetch" and "http": 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.
Findings
- Info
The description is 5,378 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...lenge handling is subject to the caller's String account and organization policy."
- Warn
The server marks "web_access_fetch" destructive (destructiveHint: true), and its name says "fetch", a word for reading.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":true}; The name "web_access_fetch" says "fetch": a word for reading.
Description, as the server wrote it Fetch a caller-specified HTTP(S) URL and get clean, LLM-ready Markdown back. **Primary use (the common case):** pass only a `url`. The page is fetched with a normal GET and returned as Markdown — no other parameters are needed. ```json { "url": "https://example.com/article" } ``` **Best for:** any URL, especially sites that block automated traffic or render their content client-side (news, docs, blogs, web apps). **Not for:** searching the web when you don't have a URL — use web_access_search instead. **Optional parameters (omit unless you need them):** - `format` — `markdown` (default), `raw` (the destination's verbatim body), or `json` (a `{ statusCode, headers, data }` envelope with the destination's status and headers). - `executeJS` — set true to render JavaScript for SPAs when the content comes back empty. - `actions` — drive a real browser (click, scroll, type, wait) before capturing the page. See below. **To send a direct POST, PUT or PATCH** (with a body), use `web_access_request` — this tool's direct HTTP path only issues GETs. Plenty of those calls are reads: a GraphQL query, a search backend that takes a body, a JSON API that refuses GET. - `headers` — forward custom request headers; not combinable with `executeJS` or `actions`, which run in a browser. - `countryCode` — ISO 3166-1 alpha-2 (e.g. "US") to route through a proxy in that country. - `solveCaptcha` — defaults true; set false to fail fast instead of spending effort solving a challenge. **Returns:** Markdown by default; the verbatim body or a JSON envelope when `format` is set accordingly. --- ## `actions` — driving the page instead of just loading it An `actions` sequence runs in a real browser session and returns the page as it stands after the last step. Use it when the content you need does not exist in the document until something happens to the page: a click past a consent gate, a search form submitted, a "load more" button, a tab or accordion opened, or rows that only render once scrolled into view. Actions can modify destination data or submit a form, so clients should treat any call to this tool as potentially destructive. **Escalate in this order — each step takes longer than the last, and steps 2 and 3 bill at the browser rate:** 1. Plain `url` — always try this first. 2. `executeJS: true` — the page renders client-side but needs no interaction. 3. `actions` — the content requires interaction. Takes tens of seconds and holds a browser session. If the data is still absent after all three, it is likely never in the HTML at all — look for the JSON API the page itself calls and fetch that endpoint directly, which is faster and returns exact values. **Steps** (max 50 per request; at most one `screenshot`): - `{"type": "wait", "selector": ".price", "timeout": 20000}` — wait until the selector appears, then continue immediately. Prefer this over a fixed pause. - `{"type": "wait", "milliseconds": 3000}` — fixed pause. Max 30000ms, as is `timeout` above. - `{"type": "click", "selector": "#accept", "all": false}` — `all: true` clicks every match. - `{"type": "write", "text": "..."}` — types into the focused element; click it first. - `{"type": "press", "key": "Enter"}` - `{"type": "scroll", "direction": "down", "amount": 1000, "selector": "..."}` — `selector` scrolls that element instead of the page. - `{"type": "hover", "selector": "..."}` - `{"type": "selectOption", "selector": "select#size", "value": "L"}` — `value` may be an array. - `{"type": "navigate", "url": "https://..."}` — go to another page mid-session, keeping cookies and state. - `{"type": "screenshot", "full_page": true, "quality": 80}` The session opens on `url` before your first step, so never begin with a `navigate` to that same URL. **Examples** Dismiss a cookie banner, then read the page: ```json { "url": "https://example.com/pricing", "actions": [ { "type": "click", "selector": "#accept-cookies" }, { "type": "wait", "selector": "main .plan", "timeout": 15000 } ] } ``` Run a search the site offers no URL for: ```json { "url": "https://example.com", "actions": [ { "type": "click", "selector": "input[name=q]" }, { "type": "write", "text": "standing desk" }, { "type": "press", "key": "Enter" }, { "type": "wait", "selector": ".results .item", "timeout": 20000 } ] } ``` Fill in rows that render only as they scroll into view: ```json { "url": "https://example.com/listings", "actions": [ { "type": "wait", "selector": ".card", "timeout": 20000 }, { "type": "scroll", "direction": "down" }, { "type": "wait", "milliseconds": 1500 }, { "type": "scroll", "direction": "down" }, { "type": "wait", "milliseconds": 1500 } ] } ``` **Returns with `actions`:** a JSON object — `data` (the final page, Markdown by default), `finalUrl`, `statusCode`, and `screenshot` when the sequence took one. If a step fails, the call still succeeds and returns `error` plus `failedActionIndex`, a 0-based index into your `actions` array, with `data` holding the page as it stood at that point — read it to see what the page actually showed, then fix that step's selector. **Not combinable with** `headers` or `format: "raw"`; a browser session is always a GET. Requests must comply with destination policy, robots directives, rate limits, and access controls. Challenge handling is subject to the caller's String account and organization policy.
Annotations the server declares
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
web_access_requestSend a POST, PUT or PATCH request to any URL, through String's Web Access API.Reads text others writeNo findings
Why it is in this group
- The name "web_access_request" says "request": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
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 Send a POST, PUT or PATCH request to any URL, through String's Web Access API. It works like web_access_fetch, but for calls that submit data rather than read a page — a JSON API that only accepts POST, a GraphQL endpoint, a search backend that takes a body. **Use web_access_fetch instead** whenever you only need to read a page. This tool sends a body to the destination rather than reading it, so use it only for a request the user actually asked for. **Usage Example:** ```json { "url": "https://api.example.com/search", "method": "POST", "body": { "q": "widgets" } } ``` **Returns:** The destination's response, in the requested format.
Annotations the server declares
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
web_access_sitemapManage an asynchronous crawl of authorized public pages on one website.Reads text others write1 finding
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 destructive (destructiveHint: true).
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 "crawl": it reads web pages, which anyone can write.
Findings
- Info
The description is 3,710 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...e chosen action (quote, status, URL page, job list) alongside a one-line summary."
Description, as the server wrote it Manage an asynchronous crawl of authorized public pages on one website. Starting from one URL, the crawler follows same-domain links breadth-first and can also seed from the site's /sitemap.xml. Requests must comply with destination policy, robots directives, rate limits, and access controls. Use this tool to discover pages for site audits, authorized retrieval worklists, or coverage checks before fetching individual pages. **Not for:** reading one page's content (use web_access_fetch) or open-ended web queries (use web_access_search). This single tool drives the whole job lifecycle through `action`: **1. `submit` — quote a crawl (nothing is crawled or billed yet).** Requires `url`. Optional: `maxPages` (1–10000, default 10), `maxDepth` (1–100, default 2), `pathPrefix` (only crawl URLs whose path starts with this, e.g. "/docs"), `budgetUsd` (spend ceiling; the crawl stops with status token_cap_exceeded if it would exceed it), `useSitemap` (also seed the site's root /sitemap.xml — one extra billed page, but finds pages links miss). A `maxPages` or `maxDepth` outside its range, 0 included, is rejected rather than replaced by the default — omit the field to get the default. Returns `jobId`, `estimatedPages`, and `estimatedCostUsd` with status `awaiting_approval`. ```json { "action": "submit", "url": "https://example.com", "maxPages": 200, "maxDepth": 3 } ``` **2. `approve` — start the quoted crawl (requires `jobId`).** This is the billing-consent step: pages are billed as they are fetched, capped by the quote/budget. Before approving a non-trivial `estimatedCostUsd`, confirm the spend with your user. Fails with status 402 if the account balance cannot cover the quote; a 409 partial_state error means an earlier approve was interrupted — just call approve again. **3. `status` — poll progress (requires `jobId`).** Statuses: `awaiting_approval` → `running` → terminal `completed` | `failed` | `canceled` | `token_cap_exceeded` (budget hit before maxPages; collected results are still readable). While running it returns `pending` and `processed` counts; a `partial_state` status means an interrupted approve — call approve again to repair it. Status never includes the URL list — page that with `results`. Poll every few seconds for small crawls; give hundreds-of-pages crawls tens of seconds between polls. **4. `results` — page through discovered URLs (requires `jobId`).** Optional `limit` (1–5000, default 1000) and `offset` (≥ 0); out-of-range values are rejected. `total` tells you when to stop paging. Each entry has `url`, `statusCode` (0 = discovered but not fetched), `depth`, `parentUrl`, `isSitemap`, `sourceType`, and an `error` when that page failed. `discoveredUrls` (links found on the page) is only present for ~1h after completion; afterwards results come from durable storage which omits it — everything else stays available. **5. `cancel` — stop a running or pending job (requires `jobId`).** Already-terminal jobs return a 409 error. Pages already fetched stay billed and readable via `results`. **6. `list` — recent crawl jobs for the account.** Optional `limit` (1–100, default 20) and `offset` (≥ 0); out-of-range values are rejected. Use it to find a jobId you lost or check for an equivalent recent crawl before paying for a new one. **Typical workflow:** submit → check estimatedCostUsd → approve → poll status until terminal → results (paged). A 404 on any jobId action means the job doesn't exist or belongs to another account; a 403 on submit means the target domain is blocked for this account (contact support@usestring.ai). **Returns:** the JSON envelope for the chosen action (quote, status, URL page, job list) alongside a one-line summary.
Annotations the server declares
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
Only reads 1Show 1 read-only tool
web_access_searchSearch the public web for a caller-specified query and get ranked organic results back, plus whatever Google rendered around them: knowledge panel, AI overview, People also ask, lo…Reads text others write1 finding
Why it is in this group
- The name "web_access_search" says "search": 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 "web_access_search" says "search" and "web": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "search" and "web": it reads web pages, which anyone can write.
Findings
- Info
The description is 12,806 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...Requests must comply with destination policy, rate limits, and access controls."
Description, as the server wrote it Search the public web for a caller-specified query and get ranked organic results back, plus whatever Google rendered around them: knowledge panel, AI overview, People also ask, local pack, videos, discussions. Google's images, videos, shopping, books, places and forums tabs are searched with `searchType`. **Primary use:** pass a `query` string. There is no engine or domain-filter parameter; any other key is rejected before the call. ```json { "query": "site:arxiv.org retrieval augmented generation" } ``` **Optional targeting fields:** `country` — ISO 3166-1 alpha-2 code the search runs from, e.g. `GB` (default `US`); `language` — results language tag such as `en` or `pt-br`. ```json { "query": "plumbers", "country": "GB", "language": "en" } ``` To search from a place, send `location`, a place name such as `London` or `Austin,Texas,United States` (1 to 200 characters), or `coordinates`, `{ latitude, longitude, radius }` with radius in meters (default 5000). The search is sent from that place's country; if both are sent, `coordinates` win. A name that cannot be placed fails, so send `coordinates` instead. On the results page the place biases results toward it. The effect is strongest for queries like `plumbers near me`, and it is not exact city targeting: a bare query such as `coffee shops` may still return results from a wider area. ```json { "query": "plumbers near me", "location": "Austin,Texas,United States" } ``` **Optional request field:** `searchCount` — how many organic results you want, an integer from 1 to 300 (above 300 is rejected). Google is paged, up to 36 pages, until that many are in hand; each page is billed as one search. Many queries run out before 300: Google often has 100-200 results for a query, and you get what it has, with `paging.complete: true` and `paging.stoppedBy: "end_of_results"`. Omit it for one page, about 10 results, and the response then carries no `paging`. Not with `format: "raw"`, which returns one page per call. ```json { "query": "construction consulting firms Ohio", "searchCount": 30 } ``` **Optional Google field:** `searchType` — the Google tab to search: `"web"` (the default, the ordinary results page), `"images"`, `"videos"`, `"shopping"`, `"books"`, `"places"` or `"forums"`. There is no news tab. Each page fetched is billed as one search, as on the web. - `videos`, `books`, `forums` answer `results`, paged like the web; each video carries `video` (`channel`, `platform`, `duration`) and each book `book` (`authors`, `published`). - `images` answers `images`, about 100 a page, each with `title`, `url` (the page it is on), `source`, `imageUrl` (the file), `imageWidth`, `imageHeight` and `thumbnail`. It has 3 pages; `searchCount` up to 300 collects across them, usually about 270 images. - `shopping` answers `products`, the one page of about 55 product cards: `title`, `productId`, `price` and `originalPrice` as shown, `merchant` and `moreMerchants`, `delivery`, `returns`, `rating`, `reviews`. A card has no `url`. Google does not page this tab, so `page` must be 1. - `places` answers `places`, 20 businesses a page, paged like the web up to page 15. `results` is empty for images, shopping and places. `dateRange`, `sortBy` and `verbatim` apply to web, videos and forums only; `format: "raw"` and `aiOverview` to web only. ```json { "query": "eames lounge chair", "searchType": "images", "searchCount": 150 } ``` **Optional Google filters:** `safeSearch` — `true` removes explicit results; `includeOmittedResults` — `true` includes the results Google hides as very similar to ones shown; `autocorrect` — `false` searches the query exactly as typed instead of Google's correction; `restrictCountry` — a two-letter code — keeps only pages from that country (unlike `country`, which sets where the search runs from); `verbatim` — `true` matches the words exactly, without synonyms. None combines with `aiMode`. ```json { "query": "climate policy", "restrictCountry": "FR", "safeSearch": true } ``` **Optional Google fields:** `page`, `dateRange` and `sortBy` apply to Google results only; none of them combines with `aiMode`. - `page` — the results page to start from, an integer from 1 to 30 (default 1), where page N is the page Google shows as N. Without `searchCount` the response is that one page; with it, `searchCount` results are collected starting from that page. `page` and `searchCount` together stay within the first 300 results: (page - 1) × 10 + (`searchCount`, or 10 without it) must be at most 300. A page past Google's last result returns no results with `zeroResults: true`. Pages hold 8-10 results, so separate `page` calls can repeat or skip a result; for one list without repeats, send one call with `searchCount`. - `dateRange` — limit results to a publication window: one of `"hour"`, `"day"`, `"week"`, `"month"` or `"year"` for the past hour through the past year, or `{ "from": "2024-01-01", "to": "2024-06-30" }` for a custom range of ISO dates (YYYY-MM-DD), inclusive. Either end is optional but at least one is required, and `from` must not be after `to`. - `sortBy` — `"relevance"` (the default) or `"date"` for the newest results first. ```json { "query": "heat pump grants", "page": 2, "dateRange": "month", "sortBy": "date" } ``` **Optional Google field:** `format` — `"structured"` (the default, recommended) for the parsed results above as JSON, or `"raw"` for the Google results page as HTML, one page per call. The response is then `html`, `htmlBytes` and `htmlTruncated` in place of `results` and the surfaces. This tool sends at most 60,000 bytes of markup per call and sets `htmlTruncated: true` when it cuts the page; for the whole page, call the HTTP API's POST /v1/search with `format: "raw"`. Raw supports `page` only, not `searchCount`: a raw call with `searchCount` is rejected (the API answers 400), so ask for page N with `page` and send one call per page, each billed as one search. `dateRange` and `sortBy` work with raw. Not combinable with `aiMode`. ``… [6806 more characters not shown]
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: 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 or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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.
Looked at Nov 20, 2026, 18:28 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://mcp.usestring.ai/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata
- https://mcp.usestring.ai/.well-known/oauth-protected-resource
- Authorization servers
- https://clerk.portal.usestring.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://mcp.usestring.ai/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata: https://mcp.usestring.ai/.well-known/oauth-protected-resource/v1/mcp to https://mcp.usestring.ai/.well-known/oauth-protected-resource
- Nov 6, 2026
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 3
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://mcp.usestring.ai/.well-known/oauth-protected-resource/v1/mcp to none
- Oct 29, 2026
- Dynamic client registration: no to yes
Findings
Matches of fixed checks, with the text they matched.
- Warnweb_access_fetch
The server marks "web_access_fetch" destructive (destructiveHint: true), and its name says "fetch", a word for reading.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":true}; The name "web_access_fetch" says "fetch": a word for reading.
- Infoweb_access_fetch
The description is 5,378 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...lenge handling is subject to the caller's String account and organization policy."
The description is 12,806 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...Requests must comply with destination policy, rate limits, and access controls."
The description is 3,710 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...e chosen action (quote, status, URL page, job list) alongside a one-line summary."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 4 more).View diff
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://mcp.usestring.ai/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata: https://mcp.usestring.ai/.well-known/oauth-protected-resource/v1/mcp to https://mcp.usestring.ai/.well-known/oauth-protected-resource
PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 3 (and 3 more).View diff
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 3
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://mcp.usestring.ai/.well-known/oauth-protected-resource/v1/mcp to none
PostureRemote posture changed. Dynamic client registration: no -> yes.View diff
- Dynamic client registration: no to yes
Install
Pinned to version 1.4.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http web-access https://mcp.usestring.ai?loginclaude mcp add --transport http web-access https://mcp.usestring.ai?loginRun 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.
{
"permissions": {
"allow": [
"mcp__web-access__web_access_search"
],
"ask": [],
"deny": [
"mcp__web-access__web_access_fetch",
"mcp__web-access__web_access_request",
"mcp__web-access__web_access_sitemap"
]
}
}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 web-access. Review it before you use it.
Capability tags behind 4 rules
- mcp__web-access__web_access_fetch untrusted-input
- mcp__web-access__web_access_request untrusted-input
- mcp__web-access__web_access_search untrusted-input
- mcp__web-access__web_access_sitemap 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.usestring/web-access/verify?hash=59db2c16f8d55b4fd2ce7884181ec58d96cc72c5b82b55c1865a01553e1cc7f8" | jq -e '.changed == false'Pinned hash 59db2c16f8d5, from Nov 16, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.usestring/web-access/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.usestring/web-access)Source: MCP Registry · repository. Synced Nov 16, 2026, 16:17 UTC.
String Web Access MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the String Web Access MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the String Web Access MCP server delete data?
- Yes. 3 tools can delete, cancel or revoke something: web_access_fetch, web_access_request and web_access_sitemap.
Can the String Web Access 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 String Web Access MCP server have?
- 4 tools: 3 destructive, 1 read. web_access_fetch, web_access_request, web_access_sitemap and web_access_search.
Does the String Web Access MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.
Does the String Web Access MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the String Web Access MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.