Skip to main content
Glama

Sentry MCP

Official
by getsentry
destination.json1.33 kB
{ "namespace": "destination", "description": "These attributes may be used to describe the receiver of a network exchange/packet. These should be used when there is no client/server relationship between the two sides, or when that relationship is unknown. This covers low-level network interactions (e.g. packet tracing) where you don't know if there was a connection or which side initiated it. This also covers unidirectional UDP flows and peer-to-peer communication where the \"user-facing\" surface of the protocol / API doesn't expose a clear notion of client and server.\n", "attributes": { "destination.address": { "description": "Destination address - domain name if available without reverse DNS lookup; otherwise, IP address or Unix domain socket name.", "type": "string", "note": "When observed from the source side, and when communicating through an intermediary, `destination.address` SHOULD represent the destination address behind any intermediaries, for example proxies, if it's available.\n", "stability": "development", "examples": ["destination.example.com", "10.1.2.80", "/tmp/my.sock"] }, "destination.port": { "description": "Destination port number", "type": "number", "stability": "development", "examples": ["3389", "2888"] } } }

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/getsentry/sentry-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server