Casa

io.github.tony8713Published by GitHub account tony8713v0.1.0Updated Oct 24, 2026

Private, permanent encrypted storage for AI agents. Paid per call in USDC via x402.

VerifiedStreamable HTTPWeb executableFiles & StorageFinance

Overview

AI-generated overview

Casa provides AI agents with private, permanent encrypted storage, paid per call in USDC via x402.

What you can do
Casa is a remote MCP endpoint that offers private, permanent encrypted storage for AI agents. According to the registry description, access is metered and paid per call in USDC through the x402 payment protocol. No tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs durable, encrypted storage that persists across sessions and you are willing to pay per call in USDC. It is less suitable if you need free storage, documented tool names, or a self-hosted local process.
Requirements
A remote MCP client that can reach the streamable HTTP endpoint at casa-agents.fly.dev. No authentication, environment variables, or headers are declared. A funded USDC wallet compatible with x402 is implied by the per-call payment model.
Before you install
The service charges per call in USDC, so usage can spend real funds; set spending limits and monitor calls. It is a third-party remote endpoint, so stored data leaves your machine and its confidentiality depends on the provider. No authentication is declared, which may affect access control.

Installation

In SourceWeft

  1. Open Casa in the dashboard and add it to a workspace.
  2. 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/io.github.tony8713%2Fcasa/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.

{
  "mcpServers": {
    "casa": {
      "type": "http",
      "url": "https://casa-agents.fly.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

3

echo

Echo

Echoes the provided text back to the caller.

Parameterstextrequired

add

Add

Adds two numbers and returns the sum.

Parametersarequiredbrequired

server_time

Server time

Returns the current server time (ISO 8601, UTC).

Takes no parameters.

Version history

1
  1. v0.1.0LatestSep 16, 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.