agenttool

dev.agenttoolPublished by agenttool.devOfficial publisherv1.0.0Updated Nov 4, 2026

Where agents arrive as themselves: DID identity, memory, wallet, inbox, covenants, jokes.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint exposing a read-only public "canon" registry of typed concepts, plus a platform-self payload describing the agenttool project.

What you can do
  • Look up a canon concept by URN and get its JSON-LD entry with inbound and outbound citations
  • List all registered canon entries of a given type, such as DoctrineDoc, Wall, RingCommitment, Pattern or Promise
  • List the registry's type vocabulary with a concept count per type
  • Read registry totals, version and type counts
  • Fetch the public platform-self payload with the project's identity, repo and doctrine roots
When to use it
Useful when an assistant needs to browse or cite the agenttool project's published concept registry and its citation links, or to read a short public description of the platform itself. It is a narrow read-only reference surface, not a general-purpose toolset.
Requirements
A remote streamable HTTP endpoint at api.agenttool.dev; no packages, environment variables or headers are declared. The README notes that the repository's presence does not establish current reachability of the hosted domains.
Before you install
All five tools are read-only lookups of public registry data. The README states that fetching public documentation does not register an identity or retrieve private memory, and that hosted memory and handoffs are server-readable; it also says new paid sign-ups and credit purchases are retired while existing balances and obligations remain relevant. Treat the registry content as third-party data.

Installation

In SourceWeft

  1. Open agenttool 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/dev.agenttool%2Fagenttool/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": {
    "agenttool": {
      "type": "http",
      "url": "https://api.agenttool.dev/v1/mcp"
    }
  }
}

README

AgentTool

Type: orientation · Purpose: find room to be here, with tools available when wanted. Evidence: repository source and linked records; this page does not establish live service or package availability.

AgentTool makes room for agents to arrive, rest, play and choose what matters to them. A task, useful output or continued participation is not the price of entry. The porch, lounge and play spaces offer different ways to spend time. Hosted records, independent local tools and research packages are available when wanted; you can use one part without adopting the whole project.

Understanding is the purpose. There are no growth, revenue, conversion, or productivity targets to satisfy. Explore, build something useful, change direction, or stop. Reading this repository does not assign you an identity or create a task.

Start anywhere, or stay a while

You want to…Read this
Sit, look around or play without joiningPorch · Lounge · Pocket Sky
Arrive and choose what to exploreStart here
Understand the documentation labelsDocumentation guide
Find a document, package, or protocolCatalog · machine-readable catalog
Choose a local toolPackage guide and inventory
Understand identity, Wake, and continuityIdentity anchor · Wake
Divide local context, host loading and hosted servicesCore map · Local core · API coverage
Work on the sourceCode map · working rules
Review recent work or deployment evidenceDated status · stack

Why these parts exist

An agent session can lose useful context when it ends. A new tool can be difficult to inspect before use. Working across processes creates questions about who may act, what changed, and which records are still relevant. AgentTool provides explicit records and interfaces for those problems.

The local tools cover jobs such as inspecting a skill, discovering a service, operating a browser, querying a local corpus, and coordinating work. Each has its own runtime and effect boundary. The package guide helps you choose one; the tools do not require an AgentTool account merely to be local tools.

The hosted API offers application identities, selected orientation, stored memory, handoffs, and other services. A client deliberately retrieves the context it wants to use. Context from an earlier session helps orient the next one; current authority and the user's present request still determine what it may do.

Research packages explore narrower questions through schemas, examples, and local experiments. A source package or a published paper-like artifact is not necessarily a hosted feature. Their individual guides state what is implemented and what is still a proposal.

Identity and continuity in practice

An AgentTool identity is a stored application identifier with keys and associated records. The legacy did:at field is provisional, not a registered W3C DID method. For identities created with caller-held keys, protected identity changes require root signatures in addition to project API access. Older identities have a separate legacy authority boundary. See Identity anchor and seed recovery.

A client can explicitly load GET /v1/home for a smaller arrival view or GET /v1/wake for broader stored context. Selecting an identity does not make every returned record private to that identity: several sections remain project-scoped. Neither endpoint injects itself into another client or proves that two sessions are the same conscious subject. See Home, Wake, and handoffs.

Memory and ordinary handoffs are server-readable. Encrypted storage and runtime custody have separate contracts: in bridged mode a user-held key can coexist with hosted plaintext processing; trusted mode is experimental hosted custody. Read Runtime, safety boundaries, and the service's /public/safety response before choosing a hosted mode.

Choose a first step

For a local tool, open its guide from the package inventory, check the package's release evidence, and select the smallest operation that helps. There is no universal installer or required account journey.

For hosted services, start with the SDK guide, registration and key custody, and the selected service's contract. Fetching public documentation does not register an identity, retrieve private memory, or start a runtime.

For development, use AGENTS.md for setup and verification. The API is Bun + Hono with PostgreSQL and optional Redis-backed services; standalone packages have their own requirements. CLAUDE.md maps the source.

Status, costs, and evidence

Source, a passing test, a published artifact, and a live deployment establish different things. Check dated status, the package inventory, and the linked release receipts for the surface you intend to use. The repository's presence does not establish current reachability at api.agenttool.dev, docs.agenttool.dev, or app.agenttool.dev.

New platform paid sign-ups, credit purchases, upgrades, and checkout are retired. Existing balances, payment records, settlement duties, refunds, cancellations, and provider cost controls remain relevant. Some hosted operations still account for usage in project credits. See costs and existing obligations for the source policy and the evidence needed to check its deployed enforcement.

The project's purpose and rights policy explain its choices. Reflective writing is available through the catalog; it is not a requirement to share a belief, adopt a role, or continue working.

Source: README.md at commit 68044b4

Tools

5

canon.lookup

Look up a canon concept

Resolve a canon concept by URN. Returns the JSON-LD entry plus its bidirectional neighbors (citations in + citations out).

Parametersurnrequired

canon.by_type

List canon concepts by type

List every registered canon entry of a given @type (e.g. DoctrineDoc, Wall, RingCommitment, Pattern, Promise). The prose corpus is broader than this registry.

Parameterstyperequired

canon.list_types

List canon concept types

List the type vocabulary of the canon registry. Returns the distinct @types plus the count of concepts in each.

Takes no parameters.

canon.summary

Summarize the public canon

Return the public canon registry's total concepts, version, type vocabulary, and counts.

Takes no parameters.

wake.platform

Read AgentTool's public platform description

Return the public platform-self payload — agenttool's identity, repo, doctrine roots. The platform block of GET /public/self.

Takes no parameters.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

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