# io.github.hackle-io/hackle-mcp

Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** io.github.hackle-io
- **License:** Unknown
- **Endpoints:** streamable-http https://mcp.hackle.io/mcp
- **Source:** https://github.com/hackle-io/hackle-mcp
- **Endpoint health:** reachable (last checked 2026-09-29T20:44:10.173Z, 5 samples) — 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 content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 57 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-09T13:20:35.125Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

19 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `experiment-list`
- `experiment-detail`
- `in-app-message-list`
- `in-app-message-detail`
- `push-message-list`
- `push-message-detail`
- `active-user-series`
- `retention-series`
- `stickiness-series`
- `data-report-list`
- `data-report-detail`
- `analytics-chart-list`
- `analytics-chart-detail`
- `remote-config-list`
- `remote-config-detail`
- `remote-config-create`
- `remote-config-update`
- `remote-config-update-user-identifier-criteria`
- `remote-config-update-description`

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"hackle-mcp\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.hackle.io/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- 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/io.github.hackle-io%2Fhackle-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.hackle-io%2Fhackle-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.hackle-io%2Fhackle-mcp
- HTML page: https://forgeregistry.com/registry/io.github.hackle-io%2Fhackle-mcp
- 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.