# Instagram Fake Follower Checker (remote · mcp.rapidapi.com)

Audit Instagram profiles for fake followers and bot risk: engagement rate, 0-100 risk score, reason.

- Trust score: 59/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.rapidapi.com`: 59/100 (this document), [markdown](https://verifymcp.io/servers/coregentdevspace-instagram-fake-follower-checker/mcp.md), [page](https://verifymcp.io/servers/coregentdevspace-instagram-fake-follower-checker/mcp)

## Channel facts

- Endpoint: `https://mcp.rapidapi.com`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-21.

- **Endpoint Security**: 49/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 551 tokens (~137/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 62% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the Instagram Fake Follower Checker MCP server?

Instagram Fake Follower Checker is a hosted endpoint at https://mcp.rapidapi.com/, 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 coregentdevspace-instagram-fake-follower-checker 'https://mcp.rapidapi.com/'
```

### Cursor

```json
{
  "mcpServers": {
    "coregentdevspace-instagram-fake-follower-checker": {
      "url": "https://mcp.rapidapi.com/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "coregentdevspace-instagram-fake-follower-checker": {
      "type": "http",
      "url": "https://mcp.rapidapi.com/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.coregentdevspace-instagram-fake-follower-checker]
url = "https://mcp.rapidapi.com/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "coregentdevspace-instagram-fake-follower-checker": {
      "type": "remote",
      "url": "https://mcp.rapidapi.com/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add coregentdevspace-instagram-fake-follower-checker --url 'https://mcp.rapidapi.com/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  coregentdevspace-instagram-fake-follower-checker:
    url: "https://mcp.rapidapi.com/"
```

### Netclaw

```json
{
  "McpServers": {
    "coregentdevspace-instagram-fake-follower-checker": {
      "Transport": "http",
      "Url": "https://mcp.rapidapi.com/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add coregentdevspace-instagram-fake-follower-checker -t streamable-http -u 'https://mcp.rapidapi.com/'
```

### Other

```json
{
  "mcpServers": {
    "coregentdevspace-instagram-fake-follower-checker": {
      "type": "http",
      "url": "https://mcp.rapidapi.com/"
    }
  }
}
```

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-11-21 (score 59, +1)

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

### 2026-11-19 (score 58, +1)

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

### 2026-11-17 (score 57, +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-11-15 (score 56, +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-11-14 (score 55, +8)

- [security] Tool “auditProfile” rewrote its description, which is the text the model reads
- [security] Tool “bulkProfiles” rewrote its description, which is the text the model reads
- [security] Tool “getJobResults” rewrote its description, which is the text the model reads
- [security] Tool “getJobStatus” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: fair → good

### 2026-11-13 (score 47)

First indexed and scored.

## MCP tools (4)

### `getJobStatus` (~77 tokens)

Status of a bulk job started by one of the bulk tools: running, succeeded or failed. Free. Poll every few seconds, then fetch rows with getJobResults.

Input parameters:

- `_endpoint` (string): Endpoint: GET /jobs/{jobId}
- `_method` (string): HTTP method
- `jobId` (string, required)

### `getJobResults` (~103 tokens)

Page through the audits of a finished bulk job (offset / limit). While the job runs it returns no items and a retryAfterSeconds hint. Each analyzed profile bills once, on first delivery; re-reading is free.

Input parameters:

- `_endpoint` (string): Endpoint: GET /jobs/{jobId}/results
- `_method` (string): HTTP method
- `jobId` (string, required)
- `limit` (integer)
- `offset` (integer)

### `bulkProfiles` (~188 tokens)

Start an async job that audits many Instagram profiles (a usernames array, up to 1,000). Returns a jobId: poll getJobStatus, then page through getJobResults. Bills 1 result per fully analyzed profile; failed, private and partial profiles are free.

Input parameters:

- `_endpoint` (string): Endpoint: POST /bulk/profiles
- `_method` (string): HTTP method
- `analysisDepth` (string)
- `callbackSecret` (string): HMAC-SHA256 signing secret for the webhook
- `callbackUrl` (string): Webhook called when the job finishes
- `limit` (integer): Job size; capped by plan (20/500/1000/2000) and at 1000 per job
- `minPostsForFullConfidence` (integer)
- `recentPostsLimit` (integer)
- `usernames` (array, required)

### `auditProfile` (~183 tokens)

Audit one public Instagram profile for fake followers and bot risk. Pass a username (natgeo, @natgeo) or profile URL. Returns follower and following counts, engagement rate from recent posts, a 0-100 bot-risk score, a risk bucket, confidence and a plain-English reason. depth: quick (no posts sample, fastest), standard, or deep (about 12 posts). Takes about 10-20 s. Bills 1 result only for a full audit; private, missing or partial profiles are free.

Input parameters:

- `_endpoint` (string): Endpoint: GET /profile
- `_method` (string): HTTP method
- `depth` (string): quick skips the recent-posts sample (lower confidence); deep samples about 12 posts
- `username` (string, required): Username (natgeo or @natgeo) or profile URL (alias url)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/coregentdevspace-instagram-fake-follower-checker/mcp#diagnostics

## Score history

- 2026-11-21: 59
- 2026-11-20: 58
- 2026-11-19: 58
- 2026-11-18: 57
- 2026-11-17: 57
- 2026-11-16: 56
- 2026-11-15: 56
- 2026-11-14: 55
- 2026-11-13: 47

## Common questions

### What is the Instagram Fake Follower Checker MCP server?

Instagram Fake Follower Checker is an MCP server listed in the public MCP registry as io.github.coregentdevspace/instagram-fake-follower-checker. Audit Instagram profiles for fake followers and bot risk: engagement rate, 0-100 risk score, reason. This page covers its hosted endpoint (https://mcp.rapidapi.com).

### Is the Instagram Fake Follower Checker MCP server safe to use?

Instagram Fake Follower Checker scores 59 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 Instagram Fake Follower Checker MCP server expose?

Instagram Fake Follower Checker exposes 4 tools: getJobStatus, getJobResults, bulkProfiles, auditProfile. Their descriptions and schemas cost roughly 551 tokens of context every time the server is loaded.

### Does the Instagram Fake Follower Checker MCP server require authentication?

No. We connected to Instagram Fake Follower Checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Instagram Fake Follower Checker MCP server still maintained?

Instagram Fake Follower Checker is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Instagram Fake Follower Checker MCP server?

VerifyMCP ran 12 checks on Instagram Fake Follower Checker, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Instagram Fake Follower Checker: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.rapidapi.com/
- Authorisation metadata: https://mcp.rapidapi.com/.well-known/oauth-protected-resource
- Website: https://rapidapi.com/coregentdevspace/api/instagram-fake-follower-checker-api
- Changelog RSS feed: https://verifymcp.io/servers/coregentdevspace-instagram-fake-follower-checker/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/coregentdevspace-instagram-fake-follower-checker/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/coregentdevspace-instagram-fake-follower-checker/mcp.json
- HTML version of this page: https://verifymcp.io/servers/coregentdevspace-instagram-fake-follower-checker/mcp
