Skip to content
Govalgo logo

Govalgo

Probes MCP servers, OpenAPI specs and plugin manifests by handshake and response time, letting you query by uptime and login requirement.

At a glanceswept 2026-10-12

not read yet

Use

For
teams building AI agents that need dependable MCP servers, OpenAPI tools and AI plugins
Price
Price not read
Activity
Maintainedsite updated 7 months ago
Company
Domain since 2026domain registered
Runs as
API
What people do with it
  • filter tool servers by uptime and latency thresholds
  • find no-auth MCP servers an agent can call directly
  • copy ready-to-paste MCP config snippets into agent setups
The companyeach fact with its source · read 2026-10-12
  • Domain since2026domain registered
How a program reaches itfound, not claimed · read 2026-10-13
  • MCP serverai.arclan/registryverified in the MCP registry
  • Stateanswers, 4 toolschecked 2026-10-13
  • Address to connectarclan.ai/mcp

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Developer tools tools →

Questions this page answers
  • What is Govalgo?

    Probes MCP servers, OpenAPI specs and plugin manifests by handshake and response time, letting you query by uptime and login requirement. It is listed in the Atlas under Developer tools.

  • Who is Govalgo for?

    teams building AI agents that need dependable MCP servers, OpenAPI tools and AI plugins

  • Do people use Govalgo?

    Little sign of use.

  • Is Govalgo still maintained?

    Maintained: site updated 7 months ago.

  • What are alternatives to Govalgo?

    In Developer tools, by use: Inception, Naptha.AI, TRMX, Kaiva · AI infrastructure for real systems, MCP-Builder.ai, MCP Junction.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.