# PenguinRadar (remote · penguinradar.com)

Instagram profiles, follower/following snapshots and changes, with budgeted public lookups.

- Trust score: 84/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `penguinradar.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/penguinradar-penguinradar/penguinradar.md), [page](https://verifymcp.io/servers/penguinradar-penguinradar/penguinradar)

## Channel facts

- Endpoint: `https://penguinradar.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.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-05.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 576 tokens (~96/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 41% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 PenguinRadar MCP server?

PenguinRadar is a hosted endpoint at https://penguinradar.com/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 penguinradar-penguinradar 'https://penguinradar.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "penguinradar-penguinradar": {
      "url": "https://penguinradar.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "penguinradar-penguinradar": {
      "type": "http",
      "url": "https://penguinradar.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.penguinradar-penguinradar]
url = "https://penguinradar.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "penguinradar-penguinradar": {
      "type": "remote",
      "url": "https://penguinradar.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add penguinradar-penguinradar --url 'https://penguinradar.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  penguinradar-penguinradar:
    url: "https://penguinradar.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "penguinradar-penguinradar": {
      "Transport": "http",
      "Url": "https://penguinradar.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add penguinradar-penguinradar -t streamable-http -u 'https://penguinradar.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "penguinradar-penguinradar": {
      "type": "http",
      "url": "https://penguinradar.com/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-11-05 (score 84, +1)

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

### 2026-11-03 (score 83, +1)

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

### 2026-11-01 (score 82, +1)

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

### 2026-10-30 (score 81, +1)

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

### 2026-10-28 (score 80, +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-10-25 (score 79, +1)

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

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

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

### 2026-10-21 (score 77, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (6)

### `list_tracking` (~61 tokens)

List your tracked accounts with profile counts and snapshot times. Reads stored data without collection charges.

Input parameters:

- `cursor` (string): meta.nextCursor from the previous page of this same tool and account.
- `includeArchived` (boolean)
- `limit` (integer)

Output parameters:

- `data` (object)
- `meta` (object)

### `get_account` (~48 tokens)

Read stored profile information and follower/following counts. Counts may have a different observation time than lists. No online collection.

Input parameters:

- `username` (string, required): Instagram username, optionally prefixed with @.

Output parameters:

- `data` (object)
- `meta` (object)

### `list_followers` (~80 tokens)

Read a page of the most recent accessible follower snapshot, or permitted public query cache. State its asOf and partial coverage. Never collects automatically.

Input parameters:

- `cursor` (string): meta.nextCursor from the previous page of this same tool and account.
- `limit` (integer)
- `username` (string, required): Instagram username, optionally prefixed with @.

Output parameters:

- `data` (object)
- `meta` (object)

### `list_following` (~80 tokens)

Read a page of the most recent accessible following snapshot, or permitted public query cache. State its asOf and partial coverage. Never collects automatically.

Input parameters:

- `cursor` (string): meta.nextCursor from the previous page of this same tool and account.
- `limit` (integer)
- `username` (string, required): Instagram username, optionally prefixed with @.

Output parameters:

- `data` (object)
- `meta` (object)

### `get_account_changes` (~126 tokens)

Read detected changes in your accessible tracking history, default last seven calendar days UTC. detectedAt is detection time, not exact Instagram action time. For the next page send username and cursor; the cursor keeps the list, dates and timezone.

Input parameters:

- `cursor` (string): meta.nextCursor from the previous page of this same tool and account.
- `from` (string)
- `limit` (integer)
- `list` (string)
- `timezone` (string)
- `to` (string)
- `username` (string, required): Instagram username, optionally prefixed with @.

Output parameters:

- `data` (object)
- `meta` (object)

### `query_public_account` (~149 tokens)

Explicit online query of a public profile or ONE page of followers/following (one source page, usually 25 people). May consume credits: a first list page needs maxCredits of at least 2 (profile + page), a next page 1. Require user authorization for this target, type and maxCredits. Generate and keep idempotencyKey before the first attempt; reuse it with identical arguments when restoring. Never automatically fetch all pages or increase budget.

Input parameters:

- `cursor` (string)
- `idempotencyKey` (string, required)
- `maxCredits` (integer, required)
- `type` (string, required)
- `username` (string, required): Instagram username, optionally prefixed with @.

Output parameters:

- `data` (object)
- `meta` (object)

## Diagnostics

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

## Score history

- 2026-11-05: 84
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 79
- 2026-10-24: 78
- 2026-10-23: 78
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 76

## Common questions

### What is the PenguinRadar MCP server?

PenguinRadar is an MCP server listed in the public MCP registry as io.github.penguinradar/penguinradar. Instagram profiles, follower/following snapshots and changes, with budgeted public lookups. This page covers its hosted endpoint (https://penguinradar.com/mcp).

### Is the PenguinRadar MCP server safe to use?

PenguinRadar scores 84 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 PenguinRadar MCP server expose?

PenguinRadar exposes 6 tools: list_tracking, get_account, list_followers, list_following, get_account_changes, query_public_account. Their descriptions and schemas cost roughly 544 tokens of context every time the server is loaded.

### Does the PenguinRadar MCP server require authentication?

Yes. PenguinRadar 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 PenguinRadar MCP server still maintained?

PenguinRadar is still listed as active in the MCP registry. We last reached this channel on 5 November 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://penguinradar.com/mcp
- Website: https://penguinradar.com/docs/plugins
- Changelog RSS feed: https://verifymcp.io/servers/penguinradar-penguinradar/penguinradar.xml
- Changelog JSON feed: https://verifymcp.io/servers/penguinradar-penguinradar/penguinradar.json
- HTML version of this page: https://verifymcp.io/servers/penguinradar-penguinradar/penguinradar