InvokeWorks

Paid MCP tools for AI agents, including DNS, TLS, HTTP, and full site audits metered by LiveAuth

Documentation

InvokeWorks

Give your AI agent useful paid tools.

InvokeWorks is an open-source MCP server for useful paid agent tools. Its flagship, site_audit, combines DNS, TLS, HTTP, redirect, and security-header checks into one structured result for 5 sats per call.

An agent can run a complete external site check without creating an account or subscribing to an API. The proof-of-work session flow needs no human payment step. LiveAuth handles MCP authentication and metering; InvokeWorks returns the result and billing metadata, including the receipt. Session budgets and expiry still apply.

Source: https://github.com/dulzuradev/invokeworks
Website: https://invokeworks.dev
MCP endpoint: https://mcp.invokeworks.dev/mcp
Health: https://mcp.invokeworks.dev/health

Tools

Tool	Purpose	Price
`site_audit`	Combined DNS, TLS, HTTP, and security-header audit	5 sats
`dns_lookup`	A, AAAA, CNAME, MX, TXT, NS, and SOA queries	1 sat
`http_inspect`	HTTP status, redirects, headers, size, timing, and security headers	2 sats
`tls_inspect`	TLS protocol, cipher, certificate, SANs, validity, and chain	2 sats

Site Audit

Run a combined DNS, TLS, HTTP, and security-header audit of a public website. LiveAuth meters site_audit at 5 sats/call through the existing gate.

Example input (bare hostnames default to HTTPS):

{ "target": "https://example.com" }

Shortened example output (illustrative; actual results vary):

{
  "hostname": "example.com",
  "score": 95,
  "issues": [
    {
      "severity": "warning",
      "code": "missing_csp",
      "message": "content-security-policy is absent; consider this recommended protection where appropriate."
    }
  ]
}

The full response also includes DNS, TLS, HTTP, and security-header sections. See Site Audit for coverage and examples.

The score is informational, not a formal security certification: start at 100, subtract 25 per critical finding and 5 per warning, subtract nothing for informational findings, and clamp to 0–100. Header presence does not establish policy correctness; recommendations depend on the endpoint's purpose. CSP frame-ancestors satisfies the frame-protection check without X-Frame-Options. HSTS is evaluated only on a final HTTPS response.

DNS returns A, AAAA, CNAME, MX and NS records. Absent records are empty arrays; other query failures appear in failedRecordTypes. TLS describes the original target (on the HTTPS URL port, or port 443 for HTTP inputs), while HTTP describes the final response and redirect chain. TLS verification stays enabled: expired/mismatched certificates produce findings without returning unverified certificate details. Failed TLS/HTTP sections are null; security headers are null when HTTP is unavailable. A non-public or unresolved starting destination fails the call. Failures after charging remain billable with sanitized metadata and receipts. No response bodies are returned.

Stable issue codes: dns_lookup_failed, tls_failed, tls_certificate_expired, tls_certificate_expiring (30 days or less), tls_hostname_mismatch, tls_obsolete_protocol, http_failed, http_not_https, http_insecure_hop, http_error_status, missing_hsts, missing_csp, missing_x_content_type_options, missing_frame_protection, missing_referrer_policy, missing_permissions_policy.

Use InvokeWorks from an MCP client

Connect a Streamable HTTP MCP client to https://mcp.invokeworks.dev/mcp. First obtain an active MCP session token for the InvokeWorks project through the LiveAuth start/confirm flow. The proof-of-work path needs no agent account, API subscription, or human payment step. Supply the JWT as Authorization: Bearer <liveauth-jwt>; discovery is public, but tool calls require authorization.

This JavaScript configuration uses the MCP client package supported by the repo's integration tests. Set LIVEAUTH_JWT to that session token and keep it out of source control.

npm install @modelcontextprotocol/client@^2.0.0

import { Client, StreamableHTTPClientTransport } from '@modelcontextprotocol/client';

const jwt = process.env.LIVEAUTH_JWT;
if (!jwt) throw new Error('Set LIVEAUTH_JWT to an active InvokeWorks MCP session token');

// One ID per logical call. Keep this ID and the arguments unchanged on a retry.
const requestId = crypto.randomUUID();
const client = new Client({ name: 'site-audit-client', version: '1.0.0' });
const transport = new StreamableHTTPClientTransport(new URL('https://mcp.invokeworks.dev/mcp'), {
  requestInit: {
    headers: {
      Authorization: `Bearer ${jwt}`,
      'X-Request-Id': requestId,
    },
  },
});

try {
  await client.connect(transport);
  const result = await client.callTool({
    name: 'site_audit',
    arguments: { target: 'https://example.com' },
  });
  console.log(result); // Audit result plus _meta.liveauth billing metadata / receipt.
} finally {
  await client.close();
}

Example agent task: “Audit https://example.com and tell me the most important issues.”

The agent can invoke site_audit; LiveAuth meters the accepted execution at 5 sats. X-Request-Id is also the billing idempotency key. Keep it and the arguments unchanged for a retry of the same call, and use a new key for a new logical call. Retry-safe charging does not cache results or prevent handler re-execution. Execution failures after charging remain billable. See the connection guide.

Architecture

Agent / MCP Client
  → InvokeWorks
  → LiveAuth authentication + metering
  → site_audit
  → receipt / result

InvokeWorks uses @liveauth-labs/mcp-server ^1.2.0. Input validation happens before the gate; LiveAuth validates authorization and charges before the tool executes.

apps/server: Hono/Node service using MCP SDK v2 createMcpHandler(), with modern stateless 2026-07-28 and SDK-supported 2025-era compatibility.
apps/web: static Astro site.
packages/tools: transport-independent tools and shared catalog registry.
packages/liveauth: the only package importing the public @liveauth-labs/mcp-server SDK.
packages/shared: environment and request utilities.
tests/integration: official MCP client → server → LiveAuth adapter → tool tests.

There is no database, InvokeWorks account system, wallet, or billing implementation.

Local development

Requires Node.js 22+ and pnpm 10.

corepack enable
pnpm install
cp .env.example .env
pnpm dev

The server listens at http://localhost:3000/mcp; health is /health. Run the website with pnpm dev:web.

For local transport testing without a LiveAuth account, set NODE_ENV=test and LIVEAUTH_BYPASS_FOR_TESTS=true; only the literal token test-token is accepted. This configuration is rejected in production.

Configuration

Variable	Required	Description
`LIVEAUTH_PUBLIC_KEY`	Production	LiveAuth project public key (`la_pk_…`)
`LIVEAUTH_API_URL`	No	Defaults to `https://api.liveauth.app`
`HOST` / `PORT`	No	Defaults to `0.0.0.0:3000`
`LOG_LEVEL`	No	Structured log level

Never commit .env or tokens. Clients send Authorization: Bearer <LiveAuth JWT>. Supply a stable, unique X-Request-Id on retries; it becomes the LiveAuth idempotency key. Signed receipts are returned under MCP result _meta.liveauth.

Adding a tool

Create a module in packages/tools/src.
Call defineTool() with one Zod v4 schema, stable name, descriptions, sat price, examples, and handler.
Inject external I/O behind a narrow interface.
Add it to tools in packages/tools/src/index.ts.
Add handler and security tests.

The MCP server and Astro catalog consume the registry automatically. Handlers return { data } and know nothing about MCP or LiveAuth.

Validation

pnpm lint
pnpm typecheck
pnpm test
pnpm build
pnpm test:integration

Integration tests use the official MCP Streamable HTTP client. Real LiveAuth production calls are separate and opt-in because they require a customer project and funded test session.

Security model

http_inspect accepts only HTTP(S), rejects URL credentials, resolves every address, rejects any non-public answer, pins a validated address into the connection, and validates redirects afresh. Redirects, response bytes, and time are capped; caller headers are never forwarded. tls_inspect applies the same destination policy and pinning. MCP bodies are capped at 64 KiB. Logs omit authorization data.

Deploy behind TLS with public Host allowlisting, concurrency/rate limits, and upstream timeouts. LiveAuth remains authoritative for session budgets and charging. See SECURITY.md.

Docker and deployment

docker build -f apps/server/Dockerfile -t invokeworks-mcp .
docker run --rm -p 3000:3000 --env-file .env invokeworks-mcp

Route mcp.invokeworks.dev to port 3000 and preserve Authorization, MCP-Protocol-Version, Accept, and X-Request-Id. Serve apps/web/dist statically for invokeworks.dev. No hosting provider is assumed.

LiveAuth portal setup

Using ordinary customer-facing functionality only:

Create a LiveAuth project and obtain its public key.
Register dns_lookup, http_inspect, tls_inspect, and site_audit at 1, 2, 2, and 5 sats.
Configure budgets/rate limits and Lightning settlement in LiveAuth.
Set the public key in the server environment and run an opt-in real charge/receipt test.

The adapter passes explicit prices, but portal values should match. See docs/liveauth-dogfood.md.

Contributing and license

Read CONTRIBUTING.md. InvokeWorks is available under the MIT License.