
lovefengis MCP server
Which MCP servers are lovefengis's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-27
- Registry namecom.lovefengis/docsverified in the MCP registry
The registry name sits under lovefengis.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-27
- Tools2
- Server calls itselflovefengis-docs
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 146 ms.
- Its tools do none of the product's use cases we checked: Set up and manage Google, Meta and ChatGPT ad campaigns; Audit a website for SEO issues and prepare fixes; Check site speed and how pages appear in search.
- Checked on 2 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- What an agent can do with it0 of 3 use cases
- Use89 npm downloads a week
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer186 ms
- Space in an agent's context≈ 197 tokensthe definitions of all its tools (2), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- cannot · Set up and manage Google, Meta and ChatGPT ad campaigns
- cannot · Audit a website for SEO issues and prepare fixes
- cannot · Check site speed and how pages appear in search
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
search_docsKeyword search over the lovefengis developer documentation. Returns matching pages with slug, title, URL and a short excerpt, best match first.
get_docGet the full Markdown of one documentation page by slug. Slugs come from search_docs.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"docs": {
"type": "http",
"url": "https://lovefengis.com/mcp/docs"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http lovefengis https://lovefengis.com/mcp/docsclaude.ai, ChatGPT and other clients: add https://lovefengis.com/mcp/docs as a custom connector in the settings.
- com.lovefengis/mcpanswers, 3 toolsverified in the MCP registry
OpenAPI spec
8 paths, read 2026-10-27. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.