updated 2026-11-10 04:07 UTC

Temporal Cortex Calendar MCP

Repository

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 4.5 / 10
Provenance None
Signed commits 2%
Last push 71d ago
Advisories None known
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 46.6/100 (Grade D), ranked #1089 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.5/10; 2% of recent commits are signed; no published advisory affects its latest release (@temporal-cortex/cortex-mcp); last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

How Temporal Cortex Calendar MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Temporal Cortex Calendar MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/temporal-cortex/mcp, MIT, last pushed 2026-08-31. 2% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.5/10 (scanned Oct 27, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 10
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 6

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @temporal-cortex/cortex-mcp 0.9.1. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-26 OSSF Scorecard: 4.5/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Temporal Cortex Calendar MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Temporal Cortex Calendar MCP compares in MCP Servers

  1. #616 MCP Fns Check 47.1 +0.5
  2. #617 Vidlens MCP 46.7 +0.1
  3. #618 Temporal Cortex Calendar MCP 46.6 this agent
  4. #619 Markifact: AI Performance Marketing 46.6 ±0
  5. #620 CleanSlice 46.6 ±0

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

Where the 46.6 comes from

HVTrust dimensions vs the MCP Servers average

46.6 / 100 · 100.0% confidence

Temporal Cortex Calendar MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.7 / 25
5.1 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.3 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
7.3 / 20
4.9 below avg 12.2
AdoptionLog-scaled stars · package downloads
6.0 / 20
1.6 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-27
Rank Moved
Rank rose 15 spots (#1091 → #1076)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.5/10. Tighten the weakest checks to improve public safety evidence.
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.
Refresh maintenance signals The repo was last pushed 71 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
24.4
Activity sub-score · out of 100
#618
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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 71 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

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

Analysis

Activity Inputs

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

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?
Temporal Cortex Calendar MCP has an OpenSSF Scorecard score of 4.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Temporal Cortex Calendar MCP actively maintained?
Slowing down. Last push was 71 days ago — keep an eye on whether activity resumes.
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 16HVTrust 3Delisted 1Listed 1MCP 1Surface 1Scorecard 1
2026-10-27
Rank Moved
Rank rose 15 spots (#1091 → #1076)
2026-10-09
Rank Moved
Rank dropped 20 spots (#1005 → #1025)
2026-09-30
Rank Moved
Rank dropped 12 spots (#969 → #981)
2026-09-26
Scorecard Added
OSSF Scorecard: 4.5/10
2026-09-26
Rank Moved
Rank rose 338 spots (#1302 → #964)
2026-09-26
HVTrust Changed
HVTrust up 21.1pts (27.9 → 49.0)
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)
GitHub → npm: @temporal-cortex/cortex-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 46.6 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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON