INDIVIDUAL MCP TOOL
resolve_surface
What a package version ACTUALLY exports at runtime, extracted from its shipped JavaScript rather than from documentation or the model's memory: names and arity, not type signatures (use usage for those).
LIVE ENDPOINT
https://api.lurq.run/mcp
Connect to this endpoint to inspect the live schema for resolve_surface and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.lurq]
url = "https://api.lurq.run/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"lurq": {
"type": "http",
"url": "https://api.lurq.run/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: lurq
Remote MCP URL: https://api.lurq.run/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"lurq": {
"url": "https://api.lurq.run/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"lurq": {
"type": "http",
"url": "https://api.lurq.run/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "lurq",
"transport": "streamable-http",
"url": "https://api.lurq.run/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
evaluate— Full evidence read for one npm package: health and quality scores and the signals behind them, advisories, the shared safety verdict, a summary and a usage guide.policy— The rules this account's selection policy enforces on which packages you may add: denied packages (with the reason), license allowlist, confidence, advisory, adoption, staleness and bundle-size floors.compare— Side-by-side comparison of 2–5 npm packages you are choosing between, ranked by health score.compat— Check whether a set of packages forms a coherent stack.verify— Confirm an npm package is real, healthy, and not risky before installing: guards against hallucinated or typosquatted names, deprecations and known advisories, and returns a safety verdict with its reasons and what was not checked.usage— A package version's TYPED API: exported symbols and their signatures from its shipped .diagram— Emit a reference-architecture Mermaid diagram for a stack you have already chosen (package names).diff_surface— What changed in a package's runtime surface between two versions: symbols removed, added, and arity changes, plus renames the package itself proves (a removed name that shared one declaration with a name the new version still exports).