A single MCP initialize call:
curl -sS -X POST https://<your-host>/mcp \
-H "Authorization: Bearer $OWNSONA_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Expected:
{"result":{"capabilities":{"tools":{"listChanged":false}},
"serverInfo":{"name":"ownsona-mcp","version":"1.0.0"},
"protocolVersion":"2025-06-18"},"id":1,"jsonrpc":"2.0"}
A 401 means the bearer token is wrong. A connection refused/reset
generally means Tomcat failed to bind 443 — check
journalctl -u ownsona.service.
End-to-end exercise of every tool:
OWNSONA_API_TOKEN="..." /home/ownsona/ownsona/sql/smoke_test.sh
Run the test suite:
sql/run_tests.sh # unit only
OWNSONA_TEST_DATABASE_URL="postgresql://ownsona:$PGPW@localhost:5432/ownsona_test" \
sql/run_tests.sh # also integration