Instagram Fake Follower Checker
REMOTE · MCP.RAPIDAPI.COM
Audit Instagram profiles for fake followers and bot risk: engagement rate, 0-100 risk score, reason.
Available components
Last scanned (17 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 17 Nov 26 +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.
- 15 Nov 26 +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.
- 14 Nov 26 +8
- 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 security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fair → good functional
- 13 Nov 26 47
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.rapidapi.com
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.rapidapi.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 21 Sept 2026 | 6 Apr 2027 | RSA 2048 | SHA256-RSA | 36a0bf9284d275a6fe0abca55f4fe71 |
| SANs: mcp.rapidapi.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.rapidapi.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| rapidapi.com. | DS published | 2371 | 13 | Verified |
| mcp.rapidapi.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.rapidapi.com | Verified | 200 | |
| http (plaintext) | http://mcp.rapidapi.com | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
auditProfile ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Username (natgeo or @natgeo) or profile URL (alias url) |
No output schema declared.
No examples provided.
bulkProfiles ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | – |
No output schema declared.
No examples provided.
getJobResults ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _endpoint | string | – | Endpoint: GET /jobs/{jobId}/results |
| _method | string | – | HTTP method |
| jobId | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
getJobStatus ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _endpoint | string | – | Endpoint: GET /jobs/{jobId} |
| _method | string | – | HTTP method |
| jobId | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · mcp.rapidapi.com
claude mcp add --transport http coregentdevspace-instagram-fake-follower-checker 'https://mcp.rapidapi.com/'
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.