# TGGET Niche Research (remote · tgget.io)

Validate app and SaaS ideas: search demand, competitors, app store data and a verdict.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `tgget.io`: 79/100 (this document), [markdown](https://verifymcp.io/servers/io-tgget-niche-research/tgget.md), [page](https://verifymcp.io/servers/io-tgget-niche-research/tgget)

## Channel facts

- Endpoint: `https://tgget.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 86/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2253 tokens (~187/item across 12 items; 10 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the TGGET Niche Research MCP server?

TGGET Niche Research is a hosted endpoint at https://tgget.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-tgget-niche-research 'https://tgget.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-tgget-niche-research": {
      "url": "https://tgget.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-tgget-niche-research": {
      "type": "http",
      "url": "https://tgget.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-tgget-niche-research]
url = "https://tgget.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-tgget-niche-research": {
      "type": "remote",
      "url": "https://tgget.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-tgget-niche-research --url 'https://tgget.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-tgget-niche-research:
    url: "https://tgget.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-tgget-niche-research": {
      "Transport": "http",
      "Url": "https://tgget.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-tgget-niche-research -t streamable-http -u 'https://tgget.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-tgget-niche-research": {
      "type": "http",
      "url": "https://tgget.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-03 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-01 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-30 (score 77, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-29 (score 77)

First indexed and scored.

## MCP tools (10)

### `start_research` (~210 tokens)

Start Research

Starts a niche research from a short search phrase or a plain-language description of an app or service idea. A phrase is scanned directly (demand, sub-topics, competitors, signals); a description is first turned into real search queries, the best one is then scanned automatically. Returns the research id to poll with get_research. Counts as one research of the plan allowance, whether the data comes from the sources or from the shared cache.

Input parameters:

- `deep` (boolean): Deeper scan with more sub-topics and competitor checks. Available on plans that include it (Pro) and to administrators; counted as two researches.
- `locale` (string): Language of the conclusions and the final report. Defaults to the interface language of the account. Texts meant for the site and the stores are always written in the language of the market.
- `text` (string, required): Search phrase (e.g. "expense tracker") or a description of the idea in your own words, up to 400 characters.

### `get_research` (~85 tokens)

Get Research

Returns the current state and findings of a research by id: status, headline numbers, ranked candidate phrases, competitor overview, child researches (sub-topics, competitor checks, signals) with their ids, and skipped stages. Call repeatedly until status is completed and pending is 0.

Input parameters:

- `id` (string, required): Research id returned by start_research or listed by list_research.

### `get_report` (~223 tokens)

Get Report

Returns the final niche report of a finished scan (or the report research itself) as Markdown: verdict, what product to build (customer pains with evidence and severity, positioning, MVP with the pain each feature relieves, platform, monetization, competitor matrix), napkin economics (price hypothesis, acquisition cost from the cost per click in paid search, revenue per customer, whether it adds up, assumptions), SEO plan for the site (clusters, pages with title/H1/description, content plan, FAQ), ASO for App Store and Google Play, name options with domain and App Store availability, landing page draft, distribution channels by type with a first step, effort and priority, validation steps and risks. Pass format "json" for structured data (keys: verdict, product, economics, seo, aso, names, landing, channels, validation, risks).

Input parameters:

- `format` (string): markdown (default) for reading, json for structured fields.
- `id` (string, required): Id of the scan research (its latest report is returned) or of the report itself.

### `list_research` (~165 tokens)

List Research

Lists the researches the account started itself, newest first: niche scans of a phrase and descriptions of an idea, without the checks they spawned. Use it to find the id of an earlier research before get_research, get_report, compare_research or follow_niche, or to see what is still running. Each item has `id`, `kind`, `phrase`, `status` (queued, running, completed, failed), `mode`, `created_at`, `url` of its page and `total_count`: monthly searches of the phrase, null for a description. `quota` tells how many researches the plan has left. Reads only; spends nothing.

Input parameters:

- `limit` (integer): How many researches to return, from 1 to 50. Default 10.

### `run_signal` (~516 tokens)

Run Signal

Adds one check to a finished research and returns the id of the new child research. Use it when the scan skipped a stage, when a person asks about one phrase in particular, or to rebuild the report after new checks. A niche scan already runs the usual checks by itself, so this tool is for what is missing. Checks added this way are free: they do not spend researches of the plan.

Checks of a demand research (`kind`):
\- `competitors`: who holds the search results for a phrase of the research; pass the phrase in `phrase`.
\- `dynamics`: two years of demand history.
\- `appstore`: App Store apps for the phrase with ratings and freshness.
\- `wiki`, `radar`, `youtube`: public interest and community signals.
\- `paid`: paid search for the phrase and its strongest candidates: volume, advertiser competition, cost per click.
\- `insight`: a summary of the findings written by the language model.
\- `report`: the final niche report, written anew from the current data; needs a finished niche scan.

Checks of a child research:
\- `fingerprint`: product sites found by a competitors check, with pricing and app links; the parent is that competitors check.
\- `reviews`: recent App Store reviews of the leaders; the parent is an App Store research.
\- `insight` also accepts a competitors check as the parent.

The parent must be completed and belong to the account. The check runs in the background: poll get_research with the returned `id` every 20-30 seconds until `status` is `completed`. `insight` and `report` are rebuilt at most once an hour.

Input parameters:

- `id` (string, required): Id of the completed research the check is added to, as returned by start_research, get_research or list_research.
- `kind` (string, required): Which check to add. competitors, dynamics, appstore, wiki, radar, youtube, paid and report need a demand research as the parent; fingerprint a competitors check; reviews an App Store research; insigh…
- `locale` (string): Only for insight and report: language of the text. Defaults to the language the research was started with, then to the language of the account.
- `phrase` (string): Only for competitors: the phrase whose search results are checked, usually one of the candidate phrases of the parent. Defaults to the phrase of the parent. Ignored by the other checks.

### `compare_research` (~249 tokens)

Compare Research

Puts two to five finished niche scans side by side to help choose between ideas. `items` are the niches with their numbers, the report's positioning and napkin economics, and `wins`: in how many rows the niche holds the better value. `rows` are the ranked measures (verdict, demand, trend, cost per click, weak search results, competitor sites, App Store apps, fresh community signals) with the value of every niche and `best`, the indexes of the items that hold the better value; `better` says which way is better (max or min), null when the row is shown but not ranked. Demand and cost per click are not ranked across different markets (`mixed_markets`). The marks are computed from numbers, not written by a language model. Every scan needs a finished report. `share_url` is a read-only link to this comparison that works without signing in: give it to the person only when they want to share the comparison, it shows the numbers and the conclusions of their researches to whoever holds it.

Input parameters:

- `ids` (array, required): Two to five ids of finished niche scans (or of their reports), as listed by list_research.

### `list_projects` (~129 tokens)

List Projects

Lists the niches the account follows. A followed niche (a project) is scanned anew once a month and compared with its previous check. For each project: status, whether the plan serves it, the date of the next check, the latest numbers (verdict, demand, cost per click, competitor sites, App Store, community signals) and what changed at the latest monthly check, as structured `changes` and as `digest` lines of text. Also returns how many niches the plan follows.

Input parameters:

- `limit` (integer): How many projects to return, 1-50 (default 20).

### `get_project` (~100 tokens)

Get Project

Returns a followed niche with the history of its checks, newest first: the first measurement (`baseline`) and the monthly checks, each with its numbers, what changed since the previous check and the id of the research it came from. Pass that `research_id` to get_report to read the fresh report of a check. Changes are computed from numbers and lists, not written by a language model.

Input parameters:

- `id` (string, required): Project id listed by list_projects.

### `follow_niche` (~106 tokens)

Follow Niche

Starts following the niche of a finished scan that has a report: the scan becomes the first measurement and the niche is scanned anew every month, with a digest of what changed sent to the account. Monthly checks do not spend researches; the plan limits how many niches are followed (FREE 1, Starter 2, Pro 10). Following a niche that is already followed returns its project.

Input parameters:

- `research_id` (string, required): Id of a finished niche scan, or of its report.

### `update_project` (~100 tokens)

Update Project

Pauses a followed niche (`paused`: no monthly checks, its place in the plan is freed), follows it again (`active`, needs a free place in the plan) or stops following it (`deleted`: the project with its checks and digests is removed for good, the researches stay in the history). Ask the person before deleting.

Input parameters:

- `id` (string, required): Project id listed by list_projects.
- `status` (string, required): active, paused or deleted.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-tgget-niche-research/tgget#diagnostics

## Score history

- 2026-10-04: 79
- 2026-10-03: 79
- 2026-10-02: 78
- 2026-10-01: 78
- 2026-09-30: 77
- 2026-09-29: 77

## Common questions

### What is the TGGET Niche Research MCP server?

TGGET Niche Research is an MCP server listed in the public MCP registry as io.tgget/niche-research. Validate app and SaaS ideas: search demand, competitors, app store data and a verdict. This page covers its hosted endpoint (https://tgget.io/mcp).

### Is the TGGET Niche Research MCP server safe to use?

TGGET Niche Research scores 79 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.

### What tools does the TGGET Niche Research MCP server expose?

TGGET Niche Research exposes 10 tools: start_research, get_research, get_report, list_research, run_signal, and 5 more. Their descriptions and schemas cost roughly 1,883 tokens of context every time the server is loaded.

### Does the TGGET Niche Research MCP server require authentication?

Yes. TGGET Niche Research asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the TGGET Niche Research MCP server still maintained?

TGGET Niche Research is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://tgget.io/mcp
- Authorisation metadata: https://tgget.io/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/tgget/tgget-mcp
- Website: https://tgget.io/docs/api
- Changelog RSS feed: https://verifymcp.io/servers/io-tgget-niche-research/tgget.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-tgget-niche-research/tgget.json
- HTML version of this page: https://verifymcp.io/servers/io-tgget-niche-research/tgget