openapi-diff-mcp-server

Created By
DrSatyra year ago
Overview

What is openapi-diff-mcp-server?

openapi-diff-mcp-server is a server interface designed for AI integration with the openapi-diff tool, which is used for comparing OpenAPI specifications.

How to use openapi-diff-mcp-server?

To use the openapi-diff-mcp-server, you need to build the server JAR file and configure it with a claude_desktop_config.json file for integration with Cloude Desktop.

Key features of openapi-diff-mcp-server?

  • Integration with the openapi-diff tool for comparing OpenAPI specifications.
  • Configurable server settings for easy deployment.

Use cases of openapi-diff-mcp-server?

  1. Comparing different versions of OpenAPI specifications to identify changes.
  2. Assisting developers in maintaining API documentation consistency.
  3. Facilitating automated testing of API changes.

FAQ from openapi-diff-mcp-server?

  • What programming language is openapi-diff-mcp-server written in?

It is written in Java.

  • Is there a license for using openapi-diff-mcp-server?

Yes, it is licensed under the Apache-2.0 license.

  • How can I build the server?

You can build it using Maven with the command mvn clean install.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
DrSatyr
Star
0
Language
Java
License
Apache-2.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

6 hours ago