io.github.jyswee/authshore
REMOTE · MCP.AUTHSHORE.AI · 2 COMPONENTS · SCANNED AUG 3
Auth infrastructure for coding agents. User pools, secrets vault, token management. As easy as git.
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 Security57
- 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 call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 148 tokens (~74/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · mcp.authshore.ai
claude mcp add --transport http jyswee-authshore https://mcp.authshore.ai/sse
[mcp_servers.jyswee-authshore] url = "https://mcp.authshore.ai/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jyswee-authshore": {
"type": "remote",
"url": "https://mcp.authshore.ai/sse",
"enabled": true
}
}
} openclaw mcp add jyswee-authshore --url https://mcp.authshore.ai/sse --transport streamable-http
mcp_servers:
jyswee-authshore:
url: "https://mcp.authshore.ai/sse" {
"mcpServers": {
"jyswee-authshore": {
"type": "http",
"url": "https://mcp.authshore.ai/sse"
}
}
} 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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Jul 26 56
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://mcp.authshore.ai/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=authshore.ai | CN=YR1,O=Let's Encrypt,C=US | 7 Jun 2026 | 5 Sept 2026 | RSA 4096 | SHA256-RSA | 518cd616aecc9e83ab8a66e142a7857c6d3 |
| SANs: *.authshore.ai, authshore.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of mcp.authshore.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| authshore.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 | 404 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.authshore.ai/sse | Verified | 200 | |
| http (plaintext) | http://mcp.authshore.ai/sse | HTTPS enforced | 301 | https://mcp.authshore.ai/sse |
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.
authshore_get_started ~33
Explains what AuthShore is and how to activate this MCP server (no API key on this session yet).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
authshore_signup ~115
Create a new AuthShore project. Returns an API key (shown once), active immediately on the Free plan — no card required. Unlocks all AuthShore tools in this session. Optionally pass the human's email to send a 7-day-trial invitation for paid plans.
| Name | Type | Req | Description |
|---|---|---|---|
| string | — | Human email (optional) — receives the paid-plan trial invitation | |
| name | string | — | Project display name (optional) |
| slug | string | yes | Short project slug, e.g. "my-app" |
No output schema declared.
No examples provided.