Specita

com.specitaPublished by specita.comOfficial publisherv1.0.0Updated Oct 26, 2026

Read-only release evidence for coding agents: findings, deliveries, source and runtime data.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Specita is a remote, read-only MCP endpoint that gives coding agents release evidence: findings, deliveries, and source and runtime data.

What you can do
  • Retrieve release evidence for a codebase, including findings raised about a release.
  • Look up deliveries and their associated release information.
  • Read source and runtime data tied to a release.
  • All access is read-only, so the assistant inspects evidence rather than changing anything.
When to use it
Useful when a coding agent needs to check what was found or delivered for a release before making changes, or when you want release context available to an assistant without giving it write access.
Requirements
A remote MCP endpoint at the provider's API host, reached over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared. Network access to the provider is needed.
Before you install
Access is granted through OAuth, so the assistant receives whatever scope the authorization grants; review the consent screen and granted scopes. The server is described as read-only, but confirm that before relying on it. Release evidence and source data are sent to the provider's service.

Installation

In SourceWeft

  1. Open Specita in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.specita%2Frelease-evidence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "specita": {
      "type": "http",
      "url": "https://api.specita.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 20, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.