EVE Online EST MCP Server
Used for code linting in the project development workflow.
Used for version control with repository cloning mentioned in the development setup.
Referenced in the clone URL for the repository in the development instructions.
Used for package management and running scripts for development, testing, and linting.
Used for code formatting in the development workflow.
Used with ESLint for type checking and linting in the development process.
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., "@EVE Online EST MCP Serverwhat time is it in EVE right now?"
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.
EVE Online EST MCP Server
An MCP server for EVE Online that provides EVE Server Time (EST) information and downtime calculations.
EVE Server Time (EST) is identical to UTC and is the standard time used across all EVE Online servers. This server provides current EST time and calculates time remaining until the next daily server downtime.
Features
Current EVE Server Time: Get the current time in EVE Server Time format (identical to UTC)
Downtime Information: Daily server maintenance occurs from 11:00 to 11:15 EST (UTC)
Time Until Downtime: Calculates hours and minutes until the next server downtime
Downtime Status: Indicates if the server is currently in downtime
Reliable Time Source: Uses system time with WorldTimeAPI (worldtimeapi.org) as fallback for maximum reliability
Related MCP server: MCP Time Server
Tool: getCurrentESTTime
This tool provides comprehensive EVE Online server time information:
{
"currentTime": "2025-01-08 15:30:45 EST",
"utcTime": "2025-01-08T15:30:45.123Z",
"isInDowntime": false,
"downtimeWindow": "11:00 to 11:15 EST (UTC)",
"timeUntilNextDowntime": "19h 29m",
"nextDowntimeStart": "2025-01-09 11:00:00 EST",
"timeSource": "system"
}The timeSource field indicates whether the time was obtained from the system clock ("system") or from the WorldTimeAPI fallback ("worldtimeapi").
Development
To get started, clone the repository and install the dependencies.
git clone https://github.com/kongyo2/EVE-EST-MCP.git
cd eve-online-est-mcp-server
npm install
npm run devStart the server
If you simply want to start the server, you can use the start script.
npm run startHowever, you can also interact with the server using the dev script.
npm run devThis will start the server and allow you to interact with it using CLI.
Testing
The server includes tests for time calculations and EST formatting.
npm run testThe tests verify the EVE Server Time calculations and downtime logic.
Linting
Having a good linting setup reduces the friction for other developers to contribute to your project.
npm run lintThis project uses Prettier, ESLint and TypeScript ESLint to lint the code.
Formatting
Use npm run format to format the code.
npm run formatAvailable Tools
1 toolgetCurrentESTTimeARead-only
Get current EVE Server Time (EST) which is identical to UTC, and calculate time until next server downtime. EVE Online servers go offline daily from 11:00 to 11:15 EST (UTC) for maintenance. Uses system time with WorldTimeAPI as fallback.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds valuable behavioral context beyond what annotations provide. While annotations indicate read-only and open-world operations, the description reveals specific implementation details: the tool uses system time with WorldTimeAPI as fallback, and it calculates time until the next scheduled downtime. This provides practical information about reliability and functionality that annotations don't cover.
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?
The description is perfectly concise and well-structured. It uses just two sentences that each earn their place: the first states the primary function, the second provides important operational context about daily maintenance and implementation details. There's zero wasted language or redundancy.
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?
For a parameterless tool with good annotations (readOnlyHint, openWorldHint) but no output schema, the description provides excellent context about what the tool returns (current time and downtime calculation) and how it works (system time with API fallback). The only minor gap is not explicitly describing the output format, but given the tool's simplicity and clear purpose, this is acceptable.
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?
With 0 parameters and 100% schema description coverage, the baseline would be 4. The description appropriately doesn't discuss parameters since none exist, and instead focuses on what the tool does with no inputs. This is efficient and correct for a parameterless tool.
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 clearly states the tool's purpose with specific verbs ('Get current EVE Server Time' and 'calculate time until next server downtime') and identifies the resource (EVE Online servers). It distinguishes this as a time-checking tool with maintenance scheduling functionality, which is unambiguous even without sibling tools.
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?
The description provides clear context about when to use this tool - for checking EVE Online server time and calculating downtime. It mentions the specific daily maintenance window (11:00-11:15 EST/UTC), giving users clear situational guidance. However, with no sibling tools, there's no need for alternative tool guidance, so it can't achieve a perfect 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'getCurrentESTTime' follows a clear verb_noun pattern.
One tool is too few for a server with the apparent scope of providing EVE Online EST time and downtime information. This feels thin and limited, lacking related operations like historical downtime checks or timezone conversions.
The server is severely incomplete for its domain. It only provides current time and next downtime, missing obvious gaps such as checking past downtimes, scheduling reminders, or handling timezone adjustments beyond EST/UTC.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
MCP server for aerospace calculations: orbital mechanics, ephemeris, DSN operations, ...
MCP server providing attendance data queries via the CloudTime API.
MCP server exposing live Helldivers 2 galactic war data.
Related MCP Servers
- AlicenseAqualityCmaintenanceAn MCP server that allows checking local time on the client machine or current UTC time from an NTP server234MIT
- FlicenseNot gradedqualityDmaintenanceA minimal MCP server that provides current time information with configurable timezone support set on the client side.
- AlicenseAqualityFmaintenanceMCP server providing various date/time functions including current time, timezone conversion, and relative time calculations. Supports both local stdio and remote HTTP access via Cloudflare Workers.64902MIT
- FlicenseAqualityCmaintenanceA simple MCP server that returns the current date and time with timezone information in ISO 8601, Unix timestamp, and human-readable formats.1
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kongyo2/EVE-EST-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server