Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
OMISS MCP server. Net schedule, nets on the air, members, check-in history, awards.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"omiss": {
"command": "uvx",
"args": [
"omiss-mcp"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add omiss -- uvx omiss-mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"omiss": {
"command": "uvx",
"args": [
"omiss-mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"omiss": {
"type": "stdio",
"command": "uvx",
"args": [
"omiss-mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub qso-graph, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.4.1) llegó al registro hace 9 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, OpenTakeoff
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Construction takeoff for AI agents: load plans, set scale, measure, count, export with provenance.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
MCP server for OMISS, the Old Man International Sideband Society: the net schedule, OMISS nets on the air now, member lookup, past nets and who checked in, the Statehood schedule, officers, awards and net statistics, through any MCP-compatible AI assistant.
Data from omiss.net's public pages; nets on the air from NetLogger. Part of the qso-graph project. No login or API key needed.
uvx omiss-mcp # run it; nothing to install
| Tool | Description | Key Parameters |
|---|---|---|
omiss_net_schedule | Every net's band, UTC time, frequency, days, band coordinator and next run; holiday dates | — |
omiss_nets_on_air | OMISS nets on the air now, from NetLogger, each matched to the net schedule | — |
omiss_member_lookup | One member: OM number, call, name, status, grid, state, county, last check-in | callsign or om_number |
omiss_checkin_history | Past nets, newest first, optionally only a member's, a band's or a date's | callsign, om_number, band, date, net_control |
omiss_net_checkins | One past net: net control, relays, notes, and the check-in list | net_id |
omiss_statehood_schedule | 40m net dates and their free-call states, and the next one | — |
omiss_officers | Officers, band coordinators, committees, appointees, past presidents | — |
omiss_awards | The awards, with the IDs the other award tools take | — |
omiss_award_rules | An award's rules, or every award's summary | award_id |
omiss_award_recipients | Who holds an award, newest first, or check one member | award_id, callsign, om_number |
omiss_net_statistics | Nets per band, last net per band, top check-ins and net controls, last check-in by state | state, top |
omiss_eligibility | For a list of callsigns (a net's check-ins): member or not, OM number, silent key, and the military, first responder and state capital rosters | callsigns |
omiss_set_callsign | Save your callsign, for omiss_nets_on_air (asked once) | callsign |
get_version_info | Service version + upstream spec version (fleet identity attestation) | — |
OMISS is an amateur-radio society that runs SSB nets on HF, from 10 to 160 meters, every day of the week. Members exchange OM numbers on the nets and work toward the society's awards. Its website publishes the net schedule, the member roster, check-in history for every net, and the award rules and recipients.
Net control often opens a net in NetLogger for check-ins well before its listed time (the 40m net has opened 35 minutes early). omiss_net_schedule gives the listed times; omiss_nets_on_air shows whether a net is open now.
Only omiss_nets_on_air needs it: it asks NetLogger, which is told which station is asking. On first use the assistant asks for your callsign and saves it. You're asked once. The other tools don't need it.
omiss.net is a volunteer-run club website, not an API. We read it gently:
| Measure | Detail |
|---|---|
| One request at a time | At most one request every 2 seconds, shared by every copy you run (Claude Desktop, Claude Code, a script) through a locked file in your settings folder. |
| Response caching | Schedule, officers, Statehood, members and award recipients 24 hours; awards and rules 7 days; history and statistics 1 hour. |
| Stale answers over errors | When the site is down or busy, the last answer comes back with its age rather than an error. |
| Back-off | A "too many requests" or "unavailable" answer stops all requests for at least a minute, longer if the site asks. |
| Request timeout | 20-second timeout. |
| User-Agent header | Every request names this project, so the site's operators can see who is asking. |
| NetLogger | omiss_nets_on_air keeps to NetLogger's call limits, shared with netlogger-mcp if you run it too. |
YYYY, YYYY-MM or YYYY-MM-DD dates, numeric net IDs, and award IDs from the site's own list. Free text is never sent to omiss.net.omiss-mcp works with any MCP-compatible client. Add the server config and restart. The tools appear automatically.
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):
{
"mcpServers": { "omiss": { "command": "uvx", "args": ["omiss-mcp"] } } }
Add to .claude/settings.json:
{
"mcpServers": { "omiss": { "command": "uvx", "args": ["omiss-mcp"] } } }
{
"mcpServers": { "omiss": { "command": "uvx", "args": ["omiss-mcp"] } } }
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": { "omiss": { "command": "uvx", "args": ["omiss-mcp"] } } }
Add to .vscode/mcp.json in your workspace:
{
"servers": { "omiss": { "command": "uvx", "args": ["omiss-mcp"] } } }
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
{
"mcpServers": { "omiss": { "command": "uvx", "args": ["omiss-mcp"] } } }
"When is the OMISS 40m net, and on what frequency?"
"Is KI7MT an OMISS member? What's their OM number?"
"Which OMISS nets are on the air right now?"
"Which nets did OM 7212 check in to this year?"
"Who checked in to last night's 80m net?"
"What are the free-call states on the next 40m Statehood net?"
"What does the Alphabet Soup award require, and have I earned it?"
"Who ran the most OMISS nets as net control in the last 90 days?"
The same code works without an AI, with the same spacing and cache:
from omiss_mcp.omiss import OmissSource
om = OmissSource() me = om.member_lookup(callsign="KI7MT")"members" for net in om.checkin_history(om_number_=me["om_number"], date_="2026")["nets"]: print(net["time"], net["name"], net["checkin_count"])
Apps can name themselves, using ADIF's PROGRAMID and PROGRAMVERSION: OmissSource(program_id="MyLogger", program_version="1.0").
OMISS_MCP_MOCK=1 omiss-mcp
omiss-mcp --transport streamable-http --port 8015
git clone https://github.com/qso-graph/omiss-mcp.git
cd omiss-mcp uv sync --group dev uv run pytest
GPL-3.0-or-later