heera.it via Agentimus: AI readiness, traffic, request log, search & index reports, by approval.
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.
Average 4.3/5 across 15 of 15 tools scored.
Most tools are highly distinct: check-page, identify-bot, preview-markdown, preview-schema, read-ai-traffic, read-ai-visibility, read-edge-traffic, read-google-index, read-readiness, read-request-log, read-search-opportunities, read-search-performance, read-search-visibility, scan-exposed-files, suggest-internal-links each target a specific capability or data source. The read-* family is somewhat overlapping conceptually (all read data), but each reads a distinctly different source. Minor potential confusion between read-ai-traffic, read-edge-traffic, and read-request-log since they all touch crawler traffic from different angles.
Tool names follow a consistent agentimus-verb-noun pattern throughout, with verbs clear (check, identify, preview, read, scan, suggest). All use snake_case with a common prefix. Minor deviation: three preview tools use preview while most read tools use read, and what one might expect to be 'read-exposed-files' is named 'scan-exposed-files', creating slight inconsistency in verb choice, but the overall convention is consistent.
15 tools is within the ideal 3-15 range for a well-scoped server. The server covers a coherent domain (AI-visibility, search-readiness, and content optimization for an AEO/GEO platform) and each tool maps to a plausible feature area of that platform: checking pages, reading traffic from various sources, previewing outputs, and suggesting optimizations. No tool feels redundant or unnecessary.
The tool surface covers the domain well: page readability checks, AI traffic from multiple sources (server, edge, request log), search performance from Google and Bing, visibility from both AI and search, readiness scoring, and content suggestions. Obvious gaps include write/update tools (only suggest-internal-links hints at 'write-description / update-content' as referenced tools, but they aren't present in this set) — the tools are almost entirely read-only. The completeness dimension might be judged as slightly incomplete if actions beyond suggestions are expected.
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.
No comments yet. Be the first to start the discussion!
Sign in to create a connector for this server.