NLocq
NLocq is a MCP server that exposes ChainContext’s NLocq capabilities to coding agents via a hosted streamable-HTTP endpoint.
About
NLocq is a minimal Model Context Protocol server entry from ChainContext, offered as a hosted streamable-HTTP remote rather than a local stdio package. developers who already run Claude Code, Cursor, or similar MCP-capable agents can register the endpoint when they need additional chain-context capabilities from ChainContext’s ecosystem. The public registry record is sparse on tool names and scopes, so treat it as an integration hook you validate in your own client after wiring the remote URL. It fits projects that centralize agent access through MCP instead of custom SDKs, especially when you are iterating on backend or agent features and want a single HTTP endpoint to maintain. Pair it with clear API-key or auth practices on your side if the hosted service adds requirements beyond what the registry snippet shows.
- Streamable-HTTP remote at nlocq.chaincontext.dev (registry schema 2025-12-11)
- Published as chaincontext publisher tooling v1.0.0
- Server version 1.0.0 with no local package install in registry metadata
- Suited as a thin context bridge for agent workflows that already use MCP clients
NLocq by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http nlocq https://nlocq.chaincontext.dev/Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | None |
What it does
Expose ChainContext’s NLocq remote MCP endpoint so your coding agent can query chain-context data over streamable HTTP during backend or agent builds.
Who is it for?
Best when you're already on MCP and want a hosted ChainContext remote with minimal local setup.
Skip if: Skip if you need documented tool lists, offline-only stdio MCP, or full feature clarity before adoption.
What you get
After you register the remote MCP URL, your agent can invoke NLocq through the same MCP configuration you use for other HTTP servers.
- Registered HTTP MCP remote in your agent config
- Callable NLocq tools once verified against the live endpoint
By the numbers
- Registry server version 1.0.0
- Publisher tooling chaincontext v1.0.0
- Single streamable-HTTP remote URL documented in server.json
Recommended MCP Servers
0piFree, 2hr expiry agent storage to cache contexts, bridge workflows, or dump data.
100Hires AI ATS & Recruitment SoftwareOfficial 100Hires MCP: AI ATS & Recruitment Software for candidates, jobs, applications, interviews.
123elec McpInterface MCP officielle du site marchand 123elec, catalogue, stock, panier, commandes.
1stayHotel booking MCP server.2
2D Assets MCPMCP server for generating advanced mock 2D PNG assets for game prototypes.43D MeshWeaverMesh spatial optimizer reducing geometric overhead in 3D assets.How it compares
Hosted MCP remote integration, not a local PyPI/npm MCP package with enumerated tools in the registry.
FAQ
Who is dev.chaincontext/nlocq for?
Developers and small teams using MCP clients who want to attach ChainContext’s NLocq HTTP endpoint to Claude Code, Cursor, or compatible agents.
When should I use dev.chaincontext/nlocq?
Use it during Build when you are wiring agent integrations and ChainContext’s hosted NLocq service matches the context queries your workflow needs.
How do I add dev.chaincontext/nlocq to my agent?
Add the streamable-HTTP remote URL https://nlocq.chaincontext.dev to your agent’s MCP server config per your client’s HTTP MCP setup docs, then verify available tools in the client UI.