# @seline-analytics/mcp

Local MCP server for Seline Analytics API

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.6
- **Author:** lo-ud
- **License:** ISC
- **npm:** @seline-analytics/mcp
- **Endpoints:** streamable-http https://api.seline.com/mcp
- **Source:** https://github.com/getseline/seline-mcp
- **Endpoint health:** reachable (last checked 2026-09-16T11:27:10.073Z, 1 sample) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-16T11:26:59.780Z
- **Version scanned:** 1.0.6
- **CVEs:** none found by OSV at scan time

## Tools

17 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `seline_list_projects` — List projects accessible with the current API key (POST /api/v1/projects). With an account-wide key this returns all account projects. Use this to resolve a pro
- `seline_get_data` — Get unique visitors and page views over time with optional interval grouping, date filtering, and analytics filters (POST /api/v1/data).
- `seline_get_charges` — Get charges and revenue over time with optional interval grouping, date filtering, and analytics filters (POST /api/v1/charges).
- `seline_get_visit_metrics` — Get visit quality metrics including visits, page views, average session duration, and bounce rate for the selected period and filters (POST /api/v1/visit-metric
- `seline_get_custom_events` — Get aggregated custom events and charge events with pagination, optional search, type filtering, date range, and analytics filters (POST /api/v1/custom-events).
- `seline_get_top_visitors` — Get top visitor dimensions (country, browser, referrer, UTM, device, OS, etc.) with counts, pagination, and optional search (POST /api/v1/stats).
- `seline_get_pages` — Get top, entry, or exit pages. Top pages are ranked by pageviews. Entry pages are where sessions start. Exit pages are from multi-page sessions (bounces exclude
- `seline_get_property_values` — Get distinct values for a specific event property with search and pagination. Can be used to find project pathnames, event names, referrers, UTMs, countries, et
- `seline_get_field_keys` — Get all custom field keys and the top 100 used values for each, for a specific custom event. Useful for discovering what data is attached to an event (POST /api
- `seline_get_field_values` — Get possible values for a specific custom event field, with pagination and search. Use 'seline_get_event_data' first to discover available fields (POST /api/v1/
- `seline_get_events` — Get raw events with full filtering capabilities, event type filtering, pagination, search, and ordering. Useful for exporting transactions, computing average or
- `seline_get_funnel` — Analyze a conversion funnel through multiple steps (pages or events). Calculates how well specific pages and events convert users through the defined flow and r
- `seline_get_visitor` — Find a visitor by their shortId (Dashboard URL id) or internal visitorId (UUID). At least one of the two is required (POST /api/v1/visitor).
- `seline_get_visitor_events` — Get all events for a specific visitor. Use after finding a visitor to analyze their behavior over time (POST /api/v1/visitor-events).
- `seline_get_visitor_insight` — Generate AI-powered insights about a visitor's behavior based on their events. Returns a structured insight with main finding, details, bullet points, and recom
- `seline_get_most_active_visitors` — Get the most active visitors ranked by event count within a given time period. Shows who has generated the most events (page views, custom events, etc.) during 
- `seline_get_visitors` — Get a paginated list of visitors with comprehensive filtering options. Use this to find specific visitors, analyze visitor segments, or pull visitor profiles by

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@seline-analytics/mcp\"\n      ],\n      \"env\": {\n        \"YOUR_API_KEY\": \"<YOUR_YOUR_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `YOUR_API_KEY` — Your API Key (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — runs locally and hosted; holds an api key.
- Floor 27, ceiling 27 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40seline-analytics%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40seline-analytics%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40seline-analytics%2Fmcp
- HTML page: https://forgeregistry.com/registry/%40seline-analytics%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.