← Registry

Data Collection

lyrenth.com

Reads public web pages as clean, structured Markdown documents with batch support and usage tracking.

1 endpoint3 known toolsFirst detected July 6, 2026Last detected September 6, 2026

ENDPOINT 1

https://api.lyrenth.com/mcp

No auth detected

MCP server metadata

Name
lyrenth
Version
0.1.6
Capabilities
tools.listChanged

Known tools 3

read_url

Read any public web page as a clean AIDocument: Markdown plus title, description, and structure, with navigation and boilerplate stripped.

Inferred read-only
read_urls

Read several public web pages in one batch call, each as a clean AIDocument.

Inferred read-only
check_usage

Check your Lyrenth credit usage: plan tier, credits used against your monthly limit, credits remaining, and the reset date.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.lyrenth]
url = "https://api.lyrenth.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "lyrenth": {
      "type": "http",
      "url": "https://api.lyrenth.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: lyrenth
Remote MCP URL: https://api.lyrenth.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "lyrenth": {
      "url": "https://api.lyrenth.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "lyrenth": {
      "type": "http",
      "url": "https://api.lyrenth.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "lyrenth",
  "transport": "streamable-http",
  "url": "https://api.lyrenth.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.