Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Stringer CleanExtract

REMOTE · EXTRACT.GETSTRINGER.APP

Convert public HTML or a public URL into token-dense Markdown through one remote MCP tool.

0 this week 73 Trust /100

Last scanned (18 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 465 tokens (~232/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 9 Oct 26 0
    • Stability: fail → pass ▲ security
    • Schema quality: pass → fail ▼ functional
  • 4 Oct 26 0
    • Stability: pass → fail ▼ security
  • 29 Sept 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 0
    • Tool “clean_extract” rewrote its description, which is the text the model reads security
    • Schema quality: 77 → 140 ▼ functional
    • Server version: 0.3.0 → 0.4.0 functional
    • New tool “clean_extract_outline” functional
    • “clean_extract” added an optional parameter “sections” cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://extract.getstringer.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=getstringer.app CN=WE1,O=Google Trust Services,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 ae403816f48b8acb0e54835cd532172b
SANs: getstringer.app, extract.getstringer.app, *.extract.getstringer.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of extract.getstringer.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
getstringer.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://extract.getstringer.app/mcp Verified 200
http (plaintext) http://extract.getstringer.app/mcp Inconclusive 405
MCP tools · 2 exposed · ~374 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
clean_extract ~241

Extract a full page or selected sections from a public URL or raw HTML as clean Markdown, with navigation, scripts and page chrome removed. Use it instead of a raw fetch when a task needs the text of documentation, an article, an RFC or another reference page: in a five-site benchmark the Markdown was 62% fewer estimated tokens than the HTML. Call the free clean_extract_outline first on a long page, then pass only the section ids you need. A call is charged only when it returns usable content; the first 3 usable extraction calls are free, total, then USD 0.05. Uncharged failures name upstream_timeout, upstream_http_error, bot_challenge, js_shell, empty_extraction, or sections_not_found. Recoverable structured data names fallback_used. Every success reports extraction_quality and extraction_content_ratio_band.

NameTypeReqDescription
max_output_bytesinteger–Optional maximum UTF-8 byte length of the returned Markdown.
sectionsarray–Optional ids from clean_extract_outline. Return only these sections in document order.
url_or_htmlstringyesA public HTTP(S) URL or a raw HTML string to convert into Markdown.

No output schema declared.

No examples provided.

clean_extract_outline ~133

Free outline with section ids, headings, byte sizes, and a fingerprint, without page body text or payment. It never uses the free extraction allowance. Use it first to see what a long page contains and which sections are worth reading. A later clean_extract call can select sections and is charged only when it returns usable content. Uncharged failures name upstream_timeout, upstream_http_error, bot_challenge, js_shell, empty_extraction, or sections_not_found. Recoverable structured data names fallback_used.

NameTypeReqDescription
url_or_htmlstringyesA public HTTP(S) URL or a raw HTML string to convert into Markdown.

No output schema declared.

No examples provided.

Install

How do I install the Stringer CleanExtract MCP server?

Stringer CleanExtract is a hosted endpoint at https://extract.getstringer.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · extract.getstringer.app

# add to Claude Code
claude mcp add --transport http app-getstringer-cleanextract 'https://extract.getstringer.app/mcp'
Common questions

What is the Stringer CleanExtract MCP server?

Stringer CleanExtract is an MCP server listed in the public MCP registry as app.getstringer/cleanextract. Convert public HTML or a public URL into token-dense Markdown through one remote MCP tool. This page covers its hosted endpoint (https://extract.getstringer.app/mcp).

Is the Stringer CleanExtract MCP server safe to use?

Stringer CleanExtract scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Stringer CleanExtract MCP server expose?

Stringer CleanExtract exposes 2 tools: clean_extract, clean_extract_outline. Their descriptions and schemas cost roughly 374 tokens of context every time the server is loaded.

Does the Stringer CleanExtract MCP server require authentication?

No. We connected to Stringer CleanExtract without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Stringer CleanExtract MCP server still maintained?

Stringer CleanExtract is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Stringer CleanExtract MCP server?

VerifyMCP ran 11 checks on Stringer CleanExtract, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Stringer CleanExtract: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.