WebMCP registry entry
go.aiven.io
What PurposeBot's crawler found when it checked go.aiven.io for WebMCP, MCP, and API discovery signals agents can use.
Evidence
Low evidence
Only indirect probe results were observed (access-protected or inconclusive responses). This entry is listed for completeness and is not indexed.
- Hosts
- go.aiven.io
- URLs checked
- 1
- Protocol class
- webmcp
- Last seen
- 2026-10-09
- Discovered via
- Directory/aggregator discovery
- Published API endpoints
- 0
- MCP quality score
- not assessed
URLs checked and signals found
- https://go.aiven.io/mcp-serverIndirect probe results only · Directory/aggregator discovery · 2026-10-09
- Probe path is access-protected (HTTP 401/403): /api/openapi.json, /api/swagger.json
- Probe returned HTTP 200 without a machine document: /.well-known/webmcp, /api-docs, /developers/openapi.json, /docs/openapi.json, /openapi.json, /platform/openapi.json, /swagger.json, /swagger/v1/swagger.json, /v1/openapi.json, /v2/openapi.json, /webmcp, /webmcp.json
Should an agent trust go.aiven.io?
Discovery signals show that a site exposes something to agents. They do not show who operates it or how it behaves. PurposeBot, the AI agent trust layer, adds identity, provenance, and conduct-based trust scores on top of discovery. Operators of go.aiven.io can register and verify their agents and tools to earn a trust score.