View the way your MCP server works from different hosts. Experience your MCP the way the user experiences it from their Claude Code or Cursor. Try at @AgentStatus

Sep 21, 2026 · 9:38 PM UTC

8
11
167
Sort replies: Relevant Recent Liked
Replying to @RomanMoska1enko @AgentStatus
cross-host testing seems especially useful for catching differences in tool discovery and result rendering. does it show the actual tool calls alongside what the user sees?
1
22
it does. we walk all the steps and test every tool that is presented to each host by a given mcp
4
Replying to @RomanMoska1enko @AgentStatus
i only ever tested my mcp server in claude code. ran it in cursor and half the tools behaved differently. worth checking both before shipping.
5
2
63
absolutely! will really appreciate if you give agentstatus a go and give me feedback. also add your mcp to the global mcp index for your seo agentstatus.dev/mcp-index

Public MCP Score | AgentStatus

Public MCP Score ranks production MCP URLs: reach, catalog, call, job, and protocol era. Not a URL ping.

agentstatus.dev
12
Replying to @RomanMoska1enko @AgentStatus
understanding your mcp server's functionality is key for optimization
6
Replying to @RomanMoska1enko @AgentStatus
strict schemas fixed so many of my tool calls. optional booleans are where mine kept breaking too, good to hear it's not just me.
2
Replying to @RomanMoska1enko @AgentStatus
Seeing an MCP server from multiple hosts is useful, but the stronger test is observing failures and permission boundaries under realistic user workflows, not just viewing the tool surface.
1
14