# Assertible MCP > Assertible lets you automate API testing and monitoring directly from your AI client. You can trigger deployments, run full service test suites, sync complex specifications like OpenAPI or Swagger, validate JSON documents against specific schemas, and get status badges—all by chatting with your agent. ## Overview - **Category:** developer-tools - **Price:** Free - **Tags:** api-testing, continuous-testing, api-monitoring, json-schema, deployment-tracking ## Description Managing an API's quality usually means running a bunch of scripts, checking multiple dashboards, and manually updating specs. This MCP lets you ditch the console commands and just talk to your AI client. You tell it what needs testing, and it handles the rest. Need to see if a new version is stable? Your agent can trigger deployments and run all necessary tests for that service, giving you instant feedback on uptime and reliability. If a change breaks something, you know right away. Plus, when your API specs update, you don't have to manually re-import them; the MCP handles syncing OpenAPI or Swagger files automatically. And if you just need to check if some incoming data is valid, you can validate JSON against a schema without leaving your chat window. It’s all about making sure your APIs stay reliable and that API quality checks are part of your natural conversation flow right through Vinkius. ## Tools ### create_deployment This tool initiates a new deployment for an API and automatically starts running the associated test suite. ### get_service_status_badge Retrieves a ready-to-use status badge URL or markdown snippet that shows the current health of an entire service. ### get_test_status_badge Gets a status badge URL and markdown specifically for one individual test case, so you know exactly what's passing or failing. ### run_service_tests It runs every single available test defined for an entire API service to give you a comprehensive health check. ### run_specific_test This tool lets you execute only one targeted, specific test case when you need to verify just one piece of functionality. ### sync_specification It pulls the latest version of your API definition from sources like OpenAPI or Swagger, keeping all your tests accurate. ### validate_json You submit a JSON document and it checks that data against a specific JSON Schema Draft 4 to ensure it's structured correctly. ## Prompt Examples **Prompt:** ``` Create a deployment for service 'api-prod-123' version 'v2.1.0' in production. ``` **Response:** ``` I've initiated the deployment for version v2.1.0. Tests are now running against the production environment. I'll let you know the results shortly. ``` **Prompt:** ``` Run all tests for service ID '550e8400-e29b-41d4-a716-446655440000'. ``` **Response:** ``` Triggering all tests for the specified service. I'm monitoring the progress and will provide a summary of the pass/fail status once complete. ``` **Prompt:** ``` Validate this JSON payload against the standard schema. ``` **Response:** ``` I'll use the `validate_json` tool to check your document. Please provide the JSON content and the schema you'd like to validate it against. ``` ## Capabilities ### Triggering Deployments It creates a new deployment instance for an API service, which immediately kicks off automated testing. ### Running Comprehensive Service Tests You can run every single test defined for an entire API service to check its overall health and stability. ### Validating JSON Payloads The system checks if a given piece of JSON data matches a specific, predefined schema draft, confirming structural integrity. ### Syncing API Specifications It pulls the latest version of your API definition—whether it's OpenAPI, Swagger, or Postman—to keep all your tests current. ## Use Cases ### Checking Post-Deployment Stability A DevOps engineer finishes a release. Instead of waiting 20 minutes for the CI/CD pipeline to finish, they ask their agent to create_deployment and run all tests for the new version in the chat. The agent provides real-time status updates on whether the service passed its health checks. ### Verifying Schema Changes A backend developer adds a new required field to the API. Before committing, they use validate_json to test several sample payloads against the current schema draft, confirming their data structure is correct before writing any code. ### Keeping Tests Current After an API Update A QA engineer knows the upstream team updated the Swagger definition. They use sync_specification to pull the latest OpenAPI file into their testing environment, ensuring that manually written test scripts aren't running against outdated data models. ### Quickly Checking Service Health A manager needs a quick health check before a call. Instead of logging in to the monitoring portal, they ask their agent for get_service_status_badge and include the status directly in the meeting summary. ## Benefits - You immediately know the API's status without navigating multiple dashboards. Just ask your agent to get a service badge, or check one test with run_specific_test. - When you make code changes, you sync_specification to update your OpenAPI documents instantly. This means your tests always match your actual running API structure. - Debugging is faster because if something breaks after a deploy, you can trigger a new deployment using create_deployment and see the results immediately in your chat thread. - Need to ensure data coming into the system is clean? You use validate_json to check any JSON payload against a schema right where you're working. No separate validation tool needed. - The entire testing process feels natural. Instead of writing `run_service_tests`, you just ask your agent, 'Check the API health,' and it runs everything for you. ## How It Works The bottom line is that you manage API quality by talking naturally to your AI client instead of running multiple commands. 1. First, subscribe to this MCP and enter your Assertible API Token (and optional Sync Token) so your AI client can talk to the service. 2. Next, tell your agent what you need. For instance, ask it to run all tests for a specific service or validate a JSON payload against a schema. 3. Finally, your agent executes the necessary actions and gives you immediate status updates or validation results in plain text. ## Frequently Asked Questions **How do I use Assertible MCP to check if my service is up?** You can get an immediate status update by using get_service_status_badge. This quickly provides a markdown badge that shows whether the entire API service is currently passing or failing its health checks. **Can Assertible MCP validate JSON schemas?** Yes, you use the validate_json tool for this. You provide the document and the schema, and it tells you if the payload conforms to the rules set in the Draft 4 standard. **What is the difference between run_service_tests and run_specific_test?** run_service_tests runs every single test available for that service, giving you a full health picture. run_specific_test lets you pinpoint and execute only one single test case if you suspect an issue with just that function. **Does Assertible MCP help me update my API specs?** Yes, use sync_specification. This tool pulls the latest OpenAPI, Swagger, or Postman definitions automatically, making sure your test environment is always current after an upstream change.