eSentire MCP Server

An authorization-gated Model Context Protocol server operated by eSentire on its own API host. Every path under https://api.esentire.com/mcp/ answers 401 UNAUTHORIZED with an RFC 9728 challenge (`WWW-Authenticate: Bearer resource_metadata="https://api.esentire.com/.well-known/oauth-protected-resource"`), while paths outside that prefix answer 403 MISSING_AUTHENTICATION_TOKEN — which is how the route family was confirmed to exist. Authorization is Okta-backed OAuth 2.0 authorization code + PKCE, with anonymous RFC 7591 dynamic client registration live at https://api.esentire.com/register. The tool list is not readable without a customer token, so no tool inventory is recorded here.

API entry from apis.yml

apis.yml Raw ↑
aid: esentire-mcp
name: eSentire MCP Server
description: 'An authorization-gated Model Context Protocol server operated by eSentire on its own API
  host. Every path under https://api.esentire.com/mcp/ answers 401 UNAUTHORIZED with an RFC 9728 challenge
  (`WWW-Authenticate: Bearer resource_metadata="https://api.esentire.com/.well-known/oauth-protected-resource"`),
  while paths outside that prefix answer 403 MISSING_AUTHENTICATION_TOKEN — which is how the route family
  was confirmed to exist. Authorization is Okta-backed OAuth 2.0 authorization code + PKCE, with anonymous
  RFC 7591 dynamic client registration live at https://api.esentire.com/register. The tool list is not
  readable without a customer token, so no tool inventory is recorded here.'
humanURL: https://www.esentire.com/what-we-do/security-operations-platform
baseURL: https://api.esentire.com/mcp
tags:
- Model Context Protocol
- Agents
- Security
properties:
- type: MCPServer
  url: mcp/esentire-mcp.yml
- type: Authentication
  url: authentication/esentire-authentication.yml
- type: OAuthScopes
  url: scopes/esentire-scopes.yml
- type: ErrorCatalog
  url: errors/esentire-problem-types.yml