Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.pzep1/mcp-meet

NPM · MCP-MEET

One-click Google Meet scheduling and Apple Calendar mirroring with smart availability detection

Available components

npm · mcp-meet 0
0 this week 0 Trust /100

Last scanned (3 months ago)

Scores higher than 0% of npm servers

Category Productivity and Notes

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • No malware found by supply-chain analysis.Pass
  • Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency0
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Tool Safety–

Not scored yet: our latest scan of this package recorded no findings here. That is usually because the category is newer than the scan, or because we have not captured the MCP schema this package serves yet. It fills in the next time we score it.

Capabilities0
  • Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

What we tested

Checks we ran (4)

  • Malware scan
  • Source repository
  • Provenance
  • License

Checks we could not complete (10)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Known CVEs in Supply Chain SecurityKnown CVEs could not be checked: the version this server declares is not published in its registry.
  • Install scripts in Supply Chain SecurityInstall-script risk not yet assessed.
  • Dependency health in Supply Chain SecurityDependency health could not be checked: the version this server declares is not published in its registry.
  • Maintenance in Provenance & TransparencyMaintenance history not yet determined.
  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.
  • Tool Safety in Tool SafetyNot scored yet: our latest scan of this package recorded no findings here. That is usually because the category is newer than the scan, or because we have not captured the MCP schema this package serves yet. It fills in the next time we score it.
  • Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 7 Aug 26 −15

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 5 Aug 26 0
    • Provenance: unverified → fail ▼ security
    • License: unverified → fail ▼ functional
  • 2 Aug 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Jul 26 −18
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +18
    • Malware scan: unverified → pass ▲ security
  • 29 Jul 26 −18
    • Malware scan: pass → unverified ▼ security
  • 27 Jul 26 0
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
  • 26 Jul 26 18

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Aug 2026 · Analysed npm/mcp-meet@0.3.1

Provenance Version not published

The package exists but this version is not published, so there is no artifact to attest.

Result Version not published
Ecosystem npm

Background: How many MCP packages publish verified provenance →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the io.github.pzep1/mcp-meet server?

io.github.pzep1/mcp-meet runs locally as an npm package, launched with npx -y mcp-meet. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-meet

# add to Claude Code
claude mcp add pzep1-mcp-meet -- npx -y mcp-meet
Common questions

What is the io.github.pzep1/mcp-meet server?

io.github.pzep1/mcp-meet is listed in the public MCP registry as io.github.pzep1/mcp-meet. One-click Google Meet scheduling and Apple Calendar mirroring with smart availability detection. This page covers its npm package (mcp-meet).

Is the io.github.pzep1/mcp-meet server safe to use?

io.github.pzep1/mcp-meet scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the io.github.pzep1/mcp-meet server still maintained?

io.github.pzep1/mcp-meet has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.pzep1/mcp-meet server?

VerifyMCP ran 4 checks on io.github.pzep1/mcp-meet, covering Malware scan, Source repository, Provenance and License. 10 items could not be completed, a gap on our side rather than a finding about io.github.pzep1/mcp-meet: Known CVEs, Install scripts, Dependency health, Maintenance and 6 more. 4 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.