camelCase hump count, value discarded
Counts camelCase humps in a string over MCP and discards the input value
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About camelCase hump count, value discarded
camelCase hump count, value discarded is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
Camel-n is a small remote MCP utility that counts the humps in a camelCase identifier, the uppercase boundaries where new words start. The MCP registry entry and the repository README both state that the submitted value is discarded rather than kept, which matters if you send it anything sensitive.
It runs as a streamable-http endpoint hosted on a Cloudflare Workers domain, so an MCP client connects to a URL rather than installing a package. The registry entry lists no local packages. The repository is a collection of similarly named single-purpose servers, and camel-n is one of those, with a PascalCase sibling that does the same job for a different naming style.
It suits developers and agent builders who want an AI client to check identifier structure as one step in a larger workflow, without writing a parser for each project.
Install
Run in a terminal
claude mcp add --transport http camel-n https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/camel-n/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/camel-n/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"camel-n": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/camel-n/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"camel-n": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/camel-n/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"camel-n": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/camel-n/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"camel-n": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/camel-n/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Camel-case hump counting
- Returns the number of camelCase word boundaries found in a supplied string.
- Value discarded after use
- The README and registry entry say the input value is not retained once the count is returned.
- Remote streamable-http endpoint
- Connects to MCP clients over streamable HTTP at a hosted URL, with no local package install listed.
- Registry-listed MCP server
- Published under the official MCP registry name io.github.sadri-dridi/camel-n.
Good for
- Checking whether identifiers in a codebase follow camelCase naming
- Letting an AI coding assistant count word segments in a field or variable name
- Adding a naming-convention check to an agent workflow without sending data to a stored service
- Comparing identifier styles across a set of names in a review pass
camelCase hump count, value discarded FAQ
Does the server keep the text I send it?
The README and registry entry both say the value is discarded, meaning it is not kept after the hump count is returned.
How do I connect to it?
The registry entry lists a streamable-http remote URL on a workers.dev domain. No local package is listed.
What does it count?
It counts camelCase humps, the uppercase boundaries where a new word starts in an identifier.
How do I add camelCase hump count, value discarded to Claude Code?
Run this command in your terminal: claude mcp add --transport http camel-n https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/camel-n/mcp
What are the best alternatives to camelCase hump count, value discarded?
The closest alternatives to camelCase hump count, value discarded are PascalCase hump count, value discarded, camelCase shape, text discarded, dot.case segment count, text discarded, PascalCase token count, value discarded and dot.case segment count, value 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.