WebMCP registry entry
ups.com
What PurposeBot's crawler found when it checked ups.com 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
- ups.com, www.ups.com
- URLs checked
- 5
- Protocol class
- webmcp
- Last seen
- 2026-10-09
- Discovered via
- Top-sites seed list
- Published API endpoints
- 0
- MCP quality score
- not assessed
URLs checked and signals found
- https://ups.com/.well-known/webmcpIndirect probe results only · Top-sites seed list · 2026-10-09
- Probe response body mentions WebMCP (not a JSON document): /.well-known/webmcp, /webmcp, /webmcp.json
- Probe returned HTTP 200 without a machine document: /api-docs, /api/openapi.json, /api/swagger.json, /developers/openapi.json, /docs/openapi.json, /openapi.json, /platform/openapi.json, /swagger.json, /swagger/v1/swagger.json, /v1/openapi.json, /v2/openapi.json
- https://ups.com/developerIndirect probe results only · Top-sites seed list · 2026-10-08
- Probe response body mentions WebMCP (not a JSON document): /.well-known/webmcp, /webmcp, /webmcp.json
- Probe returned HTTP 200 without a machine document: /api-docs, /api/openapi.json, /api/swagger.json, /developers/openapi.json, /docs/openapi.json, /openapi.json, /platform/openapi.json, /swagger.json, /swagger/v1/swagger.json, /v1/openapi.json, /v2/openapi.json
- https://ups.com/developersIndirect probe results only · Top-sites seed list · 2026-10-08
- Probe response body mentions WebMCP (not a JSON document): /.well-known/webmcp, /webmcp, /webmcp.json
- Probe returned HTTP 200 without a machine document: /api-docs, /api/openapi.json, /api/swagger.json, /developers/openapi.json, /docs/openapi.json, /openapi.json, /platform/openapi.json, /swagger.json, /swagger/v1/swagger.json, /v1/openapi.json, /v2/openapi.json
- https://www.ups.com/.well-known/webmcpIndirect probe results only · Top-sites seed list · 2026-10-09
- Probe response body mentions WebMCP (not a JSON document): /.well-known/webmcp, /webmcp, /webmcp.json
- Probe returned HTTP 200 without a machine document: /api-docs, /api/openapi.json, /api/swagger.json, /developers/openapi.json, /docs/openapi.json, /openapi.json, /platform/openapi.json, /swagger.json, /swagger/v1/swagger.json, /v1/openapi.json, /v2/openapi.json
- https://www.ups.com/developersIndirect probe results only · Top-sites seed list · 2026-10-09
- Probe response body mentions WebMCP (not a JSON document): /.well-known/webmcp, /webmcp, /webmcp.json
- Probe returned HTTP 200 without a machine document: /api-docs, /api/openapi.json, /api/swagger.json, /developers/openapi.json, /docs/openapi.json, /openapi.json, /platform/openapi.json, /swagger.json, /swagger/v1/swagger.json, /v1/openapi.json, /v2/openapi.json
Should an agent trust ups.com?
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 ups.com can register and verify their agents and tools to earn a trust score.