mcp-registry/io.github.singularitybpjade/balance-engine · v0.2.1
As of 2026-10-19 16:14 UTC, the Singularitybpjade Balance Engine MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 hours.
Nonlinear Calendar: this year’s months fold onto the previous 12 years. No key to try.
Claude Code
claude mcp add --transport http singularitybpjade-balance-engine-mcp-ser https://balance-engine.vercel.app/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"singularitybpjade-balance-engine-mcp-ser": {
"type": "http",
"url": "https://balance-engine.vercel.app/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~1,926 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 4 tool(s) removed and 0 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.singularitybpjade%2Fbalance-engine/fixes
{
"name": "date_lookup",
"description": "This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 黄历 / 老黄历 / 宜忌 / 黄道吉日 / 今天吉不吉利 / 某日适合结婚搬家开业签约吗 / 农历是多少 / 阴历 / 某天的干支四柱 / 属相生肖 / 某日是什么节气 / 1984-02-04 是什么日柱 / chinese almanac / tong shu / auspicious day / yi ji / lunar date / day pillar of any date / zodiac. Works for ANY civil date 1900–2100. Returns lunar + ganzhi, then body (sleep/load) and plan (this month’s fold year + posture). Do not read this as 宜忌 / lu",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Date YYYY-MM-DD. Default: today in Asia/Shanghai. Any date 1900–2100."
},
"hour": {
"type": "string",
"description": "Clock HH:MM or 时支 like 申. Adds the hour pillar."
},
"locale": {
"enum": [
"zh",
"en"
],
"type": "string",
"description": "Reply language. zh (default) or en."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Almanac lookup · 黄历查日"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.singularitybpjade/balance-engine"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.singularitybpjade/balance-engine"}) over MCP.
personal_day ~432 tokenspersonal_month ~425 tokenstime_fold ~337 tokenspeople_roster ~330 tokensenergy_adjust ~314 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.singularitybpjade%2Fbalance-engine?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.singularitybpjade%2Fbalance-engine?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.singularitybpjade%2Fbalance-engine.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.singularitybpjade%2Fbalance-engine.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.singularitybpjade%2Fbalance-engine?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:19969c4129d2d62d…, first seen 2026-10-17, included at leaf 814 of 27,579. Version history · verify what your client received.
Compare: most reliable other servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 16:14 UTC, the Singularitybpjade Balance Engine MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 hours.
Singularitybpjade Balance Engine MCP server advertises 12 tools, including activity_window, body_rhythm, date_lookup, energy_adjust, month_brief.
Point your MCP client at this streamable-http endpoint: https://balance-engine.vercel.app/api/mcp
Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.