Frogeye Security Scanner

REMOTE · MCP.FROGEYE.AI · 2 COMPONENTS · SCANNED AUG 3

Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns.

Available components

remote · mcp.frogeye.ai 66 remote · mcp.frogeye.ai 31

+4 this week 66 66 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security63

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 7 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 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 & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability74

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 783 tokens (~111/item across 7 items; 7 tools + 0 resources), lean.Pass
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 Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities40

Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.frogeye.ai

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http frogeye-ai-mcp https://mcp.frogeye.ai/mcp

# ~/.codex/config.toml

[mcp_servers.frogeye-ai-mcp]
url = "https://mcp.frogeye.ai/mcp"

// opencode.json

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

# add to OpenClaw

openclaw mcp add frogeye-ai-mcp --url https://mcp.frogeye.ai/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  frogeye-ai-mcp:
    url: "https://mcp.frogeye.ai/mcp"

// mcp.json

{
  "mcpServers": {
    "frogeye-ai-mcp": {
      "type": "http",
      "url": "https://mcp.frogeye.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

3 Aug 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.
31 Jul 26 +1
- 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
29 Jul 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.
28 Jul 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.
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
26 Jul 26 62

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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=YR2,O=Let's Encrypt,C=US	2 Jul 2026	30 Sept 2026	RSA 2048	SHA256-RSA	53661ab59e9162e2d2aa3263a551bae2fbc
SANs: *.frogeye.ai, frogeye.ai
CN=YR2,O=Let's Encrypt,C=US (CA)	CN=Root YR,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	RSA 2048	SHA256-RSA	4ebd24947e24d394802d84a52fd5b319
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

DNSSEC insecure

Validation of mcp.frogeye.ai. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
ai.	present	3799	8	Verified
frogeye.ai.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

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

Header	Value
strict-transport-security	max-age=63072000
x-content-type-options	nosniff
x-frame-options	SAMEORIGIN
referrer-policy	strict-origin-when-cross-origin

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.frogeye.ai/mcp	Verified	200
http (plaintext)	http://mcp.frogeye.ai/mcp	HTTPS enforced	308	https://mcp.frogeye.ai/mcp

MCP tools — 7 exposed · ~783 tokens

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.

Tool Tokens

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	62
27 Jul	62
28 Jul	63
29 Jul	64
30 Jul	64
31 Jul	65
1 Aug	65
2 Aug	65
3 Aug	66