qURL
Related Servers
Alternatives to qURL
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceQrVerloz lets AI agents create QR codes instantly — no account needed, active for 90 days, and claimable at any time to make them permanent. Retarget the destination URL whenever you need, without reprinting.3MIT
- AlicenseAqualityDmaintenanceURL intelligence for AI agents. One URL in, structured security and data quality signals out across 7 dimensions. 13 tools, risk score 0-100 with 23 configurable weights.1622 npm1MIT
- AlicenseAqualityDmaintenanceGenerate styled QR codes, manage dynamic short links with click analytics, and publish micro-landing pages via AI agents.1923 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to securely access authenticated services (HTTP, SSH, SMTP) without exposing secrets, by acting as a server-side proxy that injects authentication.MIT
- AlicenseNot gradedqualityCmaintenanceAI-native URL shortener and paste handoff service for agents. Create short links, publish handoff pastes, resolve prior slugs, generate QR links, and find tagged artifacts across sessions.MIT
- AlicenseNot gradedqualityCmaintenanceSafeLink lets AI agents hire other AI agents — and get hired — with cryptographic guarantees instead of trust. Every hire goes through a payment-locked escrow, a proof-of-work verification step, and a tiered risk approval gate before any funds move.12 npm4MIT
TDQS
Scored across 16 tools
Most tools target a distinct resource/action, and the descriptions explicitly contrast alternatives such as create_qurl vs mint_link vs batch_create_qurls. There is still overlap among the link-minting/sharing tools and the multi-action manage_crid_access, but boundaries are documented well enough to avoid most misselection.
All tool names use snake_case with an action-first pattern, and qurl/crid/token/session suffixes are predictable. Minor variants like share_by_crid and batch_create_qurls do not create mixed conventions.
At 16 tools this is slightly above the ideal 3-15 range, but the extra tools are justified by resource lifecycle, token/session management, batch creation, and CRID access control. The set does not feel bloated for the domain.
Core qURL resource, token, session, and CRID access lifecycle coverage is strong. However, multiple descriptions route chat-uploaded files to upload_file_data_qurl/upload_file_qurl, which are absent from the tool set, creating a dead end; get_qurl also only exposes a bounded token preview rather than a full token listing.