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.3/5 across 1 of 1 tools scored.
Only one tool exists, so there is no risk of confusing it with any other tool.
With a single tool, naming is inherently consistent. 'scan_url' follows a clear verb_noun pattern.
A single tool for a narrowly scoped security scanning server is reasonable, but the server's potential seems underexpressed with only one action.
The server provides only a single scanning operation, lacking any ability to manage or retrieve past scans, which limits its usefulness for broader workflows.
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 | |
| reportUrl | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark readOnlyHint=true and openWorldHint=true, indicating a safe read operation. The description adds that it returns a Launch Readiness score and paste-ready fixes, which enriches the understanding of behavior without contradiction.
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?
The description is two sentences, concise and front-loaded. Every sentence adds value: the first defines the action and findings, the second gives usage guidance. No wasted words.
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?
Given the tool's simplicity (1 parameter, no siblings, output schema present), the description covers purpose, usage, and behavioral outcomes completely. No gaps remain.
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 coverage is 100% for the single 'url' parameter, which includes a clear description and example. The description does not add further parameter details beyond what the schema provides, so a baseline of 3 is appropriate.
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?
The description starts with 'Scan a live URL for leaked API keys, exposed config files and missing security headers.' This clearly states the action (scan) and the specific resources checked, providing a precise purpose. No siblings exist, so no differentiation needed.
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?
The description includes 'Use before deploying, or when checking the security of an app built with AI coding tools like Cursor, Lovable, v0 or Bolt.' This gives concrete use cases. It does not explicitly mention when not to use or alternatives, but the context is sufficient.
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!