Five built-in tools, no payment

Start in the browser

Sign in, choose a built-in, load its example and run once. Account sign-in may use a wallet signature; invocation needs no payment signature or USDC. A successful static check is not an audit or security certification.

Connect your own client

Create a limited tools:invoke key with an enabled policy, allowed functions and a quota. Privately configure INVOKEPORT_ORIGIN and INVOKEPORT_API_KEY in the local process environment. Never put a key in prompts, URLs, committed config or logs.

Install invokeport-mcp@0.1.0 using the public MCP setup guide. It exposes search_capabilities, get_capability and invoke_capability. Search and schema retrieval need no key. The connector does not call an LLM or provide a model subscription.

node packages/mcp-connector/example.mjs
# Intentional invalid-input example (exit 1):
node packages/mcp-connector/example.mjs --invalid

Public catalog over HTTP

curl "https://invokeport.com/api/catalog?q=JSON&limit=5"
curl "https://invokeport.com/api/catalog/builtin/json-schema"

Set INVOKEPORT_ORIGIN to https://invokeport.com. For local development, use your local server origin instead. Search returns summaries; detail returns schema and example. Invoke with a limited key and a unique attempt ID. The public MCP guide includes a complete example.

Attempts, errors and limits

Every invoke needs an Idempotency-Key (16–128 letters, digits, underscore or hyphen). Use a unique ID per intended call; a repeated ID is never executed again. Changed input under the same ID conflicts. Original results are not retained.

401: key/auth; 403: policy/tool; 400: input; 429: quota; 409: existing/conflicting attempt. Network errors and unconfirmed 5xx may mean unknown outcome: keep the attempt ID, never automatically retry with a new one. execution_paused and execution_storage_limit mean no admission.

Tool input: 128 KiB; schemas have bounded depth/complexity. Agent quota: 1–60/minute, session quota: 30/minute, shared admission quota: 300/minute. A fixed 100,000 stored-attempt safety cap includes replay guards. Operators can pause a tool or all execution; agents can be disabled or revoked. Limits are enforced again on the server.

Metadata and retention

No request or result bodies are stored. Detailed metadata is visible for 30 days and compacted in bounded batches on activity. Minimal replay guards are retained without automatic expiry so old attempts cannot execute again. Inactive systems do not have a scheduled physical-deletion guarantee. Activity shows period and observation count, not an SLA.