autoxingtech MCP server
online · 100% uptimeMCP server for autoxingtech documentation, generated by doc2mcp.
2 stars
Reviews
Write oneNobody has reviewed autoxingtech yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
autoxingtech tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1367ms; handshake note: Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32003,"message":"Unauthori20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 114 days ago8/15
- Maintainer identityregistry namespace matches repository owner6/10
How autoxingtech compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 70/100
- higher than 35% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 278 ms
- faster than 51% of 30,031 servers
- GitHub stars
- 2
- more than 75% of 28,688 servers
Install autoxingtech in Claude Code, Cursor or VS Code
claude mcp add --transport http autoxingtech https://www.doc2mcp.site/api/mcp/0ddc91d1-3136-4c4a-8627-1a0be89c0ec7/mcp
What the publisher says
From the autoxingtech repository's README, as published. We do not edit it. Read it on GitHub
doc2mcp
Paste docs → get a hosted MCP server for Cursor, Claude & VS Code
Turn any documentation URL into a live Model Context Protocol server in under 60 seconds.
Try it free · Docs · Marketplace · Pricing
⭐ Star this repo — it helps developers discover doc2mcp on GitHub and the MCP Registry.
What is this repo?
This is the public face of doc2mcp on GitHub:
The live product runs at doc2mcp.site. Source code stays private so the platform cannot be copied.
How it works
- Sign in at doc2mcp.site/login
- Paste a docs URL (Stripe, LangChain, your own Mintlify site, OpenAPI, GitHub repo…)
- Get a hosted MCP URL + Bearer token
- Paste into Cursor / Claude / VS Code mcp.json
- Every MCP you create is auto-listed on the official MCP Registry as io.github.doc2mcp/
{
"mcpServers": {
"my-docs": {
"url": "https://doc2mcp.site/api/mcp/{project_id}/mcp",
"headers": { "Authorization": "Bearer <your-token>" }
}
}
}CLI
npm install -g doc2mcp
doc2mcp login
doc2mcp https://docs.example.comMCP Registry
- Registry search:
- Marketplace:
Gateway manifest (server.json)
This repo publishes the canonical platform record via GitHub OIDC when you push a v* tag:
git tag v1.0.2
git push origin v1.0.2Workflow: .github/workflows/publish-mcp.yml
Why a separate public repo?
The MCP Registry grants namespace io.github.doc2mcp/ only to workflows running inside the doc2mcp** GitHub org. This small public repo holds the OIDC publish manifest — not the product source.
Links
- 🌐 Product:
- 📦 npm CLI:
- 📋 MCP Registry:
- 🏆 Product Hunt:
- ✉️ Contact: doc2mcp@gmail.com
License
The server.json manifest in this repo is MIT. The doc2mcp product code is proprietary and not distributed in this repository.
Nothing above is checked by us. What we check is on the safety report.
autoxingtech: common questions
- Is autoxingtech MCP server safe?
- Mostly: it is graded B (70/100). Read the autoxingtech safety report
- How do I install autoxingtech?
- It runs remotely at www.doc2mcp.site. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does autoxingtech need an API key?
- Yes. The registry entry asks for
Authorization. - Is autoxingtech maintained?
- The last commit was 119 days ago (2026-07-08). The latest release is v1.0.1787738943.
- Is autoxingtech up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does autoxingtech compare with other MCP servers?
- safety score 70/100 (higher than 35% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 278 ms (faster than 51% of 30,031 servers). Full comparison.