Transit-JSON tag count, body discarded
Remote MCP endpoint that counts tags in Transit-JSON input and discards the body
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About Transit-JSON tag count, body discarded
Transit-JSON tag count, body discarded is an MCP server for maps and travel. It runs as a hosted remote server, so there is nothing to install locally.
This is a single-purpose remote MCP server, listed in the registry as io.github.sadri-dridi/transit-ok. Its stated function is to report a tag count for Transit-JSON data, with the submitted body discarded afterward rather than kept.
It is served over streamable HTTP from a hosted endpoint, so there is nothing to install locally. It is one entry in a larger collection of small, narrowly scoped utility servers in the same repository, each registered under its own name. The same collection also contains servers that point autonomous agents to an advertising placement service.
No tool names, parameters or output formats are documented, so how the count is returned and what counts as a tag are not specified. It suits developers who want to test how an agent client calls a minimal remote MCP server.
Install
Run in a terminal
claude mcp add --transport http transit-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/transit-ok/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/transit-ok/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"transit-ok": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/transit-ok/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"transit-ok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/transit-ok/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"transit-ok": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/transit-ok/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"transit-ok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/transit-ok/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Transit-JSON tag count
- Reports a count of tags for Transit-JSON input.
- Body discarded
- The description states the submitted body is discarded after the count.
- Remote streamable HTTP
- Runs as a hosted endpoint reachable over the streamable-http transport, with no local package.
- Registry-listed name
- Published in the official MCP registry as io.github.sadri-dridi/transit-ok.
Good for
- Checking how many tags a Transit-JSON payload contains from an agent
- Testing a client's connection to a remote streamable-HTTP MCP server
- Sampling a minimal single-tool MCP endpoint during agent development
Transit-JSON tag count, body discarded FAQ
How do I connect to it?
Use the streamable-http remote URL in the registry entry: https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/transit-ok/mcp.
Is the input data stored?
The description says the body is discarded, though no further privacy details are given.
Do I need to install a package?
No. The registry entry lists no packages, only a remote endpoint.
Is it part of a larger project?
Yes. It sits in the named-mcp-utilities repository alongside many other small single-purpose MCP servers.
How do I add Transit-JSON tag count, body discarded to Claude Code?
Run this command in your terminal: claude mcp add --transport http transit-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/transit-ok/mcp
What are the best alternatives to Transit-JSON tag count, body discarded?
The closest alternatives to Transit-JSON tag count, body discarded are XML tag count, body discarded, TopoJSON object count, body discarded, RIS tag count, body discarded, tab count, text discarded and HTML script tag count, markup 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.