Transport
Did the remote endpoint respond, and how long did the request take?
Remote MCP observability
Observe the remote path from auth to outcome
Remote MCP servers add an authorization boundary before the tool call. TrackMCP helps you see the transport, protected-resource discovery, token result, tool execution, and workflow that follows.
remote HTTP tracecomplete
1client
2metadata
3authorize
4tools/call
5outcome
401
auth challenge visible
tools/call
search_docs · 142ms
result
workflow completed
What to watch
Authorization is part of the user experience.
A remote server can be reachable and still unusable. Keep the auth boundary and the agent workflow in the same operational picture.
Authorization
Did protected-resource discovery, token exchange, or scope validation fail?
Tool execution
Which tool was called, what result came back, and did the client retry?
Workflow outcome
Did the multi-step task finish, or did the agent abandon the session?
Version-aware and privacy-aware
Keep the evidence you need, redact what you do not.
Protocol and authorization behavior changes over time. Record the client, deployment, status, duration, error class, and version context that lets your team reproduce a failure without shipping secrets.
clientprotocolstatusdurationerror class
remote-callsafe to investigate
endpointapi.example.com/mcp
authorizationbearer · valid
toolsearch_docs
payloadredacted locally
Remote MCP observability
Make the invisible boundary visible.
Follow one remote request from challenge to completed tool call.