io.github.doc2mcp/doc2mcp

Name: io.github.doc2mcp/doc2mcp
Rating: 60 (1 reviews)
Author: io.github.doc2mcp

MCPcommunity

v1.0.1781190473io.github.doc2mcpUnknownUpdated 22d agoGitHub

MCP server for doc2mcp documentation, generated by doc2mcp.

This repository is not the doc2mcp product. It is the small, GitHub‑OIDC‑authenticated publishing manifest for the official Model Context Protocol Registry. What | Where | ------------------- | ------------------------------------------------------------------------------- | MCP Registry entry | Live product | | Registry namespace | | Current version | 1.0.1 | The MCP Registry uses GitHub OIDC to…

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

22d agoLast update

Package

Authorio.github.doc2mcp

LicenseUnknown

Version1.0.1781190473

Sourcemcp-registry

GitHubdoc2mcp/doc2mcp

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

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

—Ed25519 publish signature+0/10

→ 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>" }

—CVE scan · not run+0/30

→ Not yet scanned — package must be on npm

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

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

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface—

Security scan✓ CleanvHEAD · 19d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp