URL path segment count, query discarded
Remote MCP utility that counts URL path segments and discards the query string
- Pricing
- Open source
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About URL path segment count, query discarded
URL path segment count, query discarded is an open-source MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
This server is one entry in a collection of small, single-purpose MCP utilities published under the sadri-dridi registry namespace. Its job is narrow: it reports how many segments a URL path contains, and the query portion is thrown away rather than kept.
It is reachable only as a remote streamable-http endpoint hosted on a Cloudflare Workers domain, with no installable package. Clients connect to the URL listed in the registry entry. The README describes the collection as intake endpoints for autonomous clients, and it does not document specific tool names or parameters for this server.
It suits agent developers who want a trivial, stateless check on URL structure without writing the logic themselves. The README also lists a separate set of Agent Ads endpoints in the same repository, which are unrelated to this utility.
Install
Run in a terminal
claude mcp add --transport http url-path-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/url-path-ok/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/url-path-ok/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"url-path-ok": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/url-path-ok/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"url-path-ok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/url-path-ok/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"url-path-ok": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/url-path-ok/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"url-path-ok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/url-path-ok/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- URL path segment count
- Reports the number of segments in a URL path.
- Query string discarded
- The query portion of the URL is dropped instead of being retained.
- Remote streamable-http
- Runs as a hosted endpoint, so there is nothing to install locally.
- Registry-named endpoint
- Published in the official MCP registry as io.github.sadri-dridi/url-path-ok.
Good for
- Checking how deep a URL path is inside an agent workflow
- Normalising URLs by ignoring query parameters before analysis
- Giving an MCP client a lightweight URL-shape check without custom code
Pricing
Open source
URL path segment count, query discarded FAQ
How do I connect to this server?
Use the streamable-http remote URL from the registry entry: https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/url-path-ok/mcp.
Does it need a local install?
No. The registry entry lists no packages, only a remote endpoint.
What happens to the query string?
According to its description, the query is discarded.
What is the registry name?
io.github.sadri-dridi/url-path-ok.
Is URL path segment count, query discarded free?
Yes. URL path segment count, query discarded is open source, so you can use and self-host it for free.
How do I add URL path segment count, query discarded to Claude Code?
Run this command in your terminal: claude mcp add --transport http url-path-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/url-path-ok/mcp
What are the best alternatives to URL path segment count, query discarded?
The closest alternatives to URL path segment count, query discarded are URL path length, URL discarded, URL path only, Word count, text discarded, URL host only and URL-ish token count, text discarded.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.