io.grovs/mcp

MCPcommunitylive
v1.0.1io.grovsUnknownUpdated 5mo agoGitHub

Manage deep links, attribution, analytics, and campaigns on Grovs — open-source Branch alternative.

MCP server for managing deep links, analytics, and app configuration on Grovs. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible client. Documentation · Grovs is an open-source, privacy-first growth platform for mobile apps — a self-hostable alternative to Branch.io and AppsFlyer. It provides: Deep Linking — one link that routes users to the right content across iOS,…

Endpoint healthlive
checked 6 days ago · 576ms · auth required
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). 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 →
2GitHub stars
5mo agoLast update
Package
Authorio.grovs
LicenseUnknown
Version1.0.1
Sourcemcp-registry
GitHubgrovs-io/mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface16 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

16 tools · none privileged
Statically extracted from the published packagevHEAD · 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.

get_statusNo description published

This tool published no description. Forge does not invent one.

get_usageNo description published

This tool published no description. Forge does not invent one.

create_projectNo description published

This tool published no description. Forge does not invent one.

create_linkNo description published

This tool published no description. Forge does not invent one.

get_linkNo description published

This tool published no description. Forge does not invent one.

update_linkNo description published

This tool published no description. Forge does not invent one.

archive_linkNo description published

This tool published no description. Forge does not invent one.

search_linksNo description published

This tool published no description. Forge does not invent one.

get_analytics_overviewNo description published

This tool published no description. Forge does not invent one.

get_link_analyticsNo description published

This tool published no description. Forge does not invent one.

get_top_linksNo description published

This tool published no description. Forge does not invent one.

configure_redirectsNo description published

This tool published no description. Forge does not invent one.

configure_sdkNo description published

This tool published no description. Forge does not invent one.

create_campaignNo description published

This tool published no description. Forge does not invent one.

list_campaignsNo description published

This tool published no description. Forge does not invent one.

archive_campaignNo description published

This tool published no description. Forge does not invent one.

0 of 16 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

MCP server for managing deep links, analytics, and app configuration on Grovs. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible client. Documentation · Grovs is an open-source, privacy-first growth platform for mobile apps — a self-hostable alternative to Branch.io and AppsFlyer. It provides: Deep Linking — one link that routes users to the right content across iOS, Android, and web. Deferred deep links survive the install flow so users land on the right screen on first…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

16 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.