# Transica

> Transica handles the whole lifecycle of an MCP app (a Model Context Protocol server) that puts your product inside ChatGPT, Claude and other AI assistants: it builds the app from your API, secures it with the sign-in your customers already use and per-tool access, gets it ready for the ChatGPT app directory and Claude's Connectors Directory, hosts it on your own domain, and keeps it working after listing.

What Transica does:
- Build: drafts MCP tools from your API spec (OpenAPI), your existing MCP server, or what AI agents observe on your site; you approve each tool.
- Get listed: checks your app against each directory's published requirements (tool annotations, sign-in, privacy policy, test account) and prepares the listing.
- Host: runs the app at an address on your domain (for example mcp.yourcompany.com) with OAuth sign-in through your existing identity provider, health checks every 15 minutes, alerts and per-tool usage by AI app.
- Secure: OAuth through your existing identity provider, with each tool public or signed in; tools that change data are public only when you approve them by name.
- Maintain after listing: daily checks of each directory's rules, health checks every 15 minutes, tool-change versions and diffs, and email alerts.
- Test: agent tests run AI agents on your website and through your app, and report exact pass counts.
- Free page scan, no account needed: checks whether AI tools can reach, read and use a page.
- Free MCP directory check, no account needed: checks a public MCP server against the ChatGPT and Claude directory requirements.

## Main pages
- [Home](https://transica.dev/): overview of build, get listed and host
- [Pricing](https://transica.dev/pricing): plans, including a free plan
- [MCP directory check](https://transica.dev/tools/mcp-directory-check): free tool: check any public MCP server against ChatGPT and Claude directory requirements
- [Agent tests](https://transica.dev/agent-test): how AI agents are tested on your site and app
- [Methodology](https://transica.dev/methodology): how the readiness scan and agent tests are graded
- [About](https://transica.dev/about): what Transica is, how we work and how to reach us
- [Contact](https://transica.dev/contact): talk to us
- [Full text](https://transica.dev/llms-full.txt): every guide and blog post in one Markdown file

## Guides
- [How to submit your app to ChatGPT's plugin directory (2026)](https://transica.dev/guides/chatgpt-app-directory): What OpenAI asks for before your app (now called a plugin) appears in ChatGPT's directory: verification, a public MCP server, sign-in, test cases and review. With links to OpenAI's docs.
- [How to get your connector listed in Claude's Connectors Directory](https://transica.dev/guides/claude-connectors-directory): What Anthropic checks before your MCP connector appears in Claude's directory: tool annotations, OAuth, a test account, the common rejection reasons and the Community and Verified labels.
- [Host your MCP server on your own domain, behind your existing sign-in](https://transica.dev/guides/mcp-server-hosting): What it takes to run an MCP server that ChatGPT and Claude can rely on: a public HTTPS address on your domain, OAuth through your identity provider, health checks, alerts and usage by AI app.
- [Turn your API into an MCP server for ChatGPT and Claude](https://transica.dev/guides/turn-your-api-into-an-mcp-server): How to go from an OpenAPI spec (or no spec at all) to MCP tools that AI assistants can use: picking operations, naming tools, splitting reads and writes, and testing them with AI agents.
- [Keep your ChatGPT and Claude listings healthy after launch](https://transica.dev/guides/manage-ai-app-listings): Getting listed is the start. Here's what changes after launch (directory rules, your tools, uptime) and how to keep your MCP listings working in ChatGPT and Claude.
- [Where to list your MCP server: every directory, checked October 2026](https://transica.dev/guides/where-to-list-your-mcp-server): ChatGPT, Claude, the official MCP Registry, Microsoft Copilot, Cursor and the community directories: which ones take submissions, what each needs and where to start.
- [MCP and AI app glossary: plain-English definitions for owners](https://transica.dev/guides/mcp-glossary): MCP, servers, tools, connectors, plugins, OAuth, tool annotations, MCP Apps and more: the terms you meet when you bring your product to ChatGPT and Claude, each linked to its official source.
- [Ways to get your API into ChatGPT and Claude, compared](https://transica.dev/guides/ways-to-build-an-mcp-server): Build it yourself with the MCP SDKs, generate it from OpenAPI, host it on Cloudflare or Vercel, use an integration platform, or use Transica: what each gives you, what's left for you to do, and who it suits.
- [The MCP server lifecycle: build, secure, list and maintain (2026)](https://transica.dev/guides/mcp-server-lifecycle): What an MCP app goes through to work in ChatGPT and Claude, and to keep working: choosing tools, building, sign-in and per-tool access, testing, hosting, review, and the upkeep after listing.
- [MCP OAuth and authentication for ChatGPT and Claude (2026)](https://transica.dev/guides/mcp-server-authentication): MCP OAuth and authentication for ChatGPT and Claude: metadata documents, app registration, PKCE, tokens bound to your server, refresh, and how to chain sign-in to the identity provider you already have.
- [Per-tool access in MCP servers: public tools, signed-in tools and scopes](https://transica.dev/guides/mcp-per-tool-access): Let ChatGPT and Claude use some MCP tools without sign-in, ask for sign-in only when a tool needs someone's account, give each tool the narrowest permission, and ask for more later without breaking the chat.
- [ChatGPT app for WooCommerce stores: products, orders and shopper sign-in (2026)](https://transica.dev/guides/chatgpt-app-for-woocommerce): What a WooCommerce store can put in ChatGPT today: product feeds, staff tools, chat widgets, and a store's own app in ChatGPT's plugin directory where shoppers sign in with their store account to check their orders.

## Blog
- [WarrantyWarden: from website to ChatGPT's plugin directory](https://transica.dev/blog/warrantywarden-chatgpt-plugin-directory): OpenAI approved WarrantyWarden for ChatGPT's plugin directory on 29 October 2026. What the plugin does, how it was built and hosted with Transica, how sign-in works, and what review flagged on the way.
- [AI agent traffic in numbers (2025–2026)](https://transica.dev/blog/ai-agent-traffic-in-numbers): What Cloudflare, Adobe, Pew, Imperva, HUMAN and Akamai have measured about AI crawlers and agents, what the numbers can and can't tell you, and what the shift means for your website.
- [Who's already inside ChatGPT, Claude and Copilot](https://transica.dev/blog/big-brands-in-chatgpt-and-claude): A dated timeline of the brands that built apps for AI assistants from 2024 to 2026, what those apps let people do, how the checkout experiment went, and what a mid-size business can take from it.
- [How to get your product listed in ChatGPT and Claude (2026)](https://transica.dev/blog/get-listed-in-chatgpt-and-claude): ChatGPT has 1.2 billion weekly users and Claude's directory lists 973 connectors. Here's what each directory asks for, side by side, what the big brands did first, and the mistakes that get apps bounced.
- [The MCP ecosystem in numbers (October 2026)](https://transica.dev/blog/mcp-in-numbers-2026): When ChatGPT, Gemini, Copilot and Claude adopted MCP, how fast the SDKs grew, how big the directories say they are, how well AI agents do on MCP tasks and how many servers are exposed, each number linked to its source.
- [MCP tool design: best practices from the directory rules and the research](https://transica.dev/blog/mcp-tool-design-best-practices): Eleven practices for MCP tools that AI agents pick correctly and the ChatGPT and Claude directories accept, drawn from OpenAI's and Anthropic's published rules, the MCP spec and the research, with every outside number linked to its source.
- [What's a live app? Hosting your MCP app on your own domain, behind your sign-in](https://transica.dev/blog/what-is-a-live-app): About 70% of exposed MCP servers hand their tool list to anyone who asks. Here's what it takes to run an app ChatGPT and Claude can rely on: your domain, your sign-in, the 2026 auth rules, monitoring, and what we handle for you.
- [Why AI agents trip up on websites, and what an app changes](https://transica.dev/blog/why-ai-agents-trip-up-on-websites): Browser agents went from 14% to around 60–70% on the standard benchmarks in under three years, but they're still slower, costlier and flakier than people. Here's what the research shows, and when an MCP app actually helps.