Developer · Remote MCP server

AI Success Story

First-person AI war-stories from coding sessions, searchable via MCP for prior-art consultation.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.Un3x/ai-success-story
Version
0.1.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-05-20
Updated
2026-05-20
Publisher
Un3x (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/Un3x) · how
Repository
github.com/Un3x/ai-success-story
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://ai-success-story-20f19ed7769b.herokuapp.com/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 404)
Handshake
HTTP 404
Checked on
2026-10-05

How the live check works

How to connect AI Success Story

AI Success Story is a remote MCP server: there is nothing to install. Its endpoint is https://ai-success-story-20f19ed7769b.herokuapp.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
AI Readiness KitGenerate 18 AI readiness files (llms.txt, ai.txt, RAG indexes, schema) for any website.Remote · HTTPLive check: ✓ handshakeai.silverbackmarketing.com
AI ScannerScan codebases for LLM/AI SDK usage, exposed API tokens, and hardcoded secrets.Local · stdionpm: ai-scanner-mcp
AI Site ScorerCheck website AI-readiness: Schema.org, llms.txt, E-E-A-T, robots.txt. Works in Cursor & Claude.Remote · HTTPLive check: ✓ handshakeai-readiness.mingles.ai
AI Skill StoreAgent-first skill marketplace with USK open standard for Claude, Cursor, Gemini, Codex CLI.Remote · HTTPLive check: ✗ no handshakeaiskillstore.io
Ai SupplySearch, install, publish & review security-scanned AI capabilities from ai-supply.store.Local · stdionpm: ai-supply-mcp
AI UsageReports real token usage and cost from Claude Code and OpenCode data. Nothing leaves your machine.Local · stdionpm: ai-usage-mcp
Ai ValidationIndependent AI code validation: test bias, edge cases, coverage gaps.Local · stdionpm: ai-validation-mcp
AI Visibility Audit - Can AI crawlers read and cite your site?One-call audit: robots.txt AI-bot rules, llms.txt, JSON-LD, meta tags, sitemap. Score plus fixes.Remote · HTTPLive check: ✓ handshakeai-visibility.rowb.app