Latitude 10 MCP Server Kit

What is the Latitude 10 MCP Server Kit?

Point it at your OpenAPI spec and Claude, ChatGPT, Cursor and other agents can use your API as MCP tools, with the parts a hello-world MCP server skips: authentication and OAuth, per-tool scopes, input validation, rate limits, an audit log, usage metering, pay-per-call and a deploy story.

It speaks both the new stateless MCP (2026-07-28) and the 2025 versions most clients still use, on one endpoint. Code you own: a TypeScript server that runs in Docker, on Fly.io, on Vercel or over stdio.

Want it built, tested through AgentCore Gateway and listed for you? That’s the Agent Listing Sprint.

You run this code and are responsible for it: review it, test it on staging, and check that it meets the laws, platform rules and security standards that apply to you before production. It is not legal, compliance or financial advice, and using it doesn’t make Latitude 10 your payment processor or service provider.

What do you get?

• OpenAPI 3.0/3.1 → MCP tools, read-only by default; re-import keeps your edits
• MCP 2026-07-28 and 2025-11-25 on one endpoint, plus stdio
• API keys and OAuth 2.1 (Auth0, Clerk, WorkOS, Amazon Cognito…) with scope step-up
• Tested as an AWS AgentCore Gateway target, ready for an AWS Marketplace listing
• Your API’s credentials stay on the server, never the client’s token
• Validation, rate limits, budgets and an audit log of every tool call
• Pay-per-call tools over x402 (USDC) and MPP (Stripe, Tempo)
• Postgres or Supabase; deploys with Docker, Fly.io or Vercel

Every kit includes

• The full source code, yours to change
• A setup wizard: node setup.mjs
• A versioned release with a changelog
• A download link that always serves the latest release

How do you set it up?

Imports your OpenAPI spec (or a demo API) as tools, writes your secrets, sets up the database, then boots the server and proves it: both MCP versions, a tool call through to your API, auth, and payment terms for agents.

You'll need: Node.js 22+ and your API’s OpenAPI spec. Optional: Docker or a Supabase project, an OAuth provider, a wallet for x402.