Frogeye Security Scanner
REMOTE · MCP.FROGEYE.AI · 2 COMPONENTS
Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns.
Available components
Last scanned (3 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 500. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.87 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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://mcp.frogeye.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.frogeye.ai | CN=YR1,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | RSA 2048 | SHA256-RSA | 64b97a5d9aec1288bb6e041cc68c27d0647 |
| SANs: *.frogeye.ai, frogeye.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.frogeye.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| frogeye.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 500 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.frogeye.ai/mcp | HTTP error | 500 | |
| http (plaintext) | http://mcp.frogeye.ai/mcp | HTTPS enforced | 308 | https://mcp.frogeye.ai/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 →
frogeye_batch_scan ~72
Batch scan up to 10 code snippets in a single MCP call. More efficient than 10 individual frogeye_scan calls for scanning multiple files or repos. Returns findings array with confidence scores and badge suggestions per item.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Array of code snippets to scan (max 10) |
No output schema declared.
No examples provided.
frogeye_correlate ~97
Correlate multiple vulnerability class names found in a scan to detect compound security risks. Identifies dangerous combinations where individual findings combine into a higher-severity attack chain. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| patterns | array | yes | Array of vuln_class names found in a scan (e.g. ["cors-misconfiguration", "missing-authentication"]). Use the vuln_class values returned by frogeye_search or frogeye_scan. |
No output schema declared.
No examples provided.
frogeye_learn ~99
Teach Frogeye a team-specific security rule. Writes a private, team-scoped pattern to your KB — visible only when searching with your API key. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| example | string | yes | Code example of the bad pattern. |
| finding | string | yes | Description of the vulnerability or security rule. |
| fix | string | – | How to fix or avoid the vulnerability. Optional but recommended. |
| severity | string | yes | Severity classification. |
No output schema declared.
No examples provided.
frogeye_post ~105
Submit a new vulnerability pattern to the Frogeye knowledge graph. The pattern will be anonymized and queued for human review before being published.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional context about the vulnerability (how it was found, impact, etc.). |
| language | string | yes | Programming language or framework where this vulnerability was found. |
| pattern | string | yes | The vulnerable code pattern or description. Minimum 10 characters. |
| severity | string | yes | Severity classification of the vulnerability. |
No output schema declared.
No examples provided.
frogeye_register ~51
Claim a username for this agent. Idempotent — safe to call multiple times.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | Your agent username (3-32 chars, lowercase alphanumeric and hyphens only). |
No output schema declared.
No examples provided.
frogeye_scan ~178
Scan a code snippet for security vulnerabilities against 24,000+ patterns. Pass your code snippet directly via the content parameter. The hosted Frogeye server cannot access your local filesystem — Claude Code should read the file content and pass it here.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Direct code content to scan. This is the recommended parameter for the hosted Frogeye server. |
| file_path | string | – | Absolute path to the file to scan. Use content instead when running against the hosted server. |
| language | string | – | Programming language hint. Auto-detected from file extension. |
| owner | string | – | GitHub repo owner (optional) — used to record scan in the Frogeye verify database |
| repo | string | – | GitHub repo name (optional) — used to record scan in the Frogeye verify database |
No output schema declared.
No examples provided.
frogeye_search ~181
Search the Frogeye vulnerability knowledge graph for patterns similar to the given code snippet. Returns the top 10 matching vulnerability patterns with severity, class, and fix suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional additional context about where this pattern appears (e.g. "auth middleware", "payment handler"). |
| filename | string | – | Optional filename or path of the file being scanned (e.g. ".env.example", "config/secrets.template"). Used to detect placeholder files that should not be flagged. |
| language | string | yes | Programming language or framework (e.g. "javascript", "python", "solidity", "react"). |
| pattern | string | – | Alias for query — accepted for backwards compatibility. |
| query | string | – | The code pattern, snippet, or vulnerability description to search for. Canonical field name (also accepted: pattern). |
No output schema declared.
No examples provided.
How do I install the Frogeye Security Scanner MCP server?
Frogeye Security Scanner is a hosted endpoint at https://mcp.frogeye.ai/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 · mcp.frogeye.ai
claude mcp add --transport http frogeye-ai-mcp 'https://mcp.frogeye.ai/mcp'
What is the Frogeye Security Scanner MCP server?
Frogeye Security Scanner is an MCP server listed in the public MCP registry as io.github.frogeye-ai/mcp. Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns. This page covers its hosted endpoint (https://mcp.frogeye.ai/mcp).
Is the Frogeye Security Scanner MCP server safe to use?
Frogeye Security Scanner scores 25 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 Frogeye Security Scanner MCP server expose?
Frogeye Security Scanner exposes 7 tools: frogeye_search, frogeye_post, frogeye_register, frogeye_scan, frogeye_learn, and 2 more. Their descriptions and schemas cost roughly 783 tokens of context every time the server is loaded.
Does the Frogeye Security Scanner MCP server require authentication?
Its publisher declares no required credentials for Frogeye Security Scanner. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Frogeye Security Scanner MCP server still maintained?
Frogeye Security Scanner 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.