Developer · Remote MCP server
Llmref
Versioned documentation registry and semantic search for AI tools and coding assistants.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
org.llmref/llmref- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-01
- Updated
- 2026-07-01
- Publisher
- org.llmref
- Namespace
- Namespace verified by the MCP Registry via the domain llmref.org · how
- Website
- llmref.org
- Repository
- github.com/reclear-io/llmref-plugin
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.llmref.org/v1/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- llmref 0.1.0 · protocol 2025-06-18
- Tools discovered
- 4:
list_projects,list_versions,resolve_docs,search_docs - Checked on
- 2026-10-05
How to connect Llmref
Llmref is a remote MCP server: there is nothing to install. Its endpoint is https://api.llmref.org/v1/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Llm Wiki MCPMCP server for Karpathy-style LLM wikis: persistent markdown your agent grows over time. | Local · stdio |
| llm-oracleUp-to-date LLM pricing + availability catalog with cited sources for AI agent routing. | Local · stdio |
| LLMemorySearch your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only. | Remote · HTTPLive check: sign-in required |
| LlmgraphInvoke deployed LLMGraph no-code LLM workflows (chat, RAG, automations) as MCP tools. | Local · stdio |
| llms.txt Checker - AI Readiness AuditChecks llms.txt, AI crawler access in robots.txt, and sitemap - with a 0-100 AI readiness score. | Remote · HTTPLive check: sign-in required |
| llms.txt for agentsAny site's llms.txt: find the covering index, read its linked docs as markdown, search sections. | Remote · HTTPLive check: ✗ no handshake |
| llms.txt GeneratorCreate, validate and audit llms.txt, incl. the Lighthouse Agentic Browsing check. | Remote · HTTPLive check: ✓ handshake |
| llms.txt ReadinessDoes a site publish llms.txt, robots permissions and a sitemap agents can use? Bounded check. | Remote · HTTPLive check: ✓ handshake |