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.

Lovely Router

REMOTE · LOVELYROUTER.COM

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

Available components

56 Trust /100

Last scanned (17 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 Usability61
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 58% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 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 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.

  • 19 Nov 26 +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.

  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 55

    First indexed and scored.

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://lovelyrouter.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lovelyrouter.com CN=WE1,O=Google Trust Services,C=US 17 Nov 2026 15 Feb 2027 ECDSA 256 ECDSA-SHA256 65d087b4b4be292d0ee7dbec17976c7a
SANs: lovelyrouter.com, uncensored.lovelyrouter.com, *.uncensored.lovelyrouter.com
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 lovelyrouter.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
lovelyrouter.com. 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://lovelyrouter.com/mcp Verified 200
http (plaintext) http://lovelyrouter.com/mcp Inconclusive 405
MCP tools · 13 exposed · ~2,190 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
browser_reply ~111

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.

NameTypeReqDescription
answerstring––
approveboolean––
doneboolean––
reasonstring––
run_idstringyes–

No output schema declared.

No examples provided.

browser_run ~474

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.

NameTypeReqDescription
approvestring–pause for approval before risky submits (default risky)
filesarray–names of files the user uploaded (/v1/browser/files) that the agent may attach to forms; ["*"] = all
goalstringyes–
human_timeout_minutesnumber–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_stepsnumber––
modestring–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)
modelstring–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_schemaobject–JSON Schema (or {"field": "type"} shorthand) for structured output returned in data
profilestring–saved profile to start from (logged-in session)
save_profilestring–save the session under this name when done
secretsarray–vault secret names the agent may fill
start_urlstringyes–

No output schema declared.

No examples provided.

browser_status ~67

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).

NameTypeReqDescription
run_idstringyes–

No output schema declared.

No examples provided.

browser_takeover ~47

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

NameTypeReqDescription
instructionsstring––
run_idstringyes–

No output schema declared.

No examples provided.

generate_image ~366

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).

NameTypeReqDescription
imagesarray–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…
promptstringyeswhat to draw: subject, style, composition, colors, any text it must show (exact wording in quotes)
sizestring–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…

No output schema declared.

No examples provided.

get_image ~47

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

NameTypeReqDescription
job_idstringyesthe img_… id generate_image returned

No output schema declared.

No examples provided.

get_run ~88

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.

NameTypeReqDescription
fieldsarray––
offsetnumber––
run_idstringyes–

No output schema declared.

No examples provided.

get_tool ~64

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.

NameTypeReqDescription
toolstringyestool id from search_tools

No output schema declared.

No examples provided.

run_tool ~261

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.

NameTypeReqDescription
fieldsarray–keep only these keys of each result, e.g. ["title","url","score","createdAt"]
inputobjectyesfollows the tool's input_schema
max_resultsnumber–cap on billed results (default: the tool default); at least the tool's min_results, or the run is refused
toolstringyes–

No output schema declared.

No examples provided.

search_tools ~85

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.

NameTypeReqDescription
limitnumber––
querystringyese.g. "tiktok comments" or "google maps reviews"

No output schema declared.

No examples provided.

suggest_tools ~154

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.

NameTypeReqDescription
limitnumber––
taskstringyes–

No output schema declared.

No examples provided.

web_fetch ~194

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.

NameTypeReqDescription
offsetnumber–character to start from, with run_id
run_idstring–to read on in a page fetched before (no new charge)
urlstring–a public http(s) URL

No output schema declared.

No examples provided.

web_search ~232

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.

NameTypeReqDescription
countnumber–results, 1–50 (default 10; same price)
need_contentboolean–also return each page's text (long); usually the summary is enough
querystringyes1–128 characters, operators allowed
questionstring–optional: the user's original question, to rank results better

No output schema declared.

No examples provided.

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.

remote · lovelyrouter.com

# add to Claude Code
claude mcp add --transport http com-lovelyrouter-mcp 'https://lovelyrouter.com/mcp'
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.