@infoinlet/mcp-calendar

Name: @infoinlet/mcp-calendar
Author: Unknown

MCPcommunity

v0.1.1UnknownMITUpdated 3mo agonpm GitHub

Google Calendar for AI agents — list/create/delete events and free-busy, using an OAuth access token. MCP server.

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 →

44Downloads/wk

3mo agoLast update

Package

AuthorUnknown

LicenseMIT

Version0.1.1

Sourcenpm+mcp-registry

npm@infoinlet/mcp-calendar

GitHubinfoinlet-marketplace/marketplace

SBOMCycloneDX 1.6 ↓

Trust Status

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✓ 60 resolved+ · none vulnerable

Tool surface4 tools · 1 privileged

Security scan✓ Cleanv0.1.1 · 3d agoHow well does this scan work?

EvalsNone

IndexedAug 26, 2026

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

Tools

4 tools · 1 privileged

Statically extracted from the published packagev0.1.1 · 3d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_eventsList upcoming events (optionally between timeMin/timeMax ISO times).

List upcoming events (optionally between timeMin/timeMax ISO times).

No input schema was published for this tool.

create_eventCreate an event. Use date (YYYY-MM-DD) for all-day, or ISO dateTime for timed.

Create an event. Use date (YYYY-MM-DD) for all-day, or ISO dateTime for timed.

No input schema was published for this tool.

delete_eventprivilegedDelete an event by id.

Delete an event by id.

No input schema was published for this tool.

free_busyFree/busy intervals between two ISO times.

Free/busy intervals between two ISO times.

No input schema was published for this tool.

4 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Google Calendar for AI agents — list/create/delete events and free-busy, using an OAuth access token. MCP server.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Dependency tree

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

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

axios1.20.04 dependencies
- form-data4.0.6+5 not drawn
- proxy-from-env2.1.0
- follow-redirects1.16.0
- https-proxy-agent5.0.1+2 not drawn
dotenv17.4.2
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.0+4 not drawn
- zod4.5.4
- cors2.8.6+2 not drawn
- hono4.13.5
- jose6.2.10
- express5.2.1incomplete+26 not drawn1 dependency
  - content-type1.0.5
- raw-body3.0.2incomplete
- ajv-formats3.0.1incomplete
- cross-spawn7.0.6incomplete
- eventsource3.0.7incomplete
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1
- express-rate-limit8.7.0incomplete
- zod-to-json-schema3.25.2

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

74 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 74

merge-descriptors ^2.0.0 — required by express@5.2.1package cap reached
content-disposition ^1.0.0 — required by express@5.2.1package cap reached
bytes ~3.1.2 — required by raw-body@3.0.2package cap reached
unpipe ~1.0.0 — required by raw-body@3.0.2package cap reached
iconv-lite ~0.7.0 — required by raw-body@3.0.2package cap reached
http-errors ~2.0.1 — required by raw-body@3.0.2package cap reached
ajv ^8.0.0 — required by ajv-formats@3.0.1package cap reached
which ^2.0.1 — required by cross-spawn@7.0.6package cap reached
path-key ^3.1.0 — required by cross-spawn@7.0.6package cap reached
shebang-command ^2.0.0 — required by cross-spawn@7.0.6package cap reached
eventsource-parser ^3.0.1 — required by eventsource@3.0.7package cap reached
debug ^4.4.3 — required by express-rate-limit@8.7.0package cap reached

+62 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

@infoinlet/mcp-calendar

Tools

Tools exposed

Dependency tree

Declared but not resolved

Topics

Related in notes & productivity