Skip to main content
Glama

Server Details

Scan any URL for AI agent readability — Vercel Spec, llmstxt.org, and agent-protocol manifests.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
mlava/agent-ready-mcp
GitHub Stars
1
Server Listing
Agent Ready

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

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.

100% free. Your data is private.
Tool DescriptionsA

Average 4.3/5 across 3 of 3 tools scored.

Server CoherenceA
Disambiguation5/5

Each tool has a clear, distinct purpose: 'ask' for searching content, 'scan_site' for initiating scans, and 'get_scan' for retrieving results. There is no overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent lowercase underscore pattern with a verb_noun structure (ask, get_scan, scan_site), making them predictable and easy to understand.

Tool Count5/5

Three tools are perfectly scoped for this server's purpose: one for knowledge search, two for scanning operations. Each tool serves a necessary function without redundancy.

Completeness4/5

Core workflows are covered: scanning, retrieval, and knowledge search. Missing are listing scans or managing content, but the server is focused on execution and search, so gaps are minor.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.