Developer · Remote MCP server
lurq
Verify npm packages before your AI agent installs them: hallucinations, advisories, API drift.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.jadenryu/lurq- Version
- 0.1.7
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-13
- Updated
- 2026-09-13
- Publisher
- jadenryu (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/jadenryu) · how
- Website
- www.lurq.run
- Repository
- github.com/jadenryu/lurq
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.lurq.run/mcp | Authorization (required, secret) |
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
- lurq 0.1.9 · protocol 2025-06-18
- Tools discovered
16 - show names
evaluate,policy,compare,compat,verify,usage,diagram,resolve_surface,diff_surface,mcp_stack,mcp_surface,mcp_drift,connect_check,audit,capabilities,report_outcome- Checked on
- 2026-10-05
How to connect lurq
lurq is a remote MCP server: there is nothing to install. Its endpoint is https://api.lurq.run/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.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
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 |
|---|---|
| Lucius MCPMCP server for managing Allure TestOps tests, launches, plans, defects, and metadata. | Local · stdio |
| LuminRead-only access to a Lumin project's logs, metrics, uptime checks, alerts and infrastructure. | Remote · HTTPLive check: sign-in required |
| Lumino MCP ServerAI-powered SRE observability for Kubernetes/OpenShift with 40+ Tekton debugging tools. | Local · stdio |
| LungeAgent-native API client: execute/test REST/GraphQL/WS/SSE with assertions, extraction, collections. | Local · stdio |
| LynxLynxMCP: 100% local MCP server for the code questions grep can't answer: call graph, hybrid search. | Local · stdio |
| LyssnaQuery and summarize research data across tests and surveys. | Remote · HTTPLive check: sign-in required |
| M1ndThe shell around your coding agent: a neuro-symbolic code graph with calibrated trust, via MCP. | Local · stdio |
| M3 MemoryLocal-first memory - 100+ tools, 99.2% LongMemEval-S retrieval@10, hybrid search, GDPR, no cloud. | Local · stdio |