Frogeye Security Scanner
REMOTE · MCP.FROGEYE.AI · 2 COMPONENTS · SCANNED SEP 20
Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns.
Available components
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 fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. 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 sse, 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.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.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.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.
How do I install the Frogeye Security Scanner MCP server?
Frogeye Security Scanner is a hosted endpoint at https://mcp.frogeye.ai/sse, 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/sse'
{
"mcpServers": {
"frogeye-ai-mcp": {
"url": "https://mcp.frogeye.ai/sse"
}
}
} {
"servers": {
"frogeye-ai-mcp": {
"type": "http",
"url": "https://mcp.frogeye.ai/sse"
}
}
} [mcp_servers.frogeye-ai-mcp] url = "https://mcp.frogeye.ai/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"frogeye-ai-mcp": {
"type": "remote",
"url": "https://mcp.frogeye.ai/sse",
"enabled": true
}
}
} openclaw mcp add frogeye-ai-mcp --url 'https://mcp.frogeye.ai/sse' --transport streamable-http
mcp_servers:
frogeye-ai-mcp:
url: "https://mcp.frogeye.ai/sse" {
"McpServers": {
"frogeye-ai-mcp": {
"Transport": "http",
"Url": "https://mcp.frogeye.ai/sse"
}
}
} assistant mcp add frogeye-ai-mcp -t streamable-http -u 'https://mcp.frogeye.ai/sse'
{
"mcpServers": {
"frogeye-ai-mcp": {
"type": "http",
"url": "https://mcp.frogeye.ai/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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 25
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- 21 Aug 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Aug 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Aug 26 0
- Stability: 0.77 → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: pass → unverified ▼ functional
- Schema quality: excellent → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Aug 26 0
- Authorization: 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. security
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Stability: fail → 0.77 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Aug 26 0
- Stability: unverified → fail ▼ security
- MCP protocol: unverified → fail ▼ functional
- Schema quality: fail → unverified ▼ functional
- Schema quality: pass → unverified ▼ functional
- Schema quality: excellent → unverified ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.67 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified 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 20 Sept 2026 · Probed https://mcp.frogeye.ai/sse
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 | 2 Sept 2026 | 1 Dec 2026 | RSA 2048 | SHA256-RSA | 6c8fed171cf59156ae94ec27a13ab13d1a2 |
| 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 | 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 | 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 |
|---|---|---|---|---|
| sse | https://mcp.frogeye.ai/sse | HTTP error | 500 | |
| http (plaintext) | http://mcp.frogeye.ai/sse | HTTPS enforced | 308 | https://mcp.frogeye.ai/sse |
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 →
No tool schema has been captured from this endpoint yet.
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/sse).
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.
Does the Frogeye Security Scanner MCP server require authentication?
No. We connected to Frogeye Security Scanner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.