glippy-mcp

Name: glippy-mcp
Author: io.github.jbobbink

MCPcommunity

v0.8.0io.github.jbobbinkUnknownUpdated 1mo agonpm GitHub

GEO (Generative Engine Optimization) analysis: check any domain's AI-readiness for LLM search

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 →

1mo agoLast update

Needs 1 credential before it runs

GLIPPY_LICENSE_KEYAPI keyrequired
Your Glippy MCP license key (GLMCP-XXXX-XXXX-XXXX)

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

Authorio.github.jbobbink

LicenseUnknown

Version0.8.0

Sourcenpm+mcp-registry

npmglippy-mcp

GitHubjbobbink/glippy

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 surface9 tools · none privileged

Security scan✓ Cleanv0.4.3 · 3mo agoHow well does this scan work?

EvalsNone

IndexedJun 12, 2026

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

Tools

9 tools · none privileged

Statically extracted from the published packagev0.4.3 · 3mo 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.

Filter toolsPrivileged only

analyze_domainNo description published