ai-smithery-mayla-debug-mcp-google-calendar2
ToolProof Connection Signal
Not Enough Evidence
Do not connect to a production agent until source, identity, tool definitions, and capability evidence are verified.
Evidence ConfidenceNot scored
Tools Inferred0
Control Signals0
Why this signal
- Source evidence fetched from 1 file(s).
- No MCP tools were confidently identified.
- No visible control signals were observed.
- 2 concern(s) identified from fetched evidence.
- The safe default is to avoid production connection until more evidence is available.
What this server exposes
No MCP tools confidently identified.
Source and observation
Source: https://github.com/mayla-debug/mcp-google-calendar2
Observed: 2026-06-10T16:45:06Z
Machine ID: mcp:ai-smithery-mayla-debug-mcp-google-calendar2
Capabilities inferred
- No capabilities inferred.
Controls observed
- No controls observed.
Recommended controls
- Use least privilege, logging, and staged rollout until controls are verified.
Open questions before connection
- Is the source repository public and attributable?
- Are tool definitions, install instructions, and security controls documented?
Findings and concerns
- No MCP tools confidently identified
- No explicit controls observed in fetched evidence
Claim or update this profile
Are you the owner of this MCP server? Submit official docs, intended use cases, support links, security contact, and recommended safe configuration.
Owner-provided information is shown separately from ToolProof evidence and does not change the connection signal unless reviewed.
Payment may buy review, monitoring, or sponsored visibility. It does not change the ToolProof connection signal.
Evidence fetched
- https://github.com/mayla-debug/mcp-google-calendar2