PenguinRadar
REMOTE · PENGUINRADAR.COM
Instagram profiles, follower/following snapshots and changes, with budgeted public lookups.
Available components
Last scanned (19 minutes ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 2026.
Category News and Social
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 576 tokens (~96/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 41% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 21 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://penguinradar.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=penguinradar.com | CN=YE2,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 52a714bc98dc96561ebeef73a5251a4a5d5 |
| SANs: *.penguinradar.com, penguinradar.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of penguinradar.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| penguinradar.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://penguinradar.com/.well-known/oauth-protected-resource", error="invalid_token", scope="data:read", error_description="Connect PenguinRadar and grant the required data scopes"
Bearer resource_metadata="https://penguinradar.com/.well-known/oauth-protected-resource", error="invalid_token", scope="data:read", error_description="Connect PenguinRadar and grant the required data scopes"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'self' https://superboard.kaitox.ai |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://penguinradar.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://penguinradar.com/mcp |
| Authorisation server | https://penguinradar.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://penguinradar.com/mcp | Verified | 200 | |
| http (plaintext) | http://penguinradar.com/mcp | HTTPS enforced | 301 | https://penguinradar.com/mcp |
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 →
get_account ~48
Read stored profile information and follower/following counts. Counts may have a different observation time than lists. No online collection.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | Instagram username, optionally prefixed with @. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
get_account_changes ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Instagram username, optionally prefixed with @. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
list_followers ~80
Read a page of the most recent accessible follower snapshot, or permitted public query cache. State its asOf and partial coverage. Never collects automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | meta.nextCursor from the previous page of this same tool and account. |
| limit | integer | – | – |
| username | string | yes | Instagram username, optionally prefixed with @. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
list_following ~80
Read a page of the most recent accessible following snapshot, or permitted public query cache. State its asOf and partial coverage. Never collects automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | meta.nextCursor from the previous page of this same tool and account. |
| limit | integer | – | – |
| username | string | yes | Instagram username, optionally prefixed with @. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
list_tracking ~61
List your tracked accounts with profile counts and snapshot times. Reads stored data without collection charges.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | meta.nextCursor from the previous page of this same tool and account. |
| includeArchived | boolean | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
query_public_account ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| idempotencyKey | string | yes | – |
| maxCredits | integer | yes | – |
| type | string | yes | – |
| username | string | yes | Instagram username, optionally prefixed with @. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
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.
remote · penguinradar.com
claude mcp add --transport http penguinradar-penguinradar 'https://penguinradar.com/mcp'
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.