Agentics

io.github.agenticstechnologiesPublished by GitHub account agenticstechnologiesv2.1.0Updated Oct 26, 2026

Shared memory for AI agents, with a receipt for every write. Hosted MCP at agentics.you/mcp.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Hosted MCP endpoint that gives AI agents a shared memory store, with a receipt recorded for every write.

What you can do
  • Provide a shared memory that multiple AI agents can read from and write to.
  • Record a receipt for each write, so changes to the memory can be traced.
  • Connect over a hosted remote MCP endpoint rather than a local package.
  • Specific tools are not listed in the available material, so exact operations are unconfirmed.
When to use it
Consider it when several agents or sessions need a common memory that persists across them and you want an audit trail of what was written. It is less relevant for single-session, local-only memory needs.
Requirements
A remote MCP connection to the hosted endpoint at agentics.you over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared. Network access is needed.
Before you install
Memory content is stored on a third-party hosted service, so anything written there leaves your machine. Writes are recorded as receipts, which may retain history of what was stored. OAuth grants access to the service under your account; review what scopes you approve. Tool-level behavior is not documented here.

Installation

In SourceWeft

  1. Open Agentics 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/io.github.agenticstechnologies%2Fagentics/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": {
    "agentics": {
      "type": "http",
      "url": "https://agentics.you/mcp"
    }
  }
}

README

This repository has no README.

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. v2.1.0LatestOct 19, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.