Skip to content

api-contract-validator MCP server

io.github.lazymac2x/api-contract-validatorlazymac2xstreamable-httpv1.0.0Scanned

Cloudflare Workers MCP server: api-contract-validator

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the api-contract-validator MCP server can do

The api-contract-validator MCP server is published by the GitHub account lazymac2x. It has 5 tools. It can create or change data (2 tools: lint_api_schema and generate_mock_from_spec), but cannot delete data. 3 tools only read.

1 tool brings in text other people can write (diff_request_response).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 2Claude Code: ask
  • generate_mock_from_specGenerate mock response data from an OpenAPI spec.No findings

    Why it is in this group

    • The name "generate_mock_from_spec" says "generate": a word for a change.
    Description, as the server wrote it
    Generate mock response data from an OpenAPI spec. Uses examples, defaults, formats, and type heuristics.
  • lint_api_schemaLint an API spec for quality and best practice compliance.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Lint an API spec for quality and best practice compliance. Rules: operation-id-kebab-case, response-success-required, tags-defined, no-empty-description, security-defined.
Only reads 3Show 3 read-only tools
  • check_breaking_changesCompare two OpenAPI spec versions to detect breaking changes: removed paths/operations, new required parameters, removed response codes, operationId renames.No findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.
    Description, as the server wrote it
    Compare two OpenAPI spec versions to detect breaking changes: removed paths/operations, new required parameters, removed response codes, operationId renames.
  • diff_request_responseCompare a real HTTP request/response against an OpenAPI spec contract.Reads text others writeNo findings

    Why it is in this group

    • The name "diff_request_response" says "diff": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "compare" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Compare a real HTTP request/response against an OpenAPI spec contract. Returns per-field violations.
  • validate_openapi_specValidate an OpenAPI 3.x or AsyncAPI spec JSON.No findings

    Why it is in this group

    • The name "validate_openapi_spec" says "validate": a word for reading.
    Description, as the server wrote it
    Validate an OpenAPI 3.x or AsyncAPI spec JSON. Returns structural errors, missing required fields, and warnings.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.lazy-mac.com/.well-known/oauth-protected-resource/api-contract-validator/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.lazy-mac.com/api-contract-validator/mcp: tools/list returned 5 tools to an anonymous client, including lint_api_schema (write), generate_mock_from_spec (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http api-contract-validator https://api.lazy-mac.com/api-contract-validator/mcp
claude mcp add --transport http api-contract-validator https://api.lazy-mac.com/api-contract-validator/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__api-contract-validator__validate_openapi_spec",
      "mcp__api-contract-validator__diff_request_response",
      "mcp__api-contract-validator__check_breaking_changes"
    ],
    "ask": [
      "mcp__api-contract-validator__lint_api_schema",
      "mcp__api-contract-validator__generate_mock_from_spec"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as api-contract-validator. Review it before you use it.

Capability tags behind 1 rule
  • mcp__api-contract-validator__diff_request_response untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.lazymac2x/api-contract-validator/verify?hash=c849ba56069c65cb8c37b581de3a790cb0050cb619402d71c17f0361748683a0" | jq -e '.changed == false'

Pinned hash c849ba56069c, from Nov 21, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.lazymac2x/api-contract-validator/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.lazymac2x/api-contract-validator
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.lazymac2x/api-contract-validator.svg)](https://radar.anlyon.com/servers/io.github.lazymac2x/api-contract-validator)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:38 UTC.

api-contract-validator MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the api-contract-validator MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the api-contract-validator MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the api-contract-validator MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the api-contract-validator MCP server have?

5 tools: 2 write, 3 read. lint_api_schema, generate_mock_from_spec, validate_openapi_spec, diff_request_response and check_breaking_changes.

Does the api-contract-validator MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the api-contract-validator MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the api-contract-validator MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.