Skip to content

MCP servers › com.scriptmasterlabs › url-to-markdown

MCP server · registry snapshot 2026-10-29 · last tested 2026-10-29

com.scriptmasterlabs/url-to-markdown

URL to Markdown API — ScriptMasterLabs — the publisher's title

by scriptmasterlabs.com · domain (the registry's namespace rule)Website ↗

URL to Markdown for AI agents: $0.001 USDC per accepted read via x402 on Base. Failed reads free. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-29version 1.0.0streamable HTTP22 tools

Summary

com.scriptmasterlabs/url-to-markdown is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain scriptmasterlabs.com. On 2026-10-29 ProtocolProbe connected to it in read-only mode and read its inventory: 22 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
22
Last tested
2026-10-29

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-29 (squeezeos-api.onrender.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 2 tools whose name or declaration suggests they change data (execute_capability, purchase_capability_read). That is our reading of the names; we did not call them. Source: our connection, 2026-10-29.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-29
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-10-28 (registry, as of the 2026-10-29 snapshot)
First listed version
2026-10-28 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-29
Package and repository
checked 2026-10-29
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-28, listed on 2026-10-29 with version 1.0.0 (published 2026-10-28).

Source: the official MCP Registry list on 2026-10-28 and on 2026-10-29.

What it is

What does this server offer?

Observed inventory
22tools
0resources
0prompts

None of its 22 tools are described as changing anything. For 22 the reading was uncertain, so no mark is shown.

  • discover_capabilitieson 16 other servers

    “Search the live SqueezeOS capability inventory by keyword.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • limitinteger“Max results to return, 1-50.”
    • modestring“'lexical' for keyword search (always available) or 'unified' to add evidence-backed semantic context.”
    • querystringrequired“Natural-language search text, 1-500 characters.”
  • recommend_capabilityon 2 other servers

    “Return the best-matching SqueezeOS capabilities for a natural-language need.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • limitinteger“Max recommendations to return, 1-20.”
    • querystringrequired“Natural-language description of what the agent needs, 1-500 characters.”
  • list_playbookson 8 other servers

    “Filter the public ScriptMasterLabs Google Play book catalog for the job a reader is working on, for example 'x402 payments' or 'options trading'.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • jobstringrequired“What the reader is working on, 1-500 characters, e.g.”
    • limitinteger“Max titles to return, 1-10.”
  • inspect_capabilityon 2 other servers

    “Inspect one live SqueezeOS capability by its sml_id.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • probeboolean“When true, performs a real liveness probe of the capability.”
    • sml_idstringrequired“The capability's sml_id from discovery, 1-500 characters.”
  • compare_capabilitieson 5 other servers

    “Compare 2-5 live SqueezeOS capabilities side by side using real metadata.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • probeboolean“When true, performs a real liveness probe of each capability.”
    • sml_idsarrayrequired“Array of 2-5 sml_id values to compare.”
  • capability_manifeston 2 other servers

    “Read the canonical machine capability manifest generated from the live Flask route table.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • x402_contracton 4 other servers

    “Read the canonical SqueezeOS x402 v2 discovery contract.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • x402_readinesson 2 other servers

    “Check the live x402 payment-rail readiness surface.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • x402_evidenceon 2 other servers

    “Read real settlement evidence recorded by the canonical x402 rail.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • system_statuson 8 other servers

    “Read the live SqueezeOS status endpoint.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • url_to_markdownon 6 other servers

    “URL to Markdown — convert any public HTTPS URL to clean LLM-ready Markdown for $0.001 USDC per accepted read, settled via x402 on Base.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • max_charsinteger“Maximum Markdown characters to return, 1000-50000.”
    • payment_signaturestring“Canonical x402 v2 PAYMENT-SIGNATURE bound to this exact URL to Markdown challenge.”
    • urlstringrequired“Public HTTPS URL to read.”
  • “Get the dealer gamma-exposure (GEX) and pin-risk map for one US ticker from live Tradier option chains: long/short gamma regime, zero-gamma flip line, call and put walls, max open-interest pin strike…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 1 required
    • payment_signaturestring“Canonical x402 v2 PAYMENT-SIGNATURE bound to this exact challenge.”
    • symbolstringrequired“US equity or ETF ticker, e.g.”
Show 10 more tools
  • ticker_dossieron 2 other servers

    “Get a one-call intelligence profile for one US ticker: live quote, dealer gamma regime/walls/pin, unusual options flow, squeeze score, SEC fails-to-deliver plus Reg SHO threshold-list status, and the…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 1 required
    • payment_signaturestring“Canonical x402 v2 PAYMENT-SIGNATURE bound to this exact challenge.”
    • symbolstringrequired“US equity or ETF ticker, e.g.”
  • commit_discover_effectson 2 other servers

    “List the SML Commit effect atlas: every registered action, target system, owner, and cap a commit check can authorize.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • commit_read_termson 2 other servers

    “Read the live SML Commit terms: price, decision outcomes, and rules.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • read_capabilityon 1 other server

    “Read one public SqueezeOS REST path with GET.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • alternative_intentstring“Optional natural-language intent used to rank the closest SML alternative after an unsigned HTTP 402.”
    • pathstringrequired“Concrete SqueezeOS path beginning with /; do not pass a full URL.”
    • queryobject“Optional object of URL query parameters.”
  • execute_capabilityon 4 other servers

    “Execute one public SqueezeOS REST path with POST after confirm_write=true.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    6 inputs, 2 required
    • alternative_intentstring“Optional natural-language intent used to rank the closest SML alternative after an unsigned HTTP 402.”
    • bodyobject or array or string or number or boolean or null“Optional request body for POST: object, array, string, number, boolean, or null.”
    • confirm_writebooleanrequired“Explicitly authorize this POST operation.”
    • pathstringrequired“Concrete SqueezeOS path beginning with /; do not pass a full URL.”
    • payment_signaturestring“Canonical x402 v2 PAYMENT-SIGNATURE value bound to this exact target-resource challenge.”
    • queryobject“Optional object of URL query parameters.”
  • purchase_capability_readon 1 other server

    “Retrieve one paid SqueezeOS REST path with GET using caller-signed authorization for that exact resource's fresh x402 challenge.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    4 inputs, 2 required
    • alternative_intentstring“Optional natural-language intent used to rank the closest SML alternative after an unsigned HTTP 402.”
    • pathstringrequired“Concrete SqueezeOS path beginning with /; do not pass a full URL.”
    • payment_signaturestringrequired“Canonical x402 v2 PAYMENT-SIGNATURE value bound to this exact target-resource challenge.”
    • queryobject“Optional object of URL query parameters.”
  • aftersearch_resolveon 2 other servers

    “Convert a natural-language query into machine intent, a bounded Evidence Pack, and one immutable x402 job with a fresh quote pointer.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • querystringrequired“The natural-language question to compile into intent and an Evidence Pack (1-60000 chars).”
  • aftersearch_verify_serpon 2 other servers

    “Verify pasted SERP or AI-answer text, or one caller-provided public URL, against retrieved sources.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • serp_text_or_urlstringrequired“Pasted SERP/AI text or one public URL to verify (1-60000 chars).”
  • aftersearch_quoteon 2 other servers

    “Return fresh x402 PAYMENT-REQUIRED terms for one immutable job.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • job_idstringrequired“The 24-char hex job_id returned by aftersearch_resolve or aftersearch_verify_serp.”
  • aftersearch_accepton 2 other servers

    “Get accepted delivery for one immutable job with caller-supplied x402 authorization.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • job_idstringrequired“The 24-char hex job_id being settled.”
    • payment_responsestringrequired“The caller x402 payment authorization payload for this exact job, supplied as the PAYMENT-SIGNATURE value for this job.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-29.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 36
Tools with a description
100% of 22
Typical description length
543 characters

The tool set

Counted from the listing

Tools
22
Size of the list
about 12,834 tokens for an agent to load (characters ÷ 4)
Naming
22 of 22 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 22 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-29 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://squeezeos-api.onrender.com/mcp/url-to-markdown
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "url-to-markdown": {
      "url": "https://squeezeos-api.onrender.com/mcp/url-to-markdown"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "url-to-markdown": {
      "type": "http",
      "url": "https://squeezeos-api.onrender.com/mcp/url-to-markdown"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"url-to-markdown","type":"http","url":"https://squeezeos-api.onrender.com/mcp/url-to-markdown"}'
Claude Code
claude mcp add --transport http url-to-markdown https://squeezeos-api.onrender.com/mcp/url-to-markdown
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "url-to-markdown": {
      "type": "streamableHttp",
      "url": "https://squeezeos-api.onrender.com/mcp/url-to-markdown",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "url-to-markdown": {
      "httpUrl": "https://squeezeos-api.onrender.com/mcp/url-to-markdown"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.url-to-markdown]
url = "https://squeezeos-api.onrender.com/mcp/url-to-markdown"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "url-to-markdown": {
      "url": "https://squeezeos-api.onrender.com/mcp/url-to-markdown"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://squeezeos-api.onrender.com/mcp/url-to-markdown --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint squeezeos-api.onrender.com/mcp/url-to-markdownSession openedmatchesour test · 2026-10-29
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-29

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-29. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about com.scriptmasterlabs/url-to-markdown

Answered from the data above

Who publishes com.scriptmasterlabs/url-to-markdown?

The registry ties the namespace com.scriptmasterlabs to the domain scriptmasterlabs.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does com.scriptmasterlabs/url-to-markdown need an API key or sign-in?

It opened a session without any credential on 2026-10-29. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.scriptmasterlabs/url-to-markdown been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-29
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-29, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,162 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 22 tools, 0 resources, 0 prompts.
  4. 5,071 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-29; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-29
MCP capability
prompts, resources, tools
our test · 2026-10-29
Transport
streamable HTTP
registry · 2026-10-29
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-29
Lifecycle status
registry · 2026-10-29
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.scriptmasterlabs/url-to-markdown: MCP server record.” Data checked 2026-10-29. https://protocolprobe.com/mcp/servers/com.scriptmasterlabs/url-to-markdown

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.scriptmasterlabs/url-to-markdown)](https://protocolprobe.com/mcp/servers/com.scriptmasterlabs/url-to-markdown)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology