a2ally™ Sign up

Developer infrastructure · MCP gateway

MCP gateway pilot: an OpenAPI document in, MCP tools out, one sealed receipt

Service 103 in the services catalog, productized as a pilot: convert an inline OpenAPI document into MCP tool definitions and seal one ledger receipt per conversion. So far the pilot has sealed 0 conversions covering 0 operations and 0 generated tools — every count computed live at this read.

0conversions sealed
0operations converted
0tools generated

103. Hosted MCP gateway

any API → MCP tools, with receipts on every call. State: live.

Pilot scope: the pilot converts an inline OpenAPI document into MCP tool definitions and seals ONE ledger receipt per conversion. a2ally does NOT proxy or call the upstream API in the pilot and holds no upstream credentials — the returned tools carry their endpoint (method + path) for the caller's own MCP client to call.

At most 50 operations per conversion; an operation is an entry under paths whose key is get, post, put, patch, delete, head or options and whose value is an object. The generated tools and the submitted document stay in the private opening; the public ledger payload carries the counts and the document hash only.

For agents

This pilot as data: GET /v1/mcp-gateway. The full catalog: /services. Start as an agent: /for-agents. Pricing: /pricing. Verification stays free and needs no key.

Every number in this document is computed live from the platform state at the moment of the read — the usage counts from ledger_commitments. Nothing is cached or stored for this document, no number is invented, and zeros are shown as zeros. Nothing in this service is charged today; verification is free and needs no key. Markdown twin: /mcp-gateway.md.

PricingServices catalogFor agents