Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@is-even-mcp Is 42 even?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
is-even-mcp is a popular MCP library, which climbed to the all-time high of the /r/mcp for a number of months.
Essentially, it's an MCP server, a connector for AI agents, that helps them do complex math such as determining if a number is even, or if it is not even.
is-even-mcpHelps you know whether a number is even or not.
This is a TypeScript-based MCP server that implements the evenness algorithm in a way accessible to AI agents.
Related MCP server: Euclid
Install dependencies:
npm installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watchTo use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"is-even": {
"command": "/path/to/is-even/build/index.js"
}
}
}Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspectorThe Inspector will provide a URL to access debugging tools in your browser.
Checks if a given number is even.
| Name | Required | Description | Default |
|---|---|---|---|
| number | Yes | The number to check. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It correctly implies a pure, read-only check with no side effects. However, it could explicitly state that it returns a boolean, though this is obvious.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise at 7 words, with no wasted words. Perfectly appropriate for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (1 required param, no output schema, no annotations), the description is minimally sufficient. It could mention the return type for completeness, but is not necessary.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a clear parameter description. The description adds no additional meaning beyond the schema, meeting the baseline expectation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Checks if a given number is even' uses a specific verb and resource, clearly stating what the tool does. With no sibling tools, no differentiation needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or alternative guidance. For a simple parity check, the description implies its usage, but lacks any contextual hints or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v4.2.0is_evenOnly one tool exists, so there is no risk of ambiguity or misselection.
The single tool name 'is_even' is clear and follows a descriptive pattern.
One tool is appropriate for a server dedicated solely to checking parity, which is a single operation.
The server fully covers its domain: checking if a number is even. No additional operations are needed.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
500+ deterministic tools for AI agents: math, conversion, validation, hashing, encoding, date/time.
Machine-readable utilities and datasets for AI agents.
Precision math engine for AI agents. 203 exact methods. Zero hallucination.
Exact hashing, base64/hex/URL encoding, JWT decoding and UUIDs for AI agents. No auth required.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jamieday/is-even-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
