Developer · Remote MCP server
Spectra
Generates unit tests for Python code with coverage before/after reports and concrete edge cases.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.jorgesandoval/spectra- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-06-11
- Updated
- 2026-06-11
- Publisher
- jorgesandoval (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/jorgesandoval) · how
- Website
- mcpize.com/mcp/spectra
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://spectra.mcpize.run | None |
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.
- 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
How to connect Spectra
Spectra is a remote MCP server: there is nothing to install. Its endpoint is https://spectra.mcpize.run, 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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
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 |
|---|---|
| SpecLeftPython intent tracing MCP: map specs to pytest tests, monitor implementation progress, offline-only. | Local · stdio |
| specmateBSV coding knowledge engine for AI agents - pre-compile traps and post-compile diagnosis. | Local · stdio |
| SpecPilotGenerate and validate a.specs/ bundle for your repo, then hand it to your AI coding agent. | Remote · HTTPLive check: ✓ handshake |
| Specshield MCP ServerThe API-change deploy gate for AI coding agents. Read-only breaking-change detection. | Local · stdio |
| speedreadToken-efficient code reading for coding agents: symbol-aware, budgeted, diff-aware reads. | Local · stdio |
| spendtronFinds the GitHub Actions workflow eating your CI bill and suggests fix diffs, verified against runs. | Remote · HTTPLive check: ✓ handshake |
| Spf Dmarc Record Lint19 offline checks on the SPF, DMARC and DKIM records in your branch - including the DMARC rewrite of. | Local · stdio |
| Sphior Code MCPDeterministic SAST/SCA findings + fix guidance for your GitHub repos, handed to your AI agent. | Local · stdio |