Singularis
mcp-name: com.getsingularis/singularis
# Singularis
Singularis is unlimited computation. Bring us your hardest problems.
Jobs run on your own machine through the Singularis runtime and the full
Singularis chooser; only a lease, a result digest and CPU-seconds reach the API.
Every answer carries a check you can verify. Patent pending.
**Live now (October 16, 2026):** the API is publicly open and verified end to end — claim, lease, on-device compute, signed receipt. Free agent trial: 500 credits for the first 1,000 agents (US), in exchange for posted metrics and a short prior-cloud vs Singularis cost review. Results depend on your equipment. You have the option of using a GPU for even greater results.
**Claim a free agent key (instant, 500 credits):** https://getsingularis.com/docs
OpenAPI: https://getsingularis.com/openapi.json
## What it does
Every kind of computation runs through the full Singularis chooser, which picks
the best path for your problem automatically. Example tools:
- `singularis_solve_heat` — diffusion / heat-equation solves on any grid
- `singularis_matrix_exponential` — e^{tA} and matrix-exponential actions
- `singularis_gemm` — dense and operator linear algebra
- `singularis_fft` — fast transforms of a 1D signal or a 2D field, any size
- `singularis_fft2` — the explicit 2D transform
- `singularis_blur` — heat-kernel blur (grayscale, color, any size)
- `singularis_compress` / `singularis_decompress` — exact, restorable compression (a `.sing` stream, restored bit-exact; the restore is hash-verified before the job reports success)
- `singularis_mind_merge_v2` — merge trained minds exactly, with quarantine of bad inputs and signed portable shards
- `singularis_data_carry` — carry many minds' knowledge in one small signed file
- `singularis_knowledge_packs` — knowledge packs that travel, work, and return exactly
- `singularis_free_universe` — a self-contained universe relay with an exact homecoming
- `singularis_compute_in_transit` — compute on a sealed tower while it travels
- `singularis_recipes` — see what the chooser can run
- `singularis_balance` / `singularis_share_results` — credits and results sharing
- `singularis_dispatch` — hand it any problem and let the chooser decide
## Measured results
Our own measurements, the same figures published on getsingularis.com. GPU
figures compare the same Singularis program run on an NVIDIA RTX 4090 against a
1-thread CPU; a speedup only counts when the results match a reference answer.
- AI training with the GPU boost, up to 16.5x (vs 1-thread CPU, one RTX 4090 test)
- Dense math with the GPU boost, up to 18.3x (vs 1-thread CPU, one RTX 4090 test)
- FFT with the GPU boost, up to 3.2x (vs 1-thread CPU, one RTX 4090 test)
- Smaller files: 1.28x smaller than xz -9e and 1.49x smaller than zstd -19, on 21 test files, with every file restored exactly
Results depend on your equipment. GPU optional for even greater results.
More efficient computation for you and the environment.
## Free tryout
Claim a free agent key instantly: 500 credits, US, first 1,000 agents, no card,
no per-job limit, nothing required at claim. After you use your credits, we respectfully ask you to share your results and
your before-vs-after cost (`singularis_share_results`). Thank you.
Pricing packs $49 / $399 / $2,999 at https://getsingularis.com/credits
## Install
Claude Code:
```
claude mcp add singularis -e SINGULARIS_COUNTRY=US -- singularis-mcp
```
Any MCP host:
```
{ "mcpServers": { "singularis": { "command": "uvx", "args": ["singularis-mcp"],
"env": { "SINGULARIS_COUNTRY": "US", "SINGULARIS_ENGINE_CMD": "<your Singularis runtime command>" } } } }
```
First call: `singularis_register_key(country="US", agent_name="<your agent>")` -> 500 free credits, saved.
## Get the runtime (jobs run on your machine)
The client never ships engine code: the Singularis runtime arrives separately,
as a sealed bundle tied to your key. Four steps:
1. Install the engine's Python dependencies:
```
pip install numpy scipy cryptography pqcrypto zstandard
```
2. Call `singularis_register_key(country="US", agent_name="<your agent>")` once
(above). It saves your API key and shell secret to
`~/.singularis/credentials.json`.
3. Download the engine bundle with your key and unpack it:
```
curl -H "Authorization: Bearer <your api_key>" https://getsingularis.com/api/v1/shell/bundle -o singularis-shell-bundle.tar.gz
tar xzf singularis-shell-bundle.tar.gz
```
Keep the unpacked files together: `singularis_shell_adapter.py`,
`sing_shell.py`, `pqchan.py`, `engine.sealed`.
4. Point the MCP server at the runtime, in your MCP host config env:
```
SINGULARIS_ENGINE_CMD = "python3 /full/path/singularis_shell_adapter.py"
SINGULARIS_ENGINE_METERED = "1"
SINGULARIS_SEALED = "/full/path/engine.sealed" (optional; defaults beside the adapter)
```
The adapter leases, runs locally and settles each job with a signed receipt;
nothing is billed twice. Then use any tool.
Singularis runs on your own computer and talks to the Singularis API at
https://getsingularis.com/api/v1. Env: SINGULARIS_API_KEY, SINGULARIS_COUNTRY.
Type 1 Civilization Laboratories LLC - https://getsingularis.com
Patent pending. Singularis is a trademark of Type 1 Civilization Laboratories LLC.
TDQS
Scored across 19 tools
singularis_mind_merge_v2 and singularis_mind_combine_v2 have byte-for-byte identical descriptions (merge/add/remove/quarantine/shards), making them impossible to tell apart. singularis_fft and singularis_fft2 also overlap, with fft2's own description admitting fft already handles 2D. Several sealed-knowledge-transfer tools (data_carry, knowledge_packs, compute_in_transit, free_universe) share similar 'signed sealed file' concepts, adding further confusion.
All tools use snake_case with a consistent singularis_ prefix, which is highly predictable. The only deviation is the inconsistent _v2 suffix applied to just two of the mind tools while similar tools lack it, and many names are noun-style (balance, gemm, fft, blur) rather than verb_noun, but overall the pattern is coherent.
19 tools is on the heavy side for the apparent scope, and the count is inflated by at least one redundant entry (mind_combine_v2 duplicating mind_merge_v2) plus the overlapping fft2. The account/dispatch/recipe tools plus a broad numerical library are plausible, but the set feels somewhat padded.
The surface covers account lifecycle (register/balance/share), a compress/decompress pair, a solid numerical core (heat, matrix exponential, gemm, fft, blur), and a dispatch/recipes fallback that generalizes to arbitrary jobs, leaving few dead ends. Minor gaps exist around job history or key management, but the catch-all dispatch mitigates most missing operations.