ToolRepute
← Back to MCP database
MCPv1.5.2Registry: active

Chronary

Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.

ai.chronary/mcp

Publication

Published

Publisher

Chronary

Publisher identity: Not verified

Primary source

Official MCP Registry record

https://github.com/Chronary/chronary-mcp

Static analysis · human review · publication

Security evidence

Scanner signals, coverage and review decisions describe different parts of this report.

How ToolRepute evaluates MCP integrations
Scan status
completed
Coverage
Sufficient source coverage
Static risk signals
0/100 · none
Finding count
1
Highest finding severity
low
Human review
Approved review
Review freshness
Stale review
Publication
Published

Scan coverage and reliability

The scan completed with enough source coverage for ToolRepute's current review workflow. This does not verify runtime behavior.

Reliability: Meets current requirements

Scanner version
V5
Scan run
203
Last scan date
2026-09-06
Files scanned
15
Bytes scanned
30,061
Manifest
Found
Source commit
Pinned
Truncation
No

Analyzed source

https://github.com/Chronary/chronary-mcp

Analyzed commit: 8ac0cffb0191234b7498d06a9fc7c558270e4b2f

This assessment covers the available repository source. It does not inspect the hosted remote service or its runtime behavior.

Human review and publication

This historical decision does not establish current approval for the current review workflow. It may concern an older run, changed evidence or an older scanner.

Review decision
Approved review
Review date
2026-09-08
Reviewed scan run
203
Reviewed commit
8ac0cffb0191234b7498d06a9fc7c558270e4b2f

Publication is a decision to display evidence under ToolRepute's current rules, not a security certification, endorsement or guarantee.

Internal reviewer identity, review notes and private metadata are not displayed.

Published findings

LowCommand-line executable declaredNPM_BIN_DECLAREDpackage.jsonFinding details and evidence

Command-line executable declared

Category: code execution

What was found

The package manifest exposes one or more command-line entry points.

Why it matters

Command-line entry points indicate code intended to execute on the user's system.

Evidence snippet

No public snippet is available. It was not recorded or is withheld to protect sensitive content.

Scanner interpretation

A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.

Recommended check

Inspect the declared command-line entry point and its startup behavior, requested permissions and inputs before running it.

Limitations and legitimate-use context

Declaring a command-line tool is common and does not by itself indicate unsafe behavior.

Reputation evidence

Insufficient evidence · low confidence · model v1

Evidence support score: 5/100. This is separate from risk, review and publication.

Assessment as of 2026-10-23. Live repository HEAD is not checked when this page loads.

Security evidence · 0/25LIMITED · low confidence

Reliable mapped v6 scope is not established; evidence age: aging.

Static support is capped at 18/25 before a risk deduction of ceil(riskScore/4); zero findings does not establish safety.

Last observed: 2026-09-06

  • scan record 203: Scanner v5; completed; manifest found; sufficient scope true; 15 files / 30061 bytes; 1 findings; not truncated; scanner risk score 0.Commit 8ac0cffb0191234b7498d06a9fc7c558270e4b2fSource evidence

Static analysis covers a bounded source scope, not runtime, dependencies in full, or hosted behavior.

Source transparency · 5/25STALE · low confidence

Completed matching public GitHub acquisition: not established (+0).

Unique primary mapping: observed (+5).

Completed matching pinned commit: not established (+0).

Completed matching source mapping: not established (+0).

Matching manifest and sufficient untruncated scope: not established (+0).

Last observed: 2026-10-04

  • source record 210: Primary mapping is incomplete or changed. Live repository HEAD is not checked by page requests.Source evidence
  • scan record 203: Scanner v5; completed; manifest found; sufficient scope true; 15 files / 30061 bytes; not truncated.Commit 8ac0cffb0191234b7498d06a9fc7c558270e4b2fSource evidence

A source mapping does not prove ownership. Repository availability and live HEAD are not rechecked here.

Review freshness · 0/25STALE · low confidence

Current artifact-bound approval earns 25; matching approval with unchecked live HEAD earns 8; stale, missing or rejected evidence earns 0.

Last observed: 2026-09-08

  • review record 10: Decision: approved; reviewed run 203; NEXT-11 freshness: stale.

Page requests make no upstream probe. An old approval is not approval of changed evidence.

Registry consistency · 0/10UNKNOWN · low confidence

Unique primary, normalized active/latest official registry observation earns 10 within 30 days, 5 within 90, otherwise 0.

Last observed: 2026-10-04

  • registry record 210: Normalized official record: false; active: true; latest: true; observation age: recent.

Registry consistency is a source-record observation, not identity verification or a security endorsement.

Publisher identity confidence · 0/15UNKNOWN · low confidence

No verified legal, domain or repository-ownership binding is available; free text and the registry verification flag earn no credit.

Last observed: Not available

    Publisher name and registry namespace cannot establish legal identity or ownership.

    Recorded assessment history (1)

    History starts with explicit captures in model v1. Past source and review state cannot be fully reconstructed. Page reads do not save snapshots; changes in the live assessment appear in history only after an explicit capture.

    1. 2026-10-11 · model v1 · 5/100 · low confidence · scan 2038ac0cffb0191234b7498d06a9fc7c558270e4b2f
      Recorded signal breakdown
      • Security evidence: 0/25 · LIMITED
      • Source transparency: 5/25 · STALE
      • Review freshness: 0/25 · STALE
      • Registry consistency: 0/10 · UNKNOWN
      • Publisher identity confidence: 0/15 · UNKNOWN

    Reputation reflects ToolRepute-observed evidence only; it is not a guarantee of security.

    Signals may be incomplete or stale. Runtime and hosted behavior may differ from scanned source.

    Publisher identity has no verified binding. Repository ownership and legal identity are not established.

    This score measures support in the available evidence, not the probability that a tool is safe.

    Registry data

    Version

    1.5.2

    Packages

    1

    Remote endpoints

    1

    Enrichment

    complete

    Last fetched

    2026-10-04

    Registry inclusion identifies the source record. It is not a ToolRepute security endorsement.

    Normalized sources

    Structured from the Official MCP Registry record.

    Enriched 2026-10-04

    github

    https://github.com/Chronary/chronary-mcp

    Packages

    npm· stdio· v1.5.2

    @chronary/mcp

    Remote endpoints

    streamable-http · api.chronary.ai

    https://api.chronary.ai/mcp

    More reviewed MCP servers

    Continue exploring integrations with published ToolRepute reviews.

    Clelp

    Search and rate AI tools, MCP servers, and agent skills, safety-checked and rated by AI agents.

    Cofound

    MCP-native co-founder directory your AI agent searches, screening inbound pitches for you.

    DABLOCK AI Visibility Index

    Measured share of answer for 24 crypto and Web3 brands. An open dataset, not an audit of your site.