Razi Tools
warningswww.razi.pro
PDF, image, video, OCR, screenshot, SQL, QR and text tools for agents. No API key, no signup.
https://www.razi.pro/api/mcpWebsiteUnknownMCP 2025-06-18v2.1.1last checked 23 Oct 2026spoke MCP on 100% of 85 checks (30 days)initialize in 165 msLast checked 23 Oct 2026
- ✓Answered the MCP handshake (MCP 2025-06-18)
- –Auth scheme could not be determined
- ✓Lists 28 tools
- !1 warning
- ✓Spoke MCP on 85 of 85 checks (30 days)
Will my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
–Claude CodeUnknown
The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.
Claude Code docs · read on 2026-08-30
–Claude (claude.ai & Desktop)Unknown
The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
–ChatGPTUnknown
The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.
ChatGPT docs · read on 2026-08-30
–CursorUnknown
The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.
Cursor docs · read on 2026-08-30
–VS Code (Copilot)Unknown
The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.
VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 23 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | Unknown |
|---|---|
| Protected-resource metadata | ✕Not found Without it a client has to guess where the authorization server lives. |
| Anonymous access | Refused — credentials required |
What the probe found
It speaks JSON-RPC but rejected the handshake: "Client identifier blocked by security policy"
Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.
Tools
Contract history
Breaking: compress_video, upload_file
Instructions rewritten: calculate_percentage, compare_text, compress_image, compress_pdf, decode_base64, decode_jwt, decode_url, draft_email, encode_base64, encode_url, extract_text_ocr, fetch_page_metadata, fetch_site_logo, format_json, generate_blog_outline, generate_fake_data, generate_image, generate_qr_code, generate_sql, generate_text, humanize_text, merge_pdf, parse_document, screenshot_url, shorten_url, split_image, split_pdf. The description an agent follows changed; the callable contract may not have.
Watch this server
Save its public contract as a baseline and manage breaking-change email alerts.
Set up a watchRoute it through the gateway
Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.
Add to my gatewayOwn this server?
Sign in to claim this listing by proving control of its host.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/razi-tools)