Atlas entry
jp- calendar. plugrail. dev
4 capabilities over MCP 2026-07-28. First atlas observation.
Atlas history
1 observation
- 4 capabilities · MCP 2026-07-28 · MCP endpoint validFirst observation
Fingerprint and versions
- Fingerprint
7e67742f803232ad8a58208a6a8443188920e0472559b2fd1e7ac3e3aad831ed- Passport schema
- 0.5.0, passport-semantic-v4
- Consistency
- MCP_PROMPTS_ADVERTISEMENT_LIST: not applicable · MCP_RESOURCES_ADVERTISEMENT_LIST: not applicable · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable
Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.
Declared and observed
Tool declarations are unavailable for this entry.
A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.
About this entry
dev.plugrail/jp-calendarListedOfficial MCP Registry · first listed 28 Sep 2026 · last listed 3 Nov 2026
Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal
Identity and snapshot
- Target key
sha256:f93d74a0860e6a399b946e9ea0e4eb15641038fc9ff9cd421951e22e4cc1c631- Locator SHA-256
0d988a81f52a6576caf78c7db9829b91654adfe009b3251012e1b424daa0cea2- Snapshot generated
- 13 Nov 2026, 00:06 UTC
The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.

