Aquant MCP Server (Authenticated)
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport http
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tool quality observed · not scored
tools with readOnly / destructive hints
parameters described (19 total)
state-changing tools without destructiveHint
tool-list tokens (11 tools)
tools over ~1,200 tokens
From an anonymous initialize + tools/list capture measured 2026-10-20; tokens are chars/3.6 of each tool definition. Recorded for the Kin Score's agent readiness as an observed signal — it contributes no points yet.
Tools
part_catalog_lookup— Part Catalog Lookup Look up part information from the catalog using a triage product ID and a user question. Args: payload: The request body containing triage_product_id and question. tenant_id: [TEMPORARY] The tenant ID. This should be removed in the future. db_session: Mock database session (ready for future replacement with real DB) ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "status": "Status", "message": "Message", "parts": [ { "part_id": "Part Id", "part_name": "Part Name", "part_description": "Part Description", "part_image_link": "Part Image Link", "part_url_link": "Part Url Link" } ] } ```part_info— Part Info Retrieve detailed part information given catalog data from the lookup tool. Args: payload: The request body containing catalog_data. tenant_id: [TEMPORARY] The tenant ID. This should be removed in the future. db_session: Mock database session (ready for future replacement with real DB) ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "status": "Status", "message": "Message", "part_info": [ {} ] } ```part_sources— Part Sources Retrieve sources for parts given catalog data, model, and question. Args: payload: The request body containing catalog_data, model, and question. tenant_id: [TEMPORARY] The tenant ID. This should be removed in the future. db_session: Mock database session (ready for future replacement with real DB) ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "status": "Status", "message": "Message", "sources": [ {} ] } ```agent_data— Agent Data Retrieve agents and their proficiency scores based on an observation name. Args: payload: The request body containing observation_name. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "status": "Status", "message": "Message", "agents": [ { "event_agent_name": "Event Agent Name", "proficiency_score": 1.0, "location": "Location" } ] } ```technician_proximity— Technician Proximity Retrieve technicians and their proximity to an asset location. Args: payload: The request body containing asset_location and technicians. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "status": "Status", "message": "Message", "technicians": [ { "event_agent_name": "Event Agent Name", "location": "Location", "proximity_km": 1.0 } ] } ```observation_existence— Observation Existence Check if an observation exists in the loaded data. Args: payload: The request body containing observation_name. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "status": "Status", "message": "Message", "exists": true, "observation_name": "Observation Name" } ```asset_location— Asset Location Retrieve the location of an asset based on its ID. Args: payload: The request body containing asset_id. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "status": "Status", "message": "Message", "asset_location": { "asset_id": "Asset Id", "location": "Location" } } ```preventive_maintenance_check_list— Preventive Maintenance Check List Generate a preventive maintenance check list for a model or asset. Args: payload: The request body containing asset_id. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "schema_version": "Schema Version", "agent_id": "Agent Id", "steps": [], "status": "Status", "message": "Message" } ```summary_report— Summary Report Generate a summary report for a chat history. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "summary_version": "Summary Version", "site": { "name": "Name", "address": "Address" }, "agents_used": [ { "id": "Id", "name": "Name", "status": "Status", "highlights": [ "string" ] } ], "status": "Status", "message": "Message" } ```next_symptom— Next Symptom Generate a next symptom for an asset based on its ID. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "asset_id": "Asset Id", "top_n": 1, "predictions": [ { "rank": 1, "obs_predict": "Obs Predict", "confidence": "Confidence", "how_to_check": [ "string" ] } ], "status": "Status", "message": "Message" } ```health_check— Health Check ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.