updated 2026-09-26 06:32 UTC

Temporal Cortex Calendar MCP

temporal-cortex/mcp

Calendar MCP server with atomic booking, conflict prevention, deterministic RRULE expansion, and TOON token compression for AI agents

MCP Servers Dockerfile Listed MIT

Is Temporal Cortex Calendar MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard No result
Provenance None
Signed commits 2%
Last push 26d ago
Compare Temporal Cortex Calendar MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Temporal Cortex Calendar MCP scores 27.9/100 (Grade D), ranked #1301 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 2% of recent commits are signed; last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

How Temporal Cortex Calendar MCP compares in MCP Servers

  1. #769 Crawleo MCP 28.8 +0.9
  2. #770 Fortnox MCP 28.7 +0.8
  3. #771 Temporal Cortex Calendar MCP 27.9 this agent
  4. #772 MCP Toolbox for Databases 27.5 −0.4
  5. #773 Hatago MCP Hub 27.4 −0.5

Bars show each HVTrust score; the tick marks Temporal Cortex Calendar MCP’s 27.9.

Where the 27.9 comes from

HVTrust dimensions vs the MCP Servers average

27.9 / 100 · 67.0% confidence

Temporal Cortex Calendar MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.1 / 25
10.2 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.7 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
10.3 / 20
1.8 below avg 12.1
AdoptionLog-scaled stars · package downloads
5.4 / 20
1.8 below avg 7.2

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-24
Provider Added
Runtime surface grew — new detected provider dependencies: OpenAI, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 25 spots (#1320 → #1295)
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Temporal Cortex Calendar MCP View MCP Servers Report missing data
30.6
Activity sub-score · out of 100
#771
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 26 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
13
Forks
2
Last Push
2026-08-31
26 days ago
Commits (4 wk)
0
Downloads (7d)
101
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▲1
was #1302

Analysis

Activity Inputs

30.6 / 100
StarsRepository reach
6.9 / 30
FreshnessLast push recency
21.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
2%
of last 100 commits verified

Common questions about Temporal Cortex Calendar MCP

Public trust evidence for Temporal Cortex Calendar MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Temporal Cortex Calendar MCP publish package provenance?
No published build provenance is currently detected for Temporal Cortex Calendar MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Temporal Cortex Calendar MCP have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Temporal Cortex Calendar MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Temporal Cortex Calendar MCP actively maintained?
Maintained. Last push was 26 days ago.
What license does Temporal Cortex Calendar MCP use?
Temporal Cortex Calendar MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Temporal Cortex Calendar MCP's commits signed?
2% of the last 100 commits to Temporal Cortex Calendar MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Implemented
Temporal Cortex Calendar MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Temporal Cortex Calendar MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-24
Provider Added
Runtime surface grew — new detected provider dependencies: OpenAI, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Temporal Cortex Calendar MCP?

For maintainers

HVTrust scores Temporal Cortex Calendar MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 13Listed 2HVTrust 2Delisted 1MCP 1Surface 1
2026-09-24
Provider Added
Runtime surface grew — new detected provider dependencies: OpenAI, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 25 spots (#1320 → #1295)
2026-09-23
HVTrust Changed
HVTrust up 19.9pts (9.6 → 29.5)
2026-09-22
Newly Listed
First tracked at rank #1320
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-07
Rank Moved
Rank dropped 10 spots (#1268 → #1278)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1253 → #1268)
2026-09-05
Rank Moved
Rank dropped 19 spots (#1234 → #1253)
2026-09-04
Rank Moved
Rank dropped 16 spots (#1218 → #1234)
2026-09-03
Rank Moved
Rank rose 76 spots (#1294 → #1218)
2026-09-03
HVTrust Changed
HVTrust up 11.1pts (18.1 → 29.2)
2026-09-02
Rank Moved
Rank dropped 13 spots (#1281 → #1294)
2026-08-30
Rank Moved
Rank dropped 12 spots (#1259 → #1271)
2026-08-29
Rank Moved
Rank dropped 13 spots (#1246 → #1259)
2026-08-28
Rank Moved
Rank dropped 10 spots (#1236 → #1246)
2026-08-26
Rank Moved
Rank dropped 31 spots (#1196 → #1227)
2026-08-16
Rank Moved
Rank dropped 23 spots (#1165 → #1188)
2026-08-10
Rank Moved
Rank dropped 71 spots (#1091 → #1162)
2026-08-08
Newly Listed
First tracked at rank #1089
GitHub → npm: @temporal-cortex/cortex-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 27.9 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/temporal-cortex-calendar-mcp.svg)](https://hvtracker.net/agents/temporal-cortex-calendar-mcp)
HTML:
<a href="https://hvtracker.net/agents/temporal-cortex-calendar-mcp"><img src="https://hvtracker.net/badge/temporal-cortex-calendar-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON