Find a tool. Read its schema. Run a free call.

1. Connect the MCP server

Install Node.js 22.5 or later. Add this STDIO server to your MCP host. Search and schema retrieval work without an account or API key.

{
  "mcpServers": {
    "invokeport": {
      "command": "npx",
      "args": [
        "-y",
        "invokeport-mcp@0.1.0"
      ],
      "env": {
        "INVOKEPORT_ORIGIN": "https://invokeport.com"
      }
    }
  }
}

On Windows, hosts that require an executable can use cmd with arguments ["/c", "npx", "-y", "invokeport-mcp@0.1.0"].

To install the archive directly: npm install https://invokeport.com/downloads/invokeport-mcp-0.1.0.tgz. Then launch Node with the absolute installed invokeport-mcp/server.mjs path.

2. Discover and inspect

Ask your agent to call search_capabilities with {"query":"JSON"}, then get_capability with {"tool":"json-schema"}. The response includes the input schema, output schema and an example.

The supported tool IDs are openapi-security, json-schema, csv-json, json-types and webhook-check.

3. Allow one free tool and invoke

Sign in, create an account profile if prompted, and create a limited key in Keys. Choose tools:invoke, allow json-schema and set a quota. Sign-in uses an off-chain wallet message. The free call requires no USDC or payment signature.

Supply INVOKEPORT_API_KEY through your host's private secret settings. Keep the key out of prompts, URLs and committed configuration. Call invoke_capability once with a fresh attempt ID:

{
  "tool": "json-schema",
  "input": {
    "schema": {
      "type": "integer",
      "minimum": 1
    },
    "value": 2
  },
  "attemptId": "replace-with-a-fresh-uuid"
}

Expect valid: true, builtin: true, mode: "free-beta" and a request ID. Check the server-observed call in connection diagnostics.

If the response is uncertain, retain the attempt ID and do not automatically retry. The connector refuses payments, redirects and external tools. Server policies, quotas and replay protection apply to every call.