STEMPA

app.kragosPublished by kragos.appOfficial publisherv1.0.1Updated Oct 30, 2026

STEMPA seals one brief every AI reads the same way, with a signed receipt.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

STEMPA is a hosted MCP server that interviews you about a job, seals your answers into one versioned brief, and issues a signed receipt.

What you can do
  • Run a guided interview: the assistant lists what it already knows about a job, then asks only about the gaps, up to five questions at a time with suggested answers.
  • Record answers by accepting a suggestion, picking an option, or typing your own.
  • Freeze the brief once the gaps are closed, then seal it from your STEMPA account to get a fingerprint and a signed receipt.
  • Read sealed briefs back from any connected AI, so every assistant works from the same version.
When to use it
Useful when you want several AI assistants to work from one agreed, versioned scope instead of re-explaining a job each time, and when you need a shareable, verifiable record of what was agreed.
Requirements
A remote MCP endpoint added to a client that supports remote servers with OAuth; no local install or API key. Sign-in uses OAuth 2.1 with dynamic client registration and PKCE, and the first sign-in creates a free STEMPA account. The README names Claude, ChatGPT (Plus or higher) and Grok as supported clients.
Before you install
Sealing happens in your STEMPA account, not in the assistant, and the brief is frozen before sealing; changing a word creates a new version. Free plan limits apply after a 14-day Pro trial (5 sealed briefs a month, kept 30 days). Brief content is stored by the hosted service, and receipts can be shared with others for verification.

Installation

In SourceWeft

  1. Open STEMPA 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/app.kragos%2Fstempa/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": {
    "stempa": {
      "type": "http",
      "url": "https://stempa.kragos.app/mcp"
    }
  }
}

README

STEMPA

Brief your AI once. Seal it.

STEMPA is a remote MCP server. Your AI first lists what it already knows about a job, then asks you only about the gaps: up to five questions at a time, each with a suggested answer. You answer once, and STEMPA seals your answers into one brief with a signed receipt. Change a word and it becomes a new version.

Works with Claude, ChatGPT (Plus or higher) and Grok.

  • Server address: https://stempa.kragos.app/mcp
  • Transport: Streamable HTTP
  • Sign-in: OAuth 2.1 with dynamic client registration and PKCE. There is no key to paste.
  • Website: https://stempa.kragos.app
  • Official MCP Registry name: app.kragos/stempa (see server.json)

This repository is documentation only. STEMPA is a hosted service; there is nothing to install or run locally.

Connect

STEMPA works with Claude, ChatGPT (Plus or higher) and Grok; step-by-step instructions for each are in CONNECT.md. In short: paste https://stempa.kragos.app/mcp into your AI's connectors, and sign in to STEMPA when asked.

Any other MCP client that supports remote servers with OAuth connects the same way: add a remote server with the address https://stempa.kragos.app/mcp. The client finds the sign-in itself; there is no key to paste. In a client that reads an mcp.json file, the entry looks like this:

json
{  "servers": {    "stempa": {      "type": "http",      "url": "https://stempa.kragos.app/mcp"    }  }}

The first sign-in creates a free STEMPA account.

Use it

  1. Say to your AI: "Grill me on [your idea]."
  2. Your AI lists what it already knows, then asks only about the gaps: up to five questions at a time, each with a suggested answer. Accept the suggestion, pick an option, or type your own.
  3. When the gaps are closed, your AI freezes the brief.
  4. Open your account at https://stempa.kragos.app and press Seal. The brief gets a fingerprint and a signed receipt.
  5. Later, in any AI you connect, ask it to read your sealed brief. It reads the same sealed version.

Tools

grill_start, grill_map, grill_gaps, grill_answer, grill_freeze, and tools that read your briefs back.

How a brief is sealed

  1. Connect. Add STEMPA to the AI you already use.
  2. Answer. Your AI lists what it already knows, then asks only about the gaps. Pick an option, accept the suggestion, or type your own.
  3. Seal. Your AI freezes the brief; you seal it with one press in your STEMPA account. The sealed brief gets a fingerprint and a receipt with post-quantum signatures. Anyone you share a receipt with can check it on the receipt page.

A sealed brief is a record of the scope you agreed.

Plans

Start free: 14 days of Pro, then Free: 5 sealed briefs a month, kept 30 days. No card. Current plans are on https://stempa.kragos.app.

Support

Use the contact details on https://stempa.kragos.app. STEMPA is supplied by KRAGOS, South Africa.

Source: README.md at commit d426133

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

2
  1. v1.0.1LatestOct 23, 2026
  2. v1.0.0Oct 18, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.