Developer documentation of lovefengis (REST API, MCP, CLI, auth) over MCP. Read-only, no auth.
Scored across 2 tools
search_docs (keyword discovery) and get_doc (full page retrieval by slug) have clearly distinct, complementary roles with no overlap. The descriptions even cross-reference each other, making the workflow unambiguous.
Both tools follow a clean, consistent verb_noun snake_case pattern (search_docs, get_doc). No deviations or mixed conventions.
Two tools is thin for a documentation server; a browse/list capability would make the surface feel complete. Still, the pair is well-scoped and each tool clearly earns its place.
Search-then-fetch covers the core documentation lookup workflow with no dead ends. Minor gaps exist: there is no way to list or browse all pages/sections without a keyword, and no index/navigation tool.
Get the full Markdown of one documentation page by slug. Slugs come from search_docs.
Inputs: slug (required).
Keyword search over the lovefengis developer documentation. Returns matching pages with slug, title, URL and a short excerpt, best match first.
Inputs: query (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Read-only MCP server over the developer docs for the portfolio's JSON API, MCP, A2A and NLWeb.
MCP server that delivers up-to-date Bitrix24 REST API documentation.
Read-only IMBA Agent API docs MCP. No register, deposit, buy, or withdraw.
Read-only MCP server that answers questions about turva.dev from its published data. Five tools return JSON: the service catalog with prices, contact and operator details, engagement principles and dated agent-readiness and security evidence with verification links. Connect over Streamable HTTP. You need no API key. The server does not scan other websites or run audits.
Add one secure layer between your agents and this server.
