"How to call a smart contract function" matching MCP servers:

MCP server for scanning smart contracts for security vulnerabilities. It detects issues like reentrancy, overflow, access control, and provides security scores with NEAR-specific recommendations.

Enables validating API responses against expected schemas/JSON and listing OpenAPI endpoints to enforce API contracts between services.

An MCP server that turns Zod schemas into mocks, violations, and contract tests, enabling AI agents to reason about API contracts without manually crafting payloads.

Enables AI clients to validate OpenAPI specs, compare versions, detect breaking changes, and generate changelogs.

Enables browser automation and API testing for AI agents using Playwright and Chrome DevTools Protocol, with numbered element references, Set-of-Mark screenshots, flow recording/replay, element memory, captcha handoff, and HTTP API test suites.

Generates standalone, human-readable MCP servers from RAML 1.0 or OpenAPI 3.x specs, exposing one tool per resource and method that makes real HTTP calls. It understands Mule/Anypoint auth patterns such as Client ID enforcement and OAuth2, wiring the expected credentials from environment variables at call time.

Converts any REST API endpoints into MCP tools, enabling AI clients like Cursor and Claude Desktop to call internal services directly.

Converts REST API code (like NestJS controllers or FastAPI endpoints) to Postman collections and environments, helping developers automatically sync their API endpoints with Postman.

MCP server that fetches API responses and generates ready-to-use model/POJO classes in your configured language, with built-in login/refresh token handling.

A tool that creates MCP (Model Context Protocol) servers from OpenAPI/Swagger specifications, enabling AI assistants to interact with your APIs.

Auto-generates MCP tools from your OpenAPI spec, allowing natural language interaction with any API via configurable headers and serverless deployment.

A bridge that enables any LLM to access and interact with documented REST APIs through the Model Context Protocol (MCP).

A minimal MCP server that auto-generates tools from your OpenAPI spec, optimized for Vercel.

A standalone proxy that transforms any OpenAPI or Swagger-described REST API into an MCP server by mapping API operations to executable MCP tools. It enables AI clients to interact with existing web services through automated HTTP requests based on their official documentation.

Automatically converts Swagger/OpenAPI specifications into dynamic MCP tools, enabling interaction with any REST API through natural language by loading specs from local files or URLs.

Converts natural language queries into valid GraphQL queries and executes them against GraphQL APIs. Includes schema introspection, query validation, execution with authentication, and query history tracking.

Turn any GraphQL API into MCP tools. Zero config, zero code. Auto-introspection, flat InputObject schemas for better LLM accuracy, smart truncation, retry logic with exponential backoff.

Provides a testable gateway path for running a local MCP-style server in hosted-like conditions, with tenant-isolated reads, approval-denied writes, deterministic failures, and smoke-test verification.

Converts OpenAPI specifications into MCP services with HTTP header passthrough support. Enables interaction with any OpenAPI-compliant service through natural language by dynamically transforming API documentation into MCP tools.

Automatically converts any OpenAPI specification or Postman Collection into an MCP server, enabling AI assistants like Claude to directly interact with REST APIs without writing any code.