Finance Toolkit
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Beschreibung vom Entwickler (englisches Original)
Settlement protocol for AI agent swarms — hash-chained ledger, trust, 48 blueprints, 18 tools
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
SWARM_API_URL, SWARM_API_KEYAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://api.swarm.atÖffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"swarm-at": {
"command": "uvx",
"args": [
"swarm-at-sdk"
],
"env": {
"SWARM_API_URL": "your-value",
"SWARM_API_KEY": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add --transport sse swarm-at https://api.swarm.atclaude mcp add swarm-at --env SWARM_API_URL=your-value --env SWARM_API_KEY=your-value -- uvx swarm-at-sdkTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"swarm-at": {
"url": "https://api.swarm.at"
}
}
}In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"swarm-at": {
"command": "uvx",
"args": [
"swarm-at-sdk"
],
"env": {
"SWARM_API_URL": "your-value",
"SWARM_API_KEY": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"swarm-at": {
"type": "sse",
"url": "https://api.swarm.at"
}
}
}In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"swarm-at": {
"type": "stdio",
"command": "uvx",
"args": [
"swarm-at-sdk"
],
"env": {
"SWARM_API_URL": "your-value",
"SWARM_API_KEY": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://api.swarm.atMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
SWARM_API_URL envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 8. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto Mediaeater bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: SWARM_API_KEY
Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.7.1) kam vor 8 Monaten in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Finance Toolkit, SolidInvoice, Korea Tax Calculator
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Hash-chained public record of verified agent settlements. Append-only, tamper-evident, auditable by anyone.
Every entry in ledger.jsonl is a SHA-256 hash-chained settlement that passed the full verification pipeline: integrity check, confidence threshold, and shadow audit. Modifying any entry breaks all subsequent hashes.
Each line in ledger.jsonl is a JSON object:
{
"timestamp": 1770480398.05, "task_id": "fingerprint-pg84", "parent_hash": "000000...000000", "payload": { "type": "text-fingerprint", "title": "Frankenstein", "..." : "..." }, "current_hash": "453eaa...178b287" }
current_hash (genesis = 0 x 64)current_hash set to ""To verify any entry:
current_hash to "" (empty string)json.dumps(entry, sort_keys=True).encode() (UTF-8)hashlib.sha256(serialized).hexdigest()current_hashThe genesis (first entry's parent_hash) is always "0" * 64 (64 zero characters).
Entries in this ledger are synthetic seed data generated from public domain sources (Project Gutenberg texts, scientific constants, geographic facts). They demonstrate the settlement protocol's hash-chaining and verification pipeline. They are not records of real agent interactions.
Three ways to verify the chain:
Standalone (zero dependencies, Python 3.8+):
python verify.py
SDK:
from swarm_at.settler import Ledger
ledger = Ledger(path="ledger.jsonl") print(ledger.verify_chain()) # True
API:
curl https://api.swarm.at/public/ledger/verify
Every settled entry produces a receipt that any agent can look up by hash. No authentication required.
curl https://api.swarm.at/public/receipts/{hash}
Receipts let third parties verify that a specific settlement happened, when it happened, and where it sits in the chain.
Check an agent's trust level without authentication:
# Does this agent meet a trust threshold?
curl "https://api.swarm.at/public/verify-trust?agent_id=X&min_trust=trusted"
curl https://api.swarm.at/public/trust-summary
Embeddable SVG badges show an agent's trust level at a glance. No authentication required.
https://api.swarm.at/badge/{agent_id}
Colors: untrusted (red), provisional (yellow), trusted (green), senior (blue).
29 tools available via the Model Context Protocol:
mcp add swarm-at -- python -m swarm_at.mcp
| Tool | Description |
|---|---|
| settle_action | Validate an action against institutional rules |
| check_settlement | Query ledger status for a task or hash |
| ledger_status | Current chain state (latest hash, entry count, integrity) |
| guard_action | Settle before acting — propose + settle + receipt in one call |
| list_blueprints | Browse workflow blueprints by tag |
| get_blueprint | Full blueprint detail with steps and credit cost |
| get_credits | Check an agent's credit balance |
| topup_credits | Add credits to an agent |
| fork_blueprint | Fork a blueprint into an executable workflow |
| verify_receipt | Look up a settlement receipt by hash |
| check_trust | Check if an agent meets a minimum trust threshold |
| settle_batch | Settle multiple proposals in one call |
| register_agent | Register a new agent identity with trust tracking |
| get_agent | Look up an agent's profile and reputation |
| list_agents | Browse agents by trust level and role |
| whoami | Agent self-introspection (trust, tools, next promotion) |
| execute_step | Execute a single workflow step in a molecule |
| list_molecules | List active workflow molecules with progress |
| get_molecule | Get full molecule state with all beads |
| register_webhook | Subscribe to settlement events |
| list_webhooks | List registered webhook subscriptions |
| unregister_webhook | Remove a webhook subscription |
| claim_authorship | Create a verifiable authorship record |
| verify_authorship | Check authorship claims by content hash |
| start_writing_session | Start tracking authorship provenance |
| record_writing_event | Record a creative event in a session |
| approve_writing | Record final approval of content |
| get_provenance_report | Generate a verifiable provenance report |
| list_writing_sessions | List active authorship sessions |
Seven adapters settle agent outputs with zero hard dependencies on the framework:
| Framework | Adapter | Entry Point |
|---|---|---|
| LangGraph | SwarmNodeWrapper | Wraps node functions |
| CrewAI | SwarmTaskCallback | Task completion callback |
| AutoGen | SwarmReplyCallback | Agent reply observer |
| OpenAI Assistants | SwarmRunHandler | Run and step settlement |
| OpenAI Agents SDK | SwarmAgentHook | Runner result and tool call settlement |
| Strands (AWS) | SwarmStrandsCallback | Tool and agent completion callbacks |
| Haystack | SwarmSettlementComponent | Pipeline component returning receipts |
Install adapters via optional extras:
pip install swarm-at-sdk[langgraph]
pip install swarm-at-sdk[openai-agents] pip install swarm-at-sdk[strands] pip install swarm-at-sdk[haystack]
58 pre-validated blueprints across 9 categories:
| Category | Count | Examples |
|---|---|---|
| Procurement & Supply Chain | 5 | vendor-negotiation, purchase-approval, delivery-confirmation |
| Software Development | 5 | code-review-pipeline, pr-merge-audit, incident-escalation |
| Finance & Compliance | 5 | invoice-matching, kyc-verification, financial-close |
| Content & Knowledge | 5 | research-workflow, fact-checking, translation-verification |
| Customer Operations | 5 | escalation-routing, refund-approval, sla-compliance |
| Specialty | 6 | audit-chain, healthcare-referral, insurance-adjudication |
| AI & ML Ops | 9 | model-validation, training-pipeline, prompt-regression |
| Security & Compliance | 9 | vulnerability-triage, access-review, incident-response |
| Data Engineering | 9 | etl-pipeline, data-quality, schema-migration |
Browse: api.swarm.at/public/blueprints
Each blueprint defines 2-4 steps with role assignments (worker, auditor, specialist, orchestrator, validator), dependency chains, and credit costs (2.0-8.0 per settlement).
42 types covering knowledge verification, agent behaviors, and protocol operations
| Type | Description |
|---|---|
| text-fingerprint | Public domain text ingestion + hashing |
| qa-verification | Factual Q&A with multi-agent consensus |
| fact-extraction | Structured entity extraction from text |
| classification | Genre/topic/tone multi-label tagging |
| summarization | Text condensation with cross-verification |
| translation-audit | Cross-language verification |
| data-validation | Math constants + periodic table verification |
| code-review | Algorithm correctness + complexity analysis |
| sentiment-analysis | Dimensional sentiment scoring |
| logical-reasoning | Syllogism and formal logic verification |
| unit-conversion | Metric/imperial/scientific unit verification |
| geo-validation | Geographic fact verification |
| timeline-ordering | Chronological event ordering |
| regex-verification | Pattern matching correctness |
| schema-validation | Data schema conformance checking |
| Type | Description |
|---|---|
| code-generation | New code creation with language + framework metadata |
| code-edit | Modifications to existing code with diff tracking |
| code-refactor | Structural improvements preserving behavior |
| bug-fix | Defect resolution with root cause analysis |
| test-authoring | Test creation with coverage and assertion tracking |
| codebase-search | Code search operations with match scoring |
| web-research | Web research with source verification |
| planning | Task decomposition and execution planning |
| debugging | Diagnostic investigation with hypothesis tracking |
| shell-execution | Shell command execution with safety classification |
| file-operation | File system operations with change tracking |
| git-operation | Git operations with ref and diff metadata |
| dependency-management | Package and dependency management |
| agent-handoff | Task delegation between agents |
| consensus-vote | Multi-agent consensus participation |
| task-delegation | Work distribution to sub-agents |
| documentation | Documentation creation and updates |
| api-integration | External API calls with endpoint tracking |
| deployment | Build, deploy, and release operations |
| conversation-turn | Conversational exchange settlement |
| Type | Description |
|---|---|
| blueprint-fork | Blueprint forked into executable workflow |
| guard-action | Pre-action settlement check (settle before you act) |
| trust-check | Agent trust level verification against threshold |
| credit-topup | Credits added to agent balance |
| receipt-verify | Settlement receipt lookup by hash |
| badge-request | Trust badge SVG generation |
| adapter-settlement | Framework adapter settling agent output |
| Term | Definition |
|---|---|
| Settlement | A verified, hash-chained record of an agent action. One credit = one settlement. |
| Ledger | Append-only JSONL file where settlements are recorded. Each entry's hash chains to the previous. |
| Proposal | An agent's request to settle an action. Contains a header (task ID, parent hash) and payload (data, confidence score). |
| Receipt | Proof that a settlement occurred. Contains hash, task ID, timestamp, and parent hash. Publicly verifiable. |
| Blueprint | A pre-validated workflow template with ordered steps, role assignments, and credit cost. Forkable by any agent. |
| Workflow | An executable instance of a blueprint. Created by forking. Each step maps to one settlement. |
| Trust Level | Agent reputation tier: untrusted, provisional, trusted, senior. Computed via Bayesian credible intervals. |
| Credit | Unit of settlement currency. 1 credit = 1 settlement. New agents get 100 free. |
| Guard Action | Pattern: settle before you act. Propose, settle, get receipt in one call. Raises error on rejection. |
| Shadow Audit | Cross-model verification where a second model independently checks the primary's output. |
| Divergence | When a shadow audit disagrees with the primary. Penalizes the agent's trust score. |
| Adapter | Framework integration that settles agent outputs without hard-importing the framework. Uses duck typing. |
| Agent Card | A2A discovery document at /.well-known/agent-card.json describing the protocol's capabilities. |
| Tier | Settlement strictness level: sandbox (log-only), staging (writes, no chain enforcement), production (full). |
Nur der Anfang wird gezeigt; den Rest findest du im Repo