Developer · Remote MCP server
qrvote
QR-code contests, surveys, quizzes and scavenger hunts: read results, manage your own.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
org.qrvote/qrvote- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- org.qrvote
- Namespace
- Namespace verified by the MCP Registry via the domain qrvote.org · how
- Website
- mcp.qrvote.org/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.qrvote.org/mcp/organizer | None |
| Streamable HTTP | https://mcp.qrvote.org/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://mcp.qrvote.org/mcp/organizer(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://mcp.qrvote.org/mcp(HTTP)- Reachable
- Yes (HTTP 200)
- Handshake
- qrvote 1.0.0 · protocol 2025-06-18
- Tools discovered
15 - show names
draft_contest,create_contest,set_entry_photo,get_campaign,get_results,get_dashboard,update_settings,add_judge,remove_judge,add_entries,export_csv,list_responses,host_step,set_questions,set_answer_key- Checked on
- 2026-10-05
How to connect qrvote
qrvote is a remote MCP server: there is nothing to install. Its endpoints are https://mcp.qrvote.org/mcp/organizer and https://mcp.qrvote.org/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Qnexus MCPMCP server for Quantinuum Nexus, wrapping the qnexus SDK. Not affiliated with Quantinuum. | Local · stdio |
| Qodercli MCPMCP server mode for Qoder CLI - delegate coding tasks to local Qoder agents from any MCP client. | Local · stdio |
| Qovery MCP ServerDeploy apps and manage Kubernetes on AWS, GCP, Azure, and On-Premise with natural language. | Remote · HTTP |
| QR for AgentDynamic QR codes for AI agents - custom styling, scan tracking, webhooks. | Local · stdio |
| Qsp ClientQSP - relay MCP tools to any OpenAI-compatible local LLM (llama.cpp, Ollama, vLLM) | Local · stdio |
| QTM4JMCP server for QMetry Test Management for Jira (QTM4J) Open API. | Local · stdio |
| Qtm4j MCP ServerMCP server for QMetry Test Management for Jira (QTM4J): test cases, cycles, executions, plans. | Local · stdio |
| QuadraticAI access to Quadratic spreadsheets: open files, run Python/SQL, query connected databases. | Remote · HTTPLive check: ✓ handshake |