MCP servers › jp.bestcalendar › koyomi
MCP server · registry snapshot 2026-10-26 · last tested 2026-10-26
jp.bestcalendar/koyomi
ベストカレンダー 暦データ — the publisher's title
by bestcalendar.jp · domain (the registry's namespace rule)Website ↗
Japanese calendar data (rokuyo, lucky days, solar terms, holidays, moon, sunrise), 1926-2080. — the publisher's description
Summary
jp.bestcalendar/koyomi is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain bestcalendar.jp. On 2026-10-26 ProtocolProbe connected to it in read-only mode and read its inventory: 16 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Tools
- 16
- Last tested
- 2026-10-26
Tool list size
8,200 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (16 tools). Counted with Anthropic's token counter on 2026-10-26, from the tool list we read on 2026-10-26. Median across 23,424 counted servers: 2,725 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-10-26 (bestcalendar.jp), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.0.0).
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-26
- Mode
- read-only (no tool calls)
- Latest version
- 1.0.0, published 2026-10-25 (registry, as of the 2026-10-26 snapshot)
- First listed version
- 2026-10-25 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-10-26
- Package and repository
- checked 2026-10-26
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-10-24, listed on 2026-10-26 with version 1.0.0 (published 2026-10-25).
Source: the official MCP Registry list on 2026-10-24 and on 2026-10-26.
What it is
What does this server offer?
Observed inventoryNone of its 16 tools are described as changing anything. For 16 the reading was uncertain, so no mark is shown.
- get_koyomi_day
“指定した日の暦: 和暦・旧暦(閏月)・六曜・吉日・不成就日・二十四節気/雑節・日干支・月齢と朔弦望の時刻・祝日・月食・年と月の九星。国立天文台・内閣府の公表値と照合したデータ(1926〜2080年)。”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
datestringrequired“YYYY-MM-DD(1926-01-01〜2080-12-31)”
- search_lucky_days
“期間(366日まで)の中から、六曜(大安・友引など)と吉日(一粒万倍日・天赦日・寅の日など)の条件に合う日を探す。曜日で絞る・不成就日を除くこともできる。結果は200件まで。”
Publisher declares: read-only yes · destructive no · open-world no
6 inputs, 3 required
startstringrequired“YYYY-MM-DD(1926-01-01〜2080-12-31)”endstringrequired“YYYY-MM-DD(1926-01-01〜2080-12-31)”kindsarrayrequired“大安 友引 先勝 先負 仏滅 赤口 一粒万倍日 天赦日 神吉日 大明日 天恩日 母倉日 月徳日 寅の日 巳の日 己巳の日 不成就日”matchstring“any=どれかに当たる日(既定)、all=すべてに当たる日”weekdaysarray“曜日で絞る(例: ["土", "日"])”exclude_fujojuboolean“不成就日を除く”
- convert_wareki_eto
“西暦の年(1926〜2080)を和暦(改元の年は両方)・十干十二支・年の九星に、または日付を和暦・本命星・月命星に換算する。year か date のどちらかを指定。”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs
yearintegerdatestring“YYYY-MM-DD(1926-01-01〜2080-12-31)”
- get_sun_moon_times
“日の出・日の入り・月の出・月の入り・南中の時刻。指定した日・都道府県(47都道府県の代表地点)の日の出・南中・日の入りと、月の出・南中・月の入り(日本時間)。国立天文台「各地のこよみ」と同じ定義。”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 2 required
datestringrequired“YYYY-MM-DD(1926-01-01〜2080-12-31)”prefecturestringrequired“都道府県名(例: 東京都・大阪府・北海道)”
- list_holidayson 11 other servers
“国民の祝日・振替休日・国民の休日の一覧(内閣府の公表値と照合済み)。year(1926〜2080)か、start と end(366日まで)で指定。”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs
yearintegerstartstring“YYYY-MM-DD(1926-01-01〜2080-12-31)”endstring“YYYY-MM-DD(1926-01-01〜2080-12-31)”
- get_solar_term_times
“二十四節気の節入りの日時(日本標準時。秒までと、分に四捨五入した値)。立春・春分・夏至・秋分・冬至などが何時何分か。year(1926〜2080)か、start と end(366日まで)で指定。国立天文台 暦要項と照合済み。”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs
yearintegerstartstring“YYYY-MM-DD(1926-01-01〜2080-12-31)”endstring“YYYY-MM-DD(1926-01-01〜2080-12-31)”
- get_moon_phaseson 4 other servers
“朔(新月)・上弦・望(満月)・下弦の瞬間(日本標準時・秒まで)の一覧。year(1926〜2080)か、start と end(366日まで)で指定。国立天文台の暦要項と照合済み。”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs
yearintegerstartstring“YYYY-MM-DD(1926-01-01〜2080-12-31)”endstring“YYYY-MM-DD(1926-01-01〜2080-12-31)”
- get_koyomi_entity
“名前(例: 春分の日・土用の丑の日・十五夜・一粒万倍日・戌の日・不成就日・節分・彼岸)から、その年の日付・次はいつ・あと何日・定義・根拠を返す。二十四節気・雑節の名前(例: 秋分・春分・二百十日・春の彼岸入り)でも引ける。year を指定するとその年、from_date(省略時は今日)を指定すると次の日。”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs, 1 required
namestringrequired“名前・読み・別名・slug”yearintegerfrom_datestring“YYYY-MM-DD(1926-01-01〜2080-12-31)”
- get_moon_events
“月食(皆既・部分・半影、日本での見え方と時刻)とスーパームーンの一覧。year(1926〜2080)か、start と end(366日まで)で指定。”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs
yearintegerstartstring“YYYY-MM-DD(1926-01-01〜2080-12-31)”endstring“YYYY-MM-DD(1926-01-01〜2080-12-31)”
- get_rokuyo_hours
“指定した日の六曜と、時間帯ごとの吉凶(例: 先勝は午前が吉、赤口は正午前後だけ吉)。暦注の慣行による。”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
datestringrequired“YYYY-MM-DD(1926-01-01〜2080-12-31)”
- get_old_time
“日本時間の日時から、その日の明六つ・暮六つ(国立天文台の定義)と、不定時法の刻(暮六つ・暁九つ など)、十二辰刻(丑三つ時 など)を返す。地点は都道府県(省略時は東京都)。”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 1 required
datetimestringrequired“YYYY-MM-DDTHH:MM(日本時間)”prefecturestring“都道府県名(省略時は東京都)”
- count_days
“2 つの日付の間の日数(開始日・終了日を含めるか選べる)と営業日数(土日祝を除く。定休の曜日・お盆・年末年始・個別の休業日と営業日も指定できる)。数え方は /tools/date-calculator と同じ。business_count_start: true のときは営業日数に開始日も数え、既定の false は開始日を数えない(ある月の営業日の数は、start を 1 日・end を末日に…”
Publisher declares: read-only yes · destructive no · open-world no
11 inputs, 2 required
startstringrequired“YYYY-MM-DD(1926-01-01〜2080-12-31)”endstringrequired“YYYY-MM-DD(1926-01-01〜2080-12-31)”include_startboolean“日数に開始日を含める(既定 true)”include_endboolean“日数に終了日を含める(既定 false)”business_count_startboolean“営業日数に開始日も数える(既定 false)”closed_weekdaysarray“定休の曜日(既定は ["土", "日"]。空の配列なら曜日では休まない)”close_holidaysboolean“祝日(振替休日・国民の休日を含む)を休む(既定 true)”obonboolean“お盆 8/13〜16 を休む(既定 false)”nenmatsuboolean“年末年始 12/29〜1/3 を休む(既定 false)”closed_datesarray“個別の休業日”open_datesarray“個別の営業日(祝日や定休日でも営業する日)”
Show 4 more tools
- add_dayson 2 other servers
“日付の N 日後・N 日前、または N 営業日後・前(business: true。土日祝を除く。定休の曜日・お盆・年末年始・個別の指定も可)。基準日は数えない。n が負なら前(締め切りの逆算)。”
Publisher declares: read-only yes · destructive no · open-world no
9 inputs, 2 required
datestringrequired“YYYY-MM-DD(1926-01-01〜2080-12-31)”nintegerrequired“日数(負なら前)。暦日は 1926〜2080 年の範囲に収まる限り何日でも、営業日は ±2000(暦日 3,000 日まで進む)”businessboolean“営業日で数える(既定 false)”closed_weekdaysarray“定休の曜日(既定は ["土", "日"]。空の配列なら曜日では休まない)”close_holidaysboolean“祝日(振替休日・国民の休日を含む)を休む(既定 true)”obonboolean“お盆 8/13〜16 を休む(既定 false)”nenmatsuboolean“年末年始 12/29〜1/3 を休む(既定 false)”closed_datesarray“個別の休業日”open_datesarray“個別の営業日(祝日や定休日でも営業する日)”
- check_business_dayon 3 other servers
“日付(または 62 日までの期間)が営業日か休みか(理由と祝日名)。1 日だけなら次の営業日・前の営業日も返す。休みの規則は既定で土日祝、定休の曜日・お盆・年末年始・個別の休業日と営業日を指定できる。”
Publisher declares: read-only yes · destructive no · open-world no
9 inputs
datestring“YYYY-MM-DD(1926-01-01〜2080-12-31)”startstring“YYYY-MM-DD(1926-01-01〜2080-12-31)”endstring“YYYY-MM-DD(1926-01-01〜2080-12-31)”closed_weekdaysarray“定休の曜日(既定は ["土", "日"]。空の配列なら曜日では休まない)”close_holidaysboolean“祝日(振替休日・国民の休日を含む)を休む(既定 true)”obonboolean“お盆 8/13〜16 を休む(既定 false)”nenmatsuboolean“年末年始 12/29〜1/3 を休む(既定 false)”closed_datesarray“個別の休業日”open_datesarray“個別の営業日(祝日や定休日でも営業する日)”
- find_dates
“期間(366日まで)の中から、条件に合う日を探す。条件は六曜・吉日(一粒万倍日・天赦日・不成就日 など)・曜日・祝日・土日祝・二十四節気/雑節・新月/満月など・日干支(十干・十二支)。all(すべて)・any(どれか)・none(除く)で組み合わせ、offset_days で「翌日が満月」「前日が祝日」のようなずれも指定できる。例: 2027年の大安の土日で不成就日でない日。”
Publisher declares: read-only yes · destructive no · open-world no
5 inputs, 2 required
startstringrequired“YYYY-MM-DD(1926-01-01〜2080-12-31)”endstringrequired“YYYY-MM-DD(1926-01-01〜2080-12-31)”allarray“条件の配列(all・any・none を合わせて 12 個まで)”anyarray“条件の配列(all・any・none を合わせて 12 個まで)”nonearray“条件の配列(all・any・none を合わせて 12 個まで)”
- answeron 17 other servers
“日本語の質問 1 つ(例: 2027年4月の一粒万倍日はいつ?/2026年10月1日の六曜は?/2027年の夏至の時刻は?/1990年5月23日から20営業日後は?)に、答え・根拠の道具と引数・出典を 1 回で返す。規則で読むので、読めない質問には推測せず「読めませんでした」と聞き方の例を返す。”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
questionstringrequired“暦についての質問(日本語・300 文字まで)”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-26.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 91% of 64
- Tools with a description
- 100% of 16
- Typical description length
- 111 characters
The tool set
Counted from the listing
- Tools
- 16
- Size of the list
- about 3,662 tokens for an agent to load (characters ÷ 4)
- Naming
- 15 of 16 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 16 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-26 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://bestcalendar.jp/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"koyomi": {
"url": "https://bestcalendar.jp/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"koyomi": {
"type": "http",
"url": "https://bestcalendar.jp/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"koyomi","type":"http","url":"https://bestcalendar.jp/mcp"}'Claude Code
claude mcp add --transport http koyomi https://bestcalendar.jp/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"koyomi": {
"type": "streamableHttp",
"url": "https://bestcalendar.jp/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"koyomi": {
"httpUrl": "https://bestcalendar.jp/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.koyomi] url = "https://bestcalendar.jp/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"koyomi": {
"url": "https://bestcalendar.jp/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://bestcalendar.jp/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint bestcalendar.jp/mcp | Session opened | matches | our test · 2026-10-26 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-26 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-26. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about jp.bestcalendar/koyomi
Answered from the data aboveWho publishes jp.bestcalendar/koyomi?
The registry ties the namespace jp.bestcalendar to the domain bestcalendar.jp; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does jp.bestcalendar/koyomi need an API key or sign-in?
It opened a session without any credential on 2026-10-26. The registry entry declares no required credential; no declaration is not a guarantee.
Has jp.bestcalendar/koyomi been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-10-26, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,586 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 16 tools, 0 resources, 0 prompts.
- 6,877 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “jp.bestcalendar/koyomi: MCP server record.” Data checked 2026-10-26. https://protocolprobe.com/mcp/servers/jp.bestcalendar/koyomi
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/jp.bestcalendar/koyomi)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology