transcribe-mcp

Name: transcribe-mcp
Author: io.github.Soboljem

MCPcommunity

v0.1.1io.github.SoboljemUnknownUpdated 2mo agonpm GitHub

Transcribe audio/video and find dead air. Pay-per-call in USDC over x402 — no account, no key.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

2mo agoLast update

Package

Authorio.github.Soboljem

LicenseUnknown

Version0.1.1

Sourcenpm+mcp-registry

npmtranscribe-mcp

GitHubSoboljem/transcribe-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface3 tools · none privileged

Security scan✓ Cleanv0.1.2 · 1mo agoHow well does this scan work?

EvalsNone

IndexedAug 19, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

3 tools · none privileged

Statically extracted from the published packagev0.1.2 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

transcribe_urlTurn a publicly reachable audio or video URL into text with per-segment timings and a

Turn a publicly reachable audio or video URL into text with per-segment timings and a

No input schema was published for this tool.

find_dead_airGiven subtitles or timings, return the spans of dead air and how much of the runtime

Given subtitles or timings, return the spans of dead air and how much of the runtime

No input schema was published for this tool.

shop_infoFree. Returns the prices, the size limit, the chain and how payment works, so an agent

Free. Returns the prices, the size limit, the chain and how payment works, so an agent

No input schema was published for this tool.

3 of 3 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Transcribe audio/video and find dead air. Pay-per-call in USDC over x402 — no account, no key.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-01 — observed resolution, not a publisher declaration.

60 packages resolved · 5 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

viem2.56.18 dependencies
- ox0.14.34+4 not drawn4 dependencies
  - @scure/bip321.7.0+2 not drawn1 dependency
    @noble/hashes1.8.0
  - @scure/bip391.6.0+1 not drawn1 dependency
    @noble/hashes1.8.0shown above
  - @noble/curves1.9.11 dependency
    @noble/hashes1.8.0shown above
  - @noble/hashes1.8.0shown above
- ws8.21.0
- isows1.0.7
- abitype1.2.3
- @scure/bip321.7.0shown above+2 not drawn
- @scure/bip391.6.0shown above+1 not drawn
- @noble/curves1.9.1shown above
- @noble/hashes1.8.0shown above
@x402/evm2.20.03 dependencies
- zod3.25.76
- viem2.56.1shown above
- @x402/core2.20.01 dependency
  - zod3.25.76shown above
@x402/core2.20.0shown above
@x402/fetch2.24.01 dependency
- @x402/core2.24.01 dependency
  - zod3.25.76shown above
@modelcontextprotocol/sdk1.30.0+8 not drawn9 dependencies
- ajv8.20.0+4 not drawn
- zod4.5.4
- cors2.8.6+2 not drawn
- hono4.13.5
- jose6.2.10
- express5.2.1incomplete+19 not drawn
- raw-body3.0.2incomplete
- ajv-formats3.0.1incomplete
- cross-spawn7.0.6incomplete

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

51 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 51

body-parser ^2.2.1 — required by express@5.2.1package cap reached
escape-html ^1.0.3 — required by express@5.2.1package cap reached
http-errors ^2.0.0 — required by express@5.2.1package cap reached
on-finished ^2.4.1 — required by express@5.2.1package cap reached
content-type ^1.0.5 — required by express@5.2.1package cap reached
finalhandler ^2.1.0 — required by express@5.2.1package cap reached
range-parser ^1.2.1 — required by express@5.2.1package cap reached
serve-static ^2.2.0 — required by express@5.2.1package cap reached
cookie-signature ^1.2.1 — required by express@5.2.1package cap reached
merge-descriptors ^2.0.0 — required by express@5.2.1package cap reached
content-disposition ^1.0.0 — required by express@5.2.1package cap reached
bytes ~3.1.2 — required by raw-body@3.0.2package cap reached

+39 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

transcribe-mcp

Tools

Tools exposed

Dependency tree

Declared but not resolved