Model Context Protocol resources, tools, and rollout status.
You are viewing the bundled MCP catalog, so the route stays useful even if the live catalog or bridge metadata cannot be fetched right now.
Protocol status is generated from live route detection + planned roadmap entries.
Session bootstrap and capability negotiation.
Roles: viewer, researcher, ops
Enumerate available SerenQuant MCP resources.
Roles: viewer, researcher, ops
Read workspace-scoped context payloads.
Roles: viewer, researcher, ops
List callable MCP tools and their schemas.
Roles: viewer, researcher, ops
Execute tools after scope and policy checks succeed.
Roles: viewer, researcher, ops
Filter tools and resources by rollout status, then inspect the selected item before you automate anything.
Selected item
market.searchFind instruments by ticker, venue, or natural-language match.
Risk class
low
Required roles
viewer
HTTP bridge
POST /api/v1/mcp/market/search
Use the generated input and output contracts to validate bridge payloads and downstream agent assumptions.
Use these snippets as a starting point for calling the selected HTTP bridge outside the docs UI.
curl --request POST \
--url "$SERENQUANT_BASE_URL/api/v1/mcp/market/search" \
--header "Accept: application/json" \
--header "Authorization: Bearer $SERENQUANT_API_TOKEN" \
--header "X-Workspace-Id: $SERENQUANT_WORKSPACE_ID" \
--header "Content-Type: application/json" \
--data '{
"query": "string"
}'POST /api/v1/mcp/market/search
Export live generated specs for API clients and MCP integration workflows.
Apr 6, 2026, 12:00 AM
Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.
Open feedback issue