PluginBench
MCP Server
Active

Leap year check MCP Server

io.github.sadri-dridi/leap-year

RepositoryRegistry
How to choose

What this kind of tool is for

  • Automate a build, test, or deployment step you repeat by hand.
  • Review or refactor code in an existing repository without leaving your agent.
  • Bridge an internal service or CLI into the agent toolset.

How to compare servers like this

Scope of control:
Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
Environment fit:
Match the runtime it expects (Node, Python, a container) to what you actually run.
Maintenance signal:
Check the last-commit date — dev tooling that lags upstream breaks first.
Config surface:
Prefer tools whose environment-variable or config keys are documented plainly.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the Leap year check MCP server?

Leap year check

How to install Leap year check

Copy-paste configuration for popular MCP clients.

transport: http
Config generated by PluginBench — verify against the source before use.
~/.cursor/mcp.json
JSON config
{
  "mcpServers": {
    "leap-year": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/leap-year/mcp"
    }
  }
}

Related MCP servers

UTC leap-year flag

0
View repository →

LEEF attr count, line discarded

0
View repository →

Less variable count, body discarded

0
View repository →

Lex rule count, body discarded

0
View repository →

HTTP status for a public library docs URL. Body discarded.

0
View repository →

Line count, text discarded

0
View repository →