Opzyai Vibe Check
Server Details
Free no-account URL security scan: 0-100 Launch Readiness score for any live site in ~15 seconds.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of ambiguity between tools.
With a single tool, naming is trivially consistent and follows a clear verb_noun pattern.
The server has only one tool, which is on the low end for a typical MCP server. While it serves a focused purpose, the single tool offers a limited surface area.
The tool 'scan_url' comprehensively covers security scanning for a live URL, including leaked API keys, exposed configs, missing headers, and provides a readiness score and fixes. No obvious gaps are present for its stated domain.
Available Tools
1 toolscan_urlRun a Vibe CheckARead-onlyInspect
Scan a live URL for leaked API keys, exposed config files and missing security headers. Returns a Launch Readiness score (0-100) and a paste-ready fix for each finding. Use before deploying, or when checking the security of an app built with AI coding tools like Cursor, Lovable, v0 or Bolt.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The full public URL of the live app to scan, e.g. https://myapp.vercel.app |
Output Schema
| Name | Required | Description |
|---|---|---|
| host | Yes | |
| score | Yes | |
| findings | Yes | |
| reachable | Yes | |
| reportUrl | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true (safe read) and openWorldHint=true (external network access). Description adds that it returns a score and paste-ready fixes, but doesn't cover error handling or prerequisites beyond 'live public URL'.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences plus a usage recommendation, no fluff. Information is front-loaded and every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With output schema present and good annotations, the description is complete for a single-parameter tool. Slightly lacking on error conditions but acceptable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema already fully describes the single parameter ('full public URL' with example). Tool description repeats 'live URL' but adds minimal extra meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool scans a live URL for security issues (leaked keys, config files, headers) and returns a score and fixes. Specific verb+resource, no siblings to differentiate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says 'Use before deploying, or when checking security of apps built with AI coding tools.' Provides clear context but no exclusions or alternatives; still effective.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!