WebMCP registry entry
deinai.ai
What PurposeBot's crawler found when it checked deinai.ai for WebMCP, MCP, and API discovery signals agents can use.
Evidence
Machine document or MCP registry listing
The crawler retrieved a machine-readable discovery document, MCP manifest, registry feed, or published API endpoints for this domain, or the MCP registry lists this domain's site.
- Hosts
- deinai.ai
- URLs checked
- 1
- Protocol class
- webmcp
- Last seen
- 2026-10-09
- Discovered via
- MCP registry
- Published API endpoints
- 0
- MCP quality score
- 0.34 (insufficient data)
URLs checked and signals found
- https://deinai.ai/Listed at its site root in the MCP registry · MCP registry · 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 deinai.ai?
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 deinai.ai can register and verify their agents and tools to earn a trust score.