@temporal-cortex/cortex-mcp

MCPcommunity
v0.9.1UnknownMITUpdated 6mo agonpmGitHub

MCP server with 12 deterministic calendar and temporal tools — calendar discovery, temporal context, datetime resolution, atomic booking, RRULE expansion, and availability merging

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
202Downloads/wk
12GitHub stars
2Forks
6mo agoLast update
Reads these credentials
  • GOOGLE_CLIENT_SECRETOAuth appoptional

    Google OAuth Client Secret (required if using Google Calendar)

  • GOOGLE_OAUTH_CREDENTIALSOAuth appoptional

    Path to Google OAuth JSON credentials file (alternative to CLIENT_ID + SECRET)

  • MICROSOFT_CLIENT_SECRETOAuth appoptional

    Azure AD client secret (required for Outlook Calendar)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnknown
LicenseMIT
Version0.9.1
Sourcenpm+mcp-registry
npm@temporal-cortex/cortex-mcp
GitHubtemporal-cortex/mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 0 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv0.9.1 · 5d agoHow well does this scan work?
EvalsNone
IndexedAug 27, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source5d ago

Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

MCP server with 12 deterministic calendar and temporal tools — calendar discovery, temporal context, datetime resolution, atomic booking, RRULE expansion, and availability merging

Keywords
mcpcalendargoogle-calendaraischedulingbookingrruleavailabilitytimezonedatetime
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-03 — observed resolution, not a publisher declaration.

0 packages resolved · 0 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

This package declares no runtime dependencies.

Topics

Related in notes & productivity