# Lovely Router (remote · lovelyrouter.com)

One MCP URL for web search, page reading, pay-per-result data tools and a browser agent.

- Trust score: 56/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `lovelyrouter.com`: 56/100 (this document), [markdown](https://verifymcp.io/servers/com-lovelyrouter-mcp/lovelyrouter.md), [page](https://verifymcp.io/servers/com-lovelyrouter-mcp/lovelyrouter)

## Channel facts

- Endpoint: `https://lovelyrouter.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 13 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2340 tokens (~180/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Lovely Router MCP server?

Lovely Router is a hosted endpoint at https://lovelyrouter.com/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.

### Claude

```bash
claude mcp add --transport http com-lovelyrouter-mcp 'https://lovelyrouter.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-lovelyrouter-mcp": {
      "url": "https://lovelyrouter.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-lovelyrouter-mcp": {
      "type": "http",
      "url": "https://lovelyrouter.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-lovelyrouter-mcp]
url = "https://lovelyrouter.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-lovelyrouter-mcp": {
      "type": "remote",
      "url": "https://lovelyrouter.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-lovelyrouter-mcp --url 'https://lovelyrouter.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-lovelyrouter-mcp:
    url: "https://lovelyrouter.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-lovelyrouter-mcp": {
      "Transport": "http",
      "Url": "https://lovelyrouter.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-lovelyrouter-mcp -t streamable-http -u 'https://lovelyrouter.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-lovelyrouter-mcp": {
      "type": "http",
      "url": "https://lovelyrouter.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 55, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 55)

First indexed and scored.

## MCP tools (13)

### `web_search` (~232 tokens)

Search the web (pages, news, docs, blogs) and get up to 50 results with title, URL, date and a summary written for you to read. Use it first whenever you need to look something up: one call, $0.0009 per search, nothing when there are no results. Query operators: site:example.com (several: site:a.com OR site:b.com), -site:example.com, "exact phrase", -word, lang:en (or lang:zh,en), after:2026-01-01, before:2026-06. For Reddit, X/Twitter, YouTube, Google Maps, Amazon, TikTok and other platforms use suggest_tools and run_tool instead.

Input parameters:

- `count` (number): results, 1–50 (default 10; same price)
- `need_content` (boolean): also return each page's text (long); usually the summary is enough
- `query` (string, required): 1–128 characters, operators allowed
- `question` (string): optional: the user's original question, to rank results better

### `web_fetch` (~194 tokens)

Read one web page as clean Markdown (title and text, no menus or ads). Always use this, not browser_run, when you only need what a page says. For YouTube, Reddit, X, TikTok, Instagram, LinkedIn, Google Maps or Amazon pages use suggest_tools and run_tool instead: they return the data itself (video details, transcripts, comments, posts, reviews, prices) structured and complete. $0.0009 per page, nothing if it cannot be read. Long pages come in parts: to read on, call again with the run_id and offset from the answer (free). It cannot open localhost, private addresses or files in your sandbox.

Input parameters:

- `offset` (number): character to start from, with run_id
- `run_id` (string): to read on in a page fetched before (no new charge)
- `url` (string): a public http(s) URL

### `generate_image` (~366 tokens)

Create an image from a description with GPT Image 2.5 (GPT Image 2 as backup): illustrations, photos, product shots, posters, icons, diagrams with little text, UI mockups. Give reference images in `images` to edit a picture or to keep a product, logo, person or style the same. $0.04 per image, any size, with or without references; nothing if it fails. It takes 30 s to 2 min. The answer is a download link that works for 24 hours without a key: save the file with the curl command it gives. If the image is not ready within the wait, call get_image with the job id (do not generate again: that is a second image, billed again).

Input parameters:

- `images` (array): optional reference images (up to 16), PNG, JPEG or WebP: public http(s) URLs (an earlier generate_image link works) or data: URLs (a local file: "data:image/png;base64,$(base64 -w0 file.png)"). Say i…
- `prompt` (string, required): what to draw: subject, style, composition, colors, any text it must show (exact wording in quotes)
- `size` (string): 1024x1024 (default), 1536x1024 (landscape), 1024x1536 (portrait), 2048x2048, 3840x2160, or WIDTHxHEIGHT with both sides multiples of 16 and the long side at most 3840; "auto" lets the model choose. S…

### `get_image` (~47 tokens)

An image from generate_image that was still being made: waits for it, then returns its download link. Free.

Input parameters:

- `job_id` (string, required): the img_… id generate_image returned

### `search_tools` (~85 tokens)

Find data tools for a platform by describing what you need (Google Maps, TikTok, Instagram, LinkedIn, Amazon, Reddit, X, YouTube, reviews, jobs…). Returns tool ids with prices. For plain web search use web_search.

Input parameters:

- `limit` (number)
- `query` (string, required): e.g. "tiktok comments" or "google maps reviews"

### `suggest_tools` (~154 tokens)

Describe the whole task (e.g. "find vegan restaurants in Austin and summarise their latest reviews", "get the transcript and top comments of this YouTube video") and get an ordered plan in ~0.5s: the tool to run first, an optional second tool, close alternatives, each with an example input to adapt (see input_required) and the estimated cost. Free. Use it first whenever you need data from YouTube, Reddit, X, TikTok, Instagram, LinkedIn, Google Maps, Amazon, job boards or similar sites: a data tool returns it structured in one call, much faster than fetching or scraping their pages.

Input parameters:

- `limit` (number)
- `task` (string, required)

### `get_tool` (~64 tokens)

A tool's input schema (field descriptions carry its query syntax), an example input and its price. Read it before run_tool unless suggest_tools already gave you example_input: run_tool rejects input that doesn't match the schema.

Input parameters:

- `tool` (string, required): tool id from search_tools

### `run_tool` (~261 tokens)

Run a data tool (an id from suggest_tools or search_tools) and get its results. `input` must follow the tool's input_schema: start from suggest_tools' example_input or get_tool's example and change only the values. It waits for the results; a longer job answers with a run_id — then call get_run with it (do not run the tool again). Results come back compact (empty fields dropped, long text cut, about 12,000 characters at most): pass `fields` to keep only the keys you need, and call get_run with `offset` for more items. Billed per call + per result, capped by max_results: ask for only as many results as the task needs. Never run a tool again to see other fields or more of the same results: get_run re-reads a finished run for free.

Input parameters:

- `fields` (array): keep only these keys of each result, e.g. ["title","url","score","createdAt"]
- `input` (object, required): follows the tool's input_schema
- `max_results` (number): cap on billed results (default: the tool default); at least the tool's min_results, or the run is refused
- `tool` (string, required)

### `get_run` (~88 tokens)

Status and results of a tool run: waits for it to finish, then returns its results compact. `offset` pages through the items; `fields` keeps only the keys you need. Free: use it to re-read a finished run with other fields instead of running the tool again.

Input parameters:

- `fields` (array)
- `offset` (number)
- `run_id` (string, required)

### `browser_run` (~474 tokens)

Run an AI browser agent on a website you have to interact with: log in, click through, fill and submit forms, multi-page flows. To read what a page says use web_fetch, to find pages use web_search: both are faster and cheaper. The browser runs in the cloud and cannot open localhost or private addresses. Give a goal (with every value it needs) and a start URL; it navigates, fills forms and reports back. It can log in with secrets the user saved in their account vault (pass their names — values never reach any model), resume a saved session (profile), and pause to ask a question, hand the browser to a human (CAPTCHA) or get approval before a purchase. Billed per step. Returns the run after up to ~45s; poll with browser_status.

Input parameters:

- `approve` (string): pause for approval before risky submits (default risky)
- `files` (array): names of files the user uploaded (/v1/browser/files) that the agent may attach to forms; ["*"] = all
- `goal` (string, required)
- `human_timeout_minutes` (number): how long to wait for a human reply/approval, 1–1440 minutes (default 30, or 5 when started by a cloud agent); time beyond 1 minute per step costs $0.005/min
- `max_steps` (number)
- `mode` (string): fast (default, $0.006/step) or accurate ($0.012/step: looks at screenshots when unsure and can run read-only code to read data; higher success on hard sites)
- `model` (string): optional model id from /v1/models (e.g. claude-sonnet-5.5) for the agent's reasoning; default: included model. Its tokens are billed at normal price × 1.2 on top of the steps
- `output_schema` (object): JSON Schema (or {"field": "type"} shorthand) for structured output returned in data
- `profile` (string): saved profile to start from (logged-in session)
- `save_profile` (string): save the session under this name when done
- `secrets` (array): vault secret names the agent may fill
- `start_url` (string, required)

### `browser_status` (~67 tokens)

Status of a browser run (waits up to ~45s for progress). When status is waiting_for_human, "needs" says what it needs: a question to answer, an approval, or a takeover (live_view_url for the user).

Input parameters:

- `run_id` (string, required)

### `browser_reply` (~111 tokens)

Reply to a browser run waiting for a human: {"answer": "…"} for a question, {"approve": true|false} for an approval, {"done": true} after the user finished a takeover. Codes and passwords the user gives should be sent by them through the API "secret" reply, not through this tool.

Input parameters:

- `answer` (string)
- `approve` (boolean)
- `done` (boolean)
- `reason` (string)
- `run_id` (string, required)

### `browser_takeover` (~47 tokens)

Ask a browser run to hand the browser to the user now; the run status then carries a live_view_url.

Input parameters:

- `instructions` (string)
- `run_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-lovelyrouter-mcp/lovelyrouter#diagnostics

## Score history

- 2026-11-21: 56
- 2026-11-20: 56
- 2026-11-19: 56
- 2026-11-18: 55
- 2026-11-17: 55

## Common questions

### What is the Lovely Router MCP server?

Lovely Router is an MCP server listed in the public MCP registry as com.lovelyrouter/mcp. One MCP URL for web search, page reading, pay-per-result data tools and a browser agent. This page covers its hosted endpoint (https://lovelyrouter.com/mcp).

### Is the Lovely Router MCP server safe to use?

Lovely Router scores 56 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 Lovely Router MCP server expose?

Lovely Router exposes 13 tools: web_search, web_fetch, generate_image, get_image, search_tools, and 8 more. Their descriptions and schemas cost roughly 2,190 tokens of context every time the server is loaded.

### Does the Lovely Router MCP server require authentication?

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

### Is the Lovely Router MCP server still maintained?

Lovely Router 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 Lovely Router MCP server?

VerifyMCP ran 11 checks on Lovely Router, 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 Lovely Router: 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.

## Links

- Remote endpoint: https://lovelyrouter.com/mcp
- Authorisation metadata: https://lovelyrouter.com/.well-known/oauth-protected-resource/mcp
- Website: https://lovelyrouter.com/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/com-lovelyrouter-mcp/lovelyrouter.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-lovelyrouter-mcp/lovelyrouter/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-lovelyrouter-mcp/lovelyrouter.json
- HTML version of this page: https://verifymcp.io/servers/com-lovelyrouter-mcp/lovelyrouter
