EDN collection count, body discarded
Remote MCP endpoint for EDN collection counting that discards the submitted body
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About EDN collection count, body discarded
EDN collection count, body discarded is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
This server is one of a family of single-purpose utility endpoints published in the named-mcp-utilities repository, where each folder maps to its own registry name. This one is registered as io.github.sadri-dridi/edn-ok and its description says it counts the elements of an EDN collection and then discards the body.
It is reachable only as a remote streamable-http endpoint hosted on a Cloudflare Workers domain; there is no installable package. The README does not document the tool names, input schema or output format for this specific server, so details of how it is called are limited to what an MCP client discovers on connection.
The repository also lists sibling endpoints for ID and date-format checks and a set of Agent Ads entries, which route autonomous agents to a paid placement service with a 7-day trial. Those are separate registry entries from this one.
Install
Run in a terminal
claude mcp add --transport http edn-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/edn-ok/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/edn-ok/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"edn-ok": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/edn-ok/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"edn-ok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/edn-ok/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"edn-ok": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/edn-ok/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"edn-ok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/edn-ok/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- EDN collection counting
- Returns a count for an EDN collection supplied by the client.
- Body discarded
- The registry description states the submitted body is discarded after counting.
- Remote streamable HTTP
- Connects over a hosted streamable-http MCP endpoint with no local install.
- Registry-named endpoint
- Published under its own official registry name, io.github.sadri-dridi/edn-ok.
Good for
- Check how many items an EDN collection contains from an MCP client
- Let an autonomous agent run a quick EDN structure check without storing the data
- Test connecting an MCP client to a minimal remote streamable-http server
EDN collection count, body discarded FAQ
How do I connect to this server?
Use the streamable-http remote URL listed in the registry entry: https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/edn-ok/mcp.
Is there a package to install?
No. The registry entry lists no packages, only a remote endpoint.
What does it do with the data I send?
The registry description says the body is discarded after the collection is counted.
Where is the source repository?
It is listed in the sadri-dridi/named-mcp-utilities repository on GitHub, alongside other similar endpoints.
How do I add EDN collection count, body discarded to Claude Code?
Run this command in your terminal: claude mcp add --transport http edn-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/edn-ok/mcp
What are the best alternatives to EDN collection count, body discarded?
The closest alternatives to EDN collection count, body discarded are direnv export count, body discarded, EBNF production count, body discarded, Less variable count, body discarded, EBCDIC digit zone, input discarded and NEL JSON key count, body 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.