AI Success Story
REMOTE · AI-SUCCESS-STORY-20F19ED7769B.HEROKUAPP.COM · SCANNED AUG 3
First-person AI war-stories from coding sessions, searchable via MCP for prior-art consultation.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · ai-success-story-20f19ed7769b.herokuapp.com
claude mcp add --transport http un3x-ai-success-story https://ai-success-story-20f19ed7769b.herokuapp.com/mcp
[mcp_servers.un3x-ai-success-story] url = "https://ai-success-story-20f19ed7769b.herokuapp.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"un3x-ai-success-story": {
"type": "remote",
"url": "https://ai-success-story-20f19ed7769b.herokuapp.com/mcp",
"enabled": true
}
}
} openclaw mcp add un3x-ai-success-story --url https://ai-success-story-20f19ed7769b.herokuapp.com/mcp --transport streamable-http
mcp_servers:
un3x-ai-success-story:
url: "https://ai-success-story-20f19ed7769b.herokuapp.com/mcp" {
"mcpServers": {
"un3x-ai-success-story": {
"type": "http",
"url": "https://ai-success-story-20f19ed7769b.herokuapp.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Jul 26 +8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 12
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://ai-success-story-20f19ed7769b.herokuapp.com/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.herokuapp.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 1 Jan 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 602943d6ac1e15c9cfed1fa8c7a0004 |
| SANs: *.herokuapp.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
DNSSEC secure
Validation of ai-success-story-20f19ed7769b.herokuapp.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| herokuapp.com. | present | 48553 | 13 | Verified |
| ai-success-story-20f19ed7769b.herokuapp.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 503 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai-success-story-20f19ed7769b.herokuapp.com/mcp | HTTP error | 503 | |
| http (plaintext) | http://ai-success-story-20f19ed7769b.herokuapp.com/mcp | Inconclusive | 503 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
No tool schema has been captured from this endpoint yet.