Openclaw Output Vetter MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 74 installs a week from pypi.
Verify AI agent claims vs reality: inline grounding-check + swallowed-exception + transcript review.
The linked repository no longer exists on GitHub — it was deleted or made private.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add openclaw-output-vetter-mcp -- uvx openclaw-output-vetter-mcp
{
"mcpServers": {
"openclaw-output-vetter-mcp": {
"args": [
"openclaw-output-vetter-mcp"
],
"command": "uvx"
}
}
}
[mcp_servers.openclaw-output-vetter-mcp]
command = "uvx"
args = ["openclaw-output-vetter-mcp"]
{
"mcpServers": {
"openclaw-output-vetter-mcp": {
"args": [
"openclaw-output-vetter-mcp"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"openclaw-output-vetter-mcp": {
"args": [
"openclaw-output-vetter-mcp"
],
"command": "uvx"
}
}
}
Answers built from our own checks of this server.