Skip to main content
Glama

Server Details

Access-posture reports for agent data sourcing: robots, bot wall, licensing. Paid per call via x402.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
63.6% over 23 days
Last Tested
Transport
Streamable HTTP
URL

TDQS

A4.1/5.0

Scored across 11 tools

Disambiguation3/5

Several tools answer closely related questions about robots permissions, agent posture and page data (e.g. robots_check/can_fetch/crawl_policy, page_posture/posture_preview/pages_posture/page_report, page_sources/page_data), so misselection is possible. The descriptions explicitly differentiate use cases, pricing and batching, which helps, but the overlapping clusters still require careful reading.

Naming Consistency4/5

All tool names use snake_case, with mostly noun_noun patterns like page_posture, origin_policy and page_sources. Minor deviations are can_fetch (verb_noun) and robots_check (noun_verb), but the set remains readable and predictable.

Tool Count4/5

11 tools is within a reasonable range for a multi-tier posture/data API, and each maps to a discernible operation. However, the set includes several deliberate variants—free previews, paid single calls, batch calls and composed bundles—making it slightly heavier than a minimal tool surface would need to be.

Completeness4/5

The surface covers crawl permission, origin and domain policy, page posture, page sources, page data and composed reports, which is strong lifecycle coverage for this domain. Gaps remain, such as no batch versions for page_data/page_sources/domain_report and no raw robots.txt retrieval, but core agent-access workflows are supported.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Addedorigin_policy
  2. 1 tool update
    • Addedcan_fetch
  3. 1 tool update
    • Addedcrawl_policy
  4. 1 tool update
    • Addeddomain_report
  5. 1 tool update
    • Addedpage_report
  6. 1 tool update
    • Addedpages_posture
  7. 1 tool update
    • Addedrobots_check
  8. 1 tool update
    • Addedpage_data
  9. 3 tool updates
    • Changedpage_posture1 field changed
      • addedInput schema / properties / url / description
        Added value: +"Public http(s) URL to analyse. Must be reachable from the internet; private, loopback and link-local addresses are refused (target_not_analysable) and are never charged for."
    • Addedpage_sources
    • Changedposture_preview1 field changed
      • addedInput schema / properties / url / description
        Added value: +"Public http(s) URL to analyse. Must be reachable from the internet; private, loopback and link-local addresses are refused (target_not_analysable) and are never charged for."
  10. 2 tool updates
    • First observedpage_posture
    • First observedposture_preview

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources