An agent can connect after a one-time OAuth consent by a human.Remote endpoint behind OAuth 2. Tokens stay with the agent; the registry only exposes the authorization metadata.
Placeholders to fill from your own secret store: ${JUSTTRANSCRIBE_MCP_TOKEN}. The registry never accepts secret values.
Quality 100 / 100strong
protocoln/a · weight 25
n/a
protocol.modern, protocol.stateless, protocol.transport, protocol.list_ttlno remote answered a protocol handshake (not probed yet, unreachable, or local-only)
authorization100 · weight 15
pass
auth.prmProtected Resource Metadata (RFC 9728) published
pass
auth.as_metadataauthorization server metadata reachable
pass
auth.cimdClient ID Metadata Documents supported
n/a
auth.secret_in_urlno templated URL
tool hygienen/a · weight 30
n/a
tools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)
stabilityn/a · weight 15
n/a
stability.changes, stability.rug_pulltool list unknown
dependencies100 · weight 15
pass
deps.known_vulnsno known advisory in 1 resolved packages
n/a
deps.mcp_sdk_versionthe official MCP SDK is not in the dependency graph
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
Endpoints
remote
auth
reachable
uptime 30d
p50
protocol
last ok
https://justtranscribe.ai/api/mcpstreamable-http
oauth2 AS: https://justtranscribe.ai
yes
97%
880 ms
–
2026-10-20
package
registry
version
runtime
secrets
justtranscribe-mcp
npm
0.1.1
–
JUSTTRANSCRIBE_API_KEY
Tools (0)
No tools observed. Tools appear once a credential-free probe can list them.