Glasser
Server Details
One key to 1,000+ paid data APIs: enrichment, SEO/SERP, scraping, places, news. Pay per call.
The last two health checks of this connector failed. 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
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- glasser-ai/plugins
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 7 tools
Each tool occupies a distinct slot in the search→inspect→run→monitor workflow: search finds endpoints, inspect reads a contract, run executes, runs_get/runs_list/runs_stop manage runs, and balance checks funds. There is no plausible confusion between any pair — even run vs runs_get is clearly split between 'create a run' and 'read one run'.
The run-management family follows a clean noun_verb pattern (runs_get, runs_list, runs_stop), but the remaining tools are bare verbs/nouns (balance, inspect, run, search) with no prefix, so 'run' sits awkwardly next to 'runs_*' where 'runs_create' would be expected. The convention is readable and mostly predictable, just not uniform.
Seven tools is well-scoped for an endpoint-marketplace proxy: discovery, contract inspection, execution, run lifecycle (get/list/stop), and balance accounting. Every tool earns its place with no redundancy or bloat.
The core paid-execution lifecycle is fully covered: search, inspect, run, get/list/stop runs, and balance — with idempotency, async status, and charging semantics all addressed. Minor gaps exist around task/work management (task_id is threaded through tools but there is no explicit tool to list or inspect tasks) and no endpoint browsing beyond keyword search.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Hundreds of scraping & data APIs through one key. USD pay-per-request, normalized schemas, failover.
One key and one balance for 2,500+ data APIs from 90+ providers. Your AI agent pays per call.
One key for 4,000+ tools: web search, scraping, people and company data, SEO, calls and email.
140+ data APIs for agents: finance, banking validation, geo, weather, text. One API key.
Related MCP Servers
AlicenseAqualityBmaintenanceLive search on six engines (Google, Bing, Yandex, Baidu, DuckDuckGo, Ecosia), image search and single/batch page extraction for AI agents. Keeps source engine and rank. Runs against a self-hosted OpenSERP server or OpenSERP Cloud.1910240 npm3MIT- AlicenseAqualityNot gradedmaintenanceUnified API for Government Data and Web Scraping100-
- -licenseNot gradedqualityCmaintenanceTwitter/X, YouTube, Reddit, Google and more - 100+ endpoints in total. No account, no OAuth, no subscription. Pay per call in USDC, or top up once and spend one balance across all of them.2-
- AlicenseNot gradedqualityBmaintenanceProvides live web and document intelligence, including search, company news, scraping, crawling, structured extraction, document parsing, brand intelligence, screenshots, website monitoring, and batch jobs.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.