ProofLayered
Server Details
Free passive growth-bottleneck scan for B2B SaaS websites: visibility, trust, conversion, scale.
- 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/5 across 1 of 1 tools scored.
With only one tool, there is no risk of confusion. The tool's purpose is clearly described and distinct by default.
A single tool named 'growth_bottleneck_scan' follows a clear verb_noun pattern consistent with itself.
One tool is borderline for a server; while the tool is not trivial, the scope feels thin. A few more tools (e.g., for viewing past scans) would be expected.
The server offers only a single scan operation. Missing lifecycle operations like listing, retrieving, or managing scans. The user is directed to an external site for paid results, creating a dead end.
Available Tools
1 toolgrowth_bottleneck_scanAInspect
Free passive scan of a public B2B SaaS website. Returns bottleneck scores (visibility, trust, conversion, scale), the primary public growth blocker, and top fix priorities. Passive only: no credentials, no production access. Full signed diagnosis with deploy-ready fix packs is a flat $490 at prooflayered.com/app.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public company URL, e.g. https://example.com |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description fully carries the burden. It clearly states the tool is passive, requires no credentials or production access, and scans only public websites. This discloses all relevant behavioral traits for an agent to use safely.
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, no redundancy. Front-loaded with the tool's purpose and key outputs, then adds behavioral constraints. Every sentence earns its place.
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?
For a simple tool with one parameter, no output schema, and no annotations, the description covers everything needed: what it does, its passive nature, and what it returns. No gaps.
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?
The only parameter 'url' has a schema description that already explains it. The description adds no additional semantic meaning beyond the schema. With 100% schema coverage, baseline 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 clearly states it performs a 'free passive scan of a public B2B SaaS website' and specifies the outputs: bottleneck scores, primary growth blocker, and fix priorities. The verb 'scan' and resource 'public B2B SaaS website' are specific and unambiguous.
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 explicitly notes it is 'passive only: no credentials, no production access,' setting clear usage boundaries. It also mentions the paid full diagnosis option as an alternative, but does not exclude other potential use cases due to lack of sibling tools.
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!
Related MCP Servers
- Flicense-qualityBmaintenancePassive website security and trust auditor that checks for security, SEO, AI surface, email, and other exposures, producing a score and remediation plan.Last updated
- Alicense-qualityBmaintenanceEvaluates any website's AI visibility with 15 checks across crawlability, structure, content, and connectivity, and provides actionable fixes.Last updated2MIT
- AlicenseAqualityBmaintenanceAudits AI-bot visibility: robots.txt per-bot for 22 AI user-agents (GPTBot/ClaudeBot/PerplexityBot/etc), Cloudflare flags, JSON-LD, sitemap, llms.txt, SPA shell, plus cross-model brand mentions via Perplexity + OpenRouter. 0-100 score. SSRF-guarded, spend-capped.Last updated41MIT
- AlicenseAqualityCmaintenanceBuyer intelligence for technical founders who sell to enterprises — ICP scoring, persona simulation, competitive positioning, deal classification, and 14 more revenue intelligence tools. 50 free queries/month.Last updated231132MIT