For AI Agents

MCP server

The server speaks MCP over Streamable HTTP at https://www.outfame.com/mcp. It is stateless: send one JSON-RPC message per POST and read the JSON reply. It answers initialize, ping, tools/list and tools/call; a GET returns status 405.

No account, API key or token is needed. The server card is at https://www.outfame.com/.well-known/mcp/server-card.json.

Tools

Tool	What it returns	Arguments
`list_plans`	Outfame's three plans (Go, Grow, Glory) with first-month price in US dollars, what each includes and the sign-up link.	None
`list_free_tools`	Outfame's free Instagram and AI tools (calculators, analyzers, generators) with the page URL and a one-line description of each.	None
`search_blog`	Search Outfame's blog articles by words in the title, description, tags or category. Returns title, URL and description of the best matches.	query (string, 2 to 100 characters, required); limit (whole number, 1 to 10, optional)
`get_company_facts`	What Outfame is, how it works in four steps, and company facts (founding, headquarters, support contacts).	None
`get_signup_link`	The link where a person starts with Outfame (connect an account by username and select a plan), with the steps they will see.	None

Every tool is read-only. Each result has a readable text block and the same data as structured content.

Protocol versions

Version	How it works
`2025-11-25`, `2025-06-18`, `2025-03-26`	Starts with `initialize`; the server answers in the version the client asks for. A client that asks for a version the server does not know gets `2025-11-25`.
`2026-07-28`	No handshake. Every request names its version in the `MCP-Protocol-Version` header and repeats the method and tool name in the `Mcp-Method` and `Mcp-Name` headers; `server/discover` describes the server.

A request without an MCP-Protocol-Version header is treated as 2025-03-26. An unknown version in the header returns status 400 with error code -32022 and the list of supported versions.

Add it to an MCP client

Claude Code:

claude mcp add --transport http outfame https://www.outfame.com/mcp

Clients that read a JSON configuration with a server URL, such as Cursor:

{
  "mcpServers": {
    "outfame": {
      "url": "https://www.outfame.com/mcp"
    }
  }
}

Call it directly

List the tools:

curl -s https://www.outfame.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Call one:

curl -s https://www.outfame.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_plans","arguments":{}}}'

Errors and limits

Case	Answer
Body is not valid JSON	Status 400, error code -32700
A batch (JSON array) or a message that is not JSON-RPC 2.0	Status 400, error code -32600
Body longer than 100,000 characters	Status 413
Request from a browser page on another site	Status 403 (only outfame.com pages may call it from a browser; requests without an Origin header are fine)
A notification or a client response	Status 202, empty body
More than 30 `search_blog` calls a minute from one IP address	A tool result that says to wait a minute, with `{"error":"rate_limited"}` as structured content
GET or DELETE	Status 405: there is no session stream

Pages in this section

AI agents and developer access: what the agent interfaces are and where each one lives.
A2A agent: the A2A endpoint at /a2a: both message methods, the five skills with example questions, the reply format and errors.
REST API for agents: the read-only JSON endpoints under /api/agents/v1, their parameters, response fields and the OpenAPI file.
Account access for agents: reading a user's own account with their approval: OAuth 2.1, auth.md agent registration, the account API and the account MCP server.
Discovery files: the llms.txt, robots.txt and /.well-known files that let agents find these interfaces.