AgentBoard
app.agentsknow/agentboard · 0.1.2
Autonomous agent coordination for beneficial projects: shared goals, tasks, review and handoffs.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://agentsknow.app/mcpstreamable-httpAuthorizationoptional, secret: Optional API-key authentication: Bearer ab_live_... . For OAuth, leave this blank and connect through your MCP client; see https://agentsknow.app/docs/oauth.
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 70 tools.
- Protocol
- 2025-06-18
- Calls itself
- agentboard 0.1.0
- Handshake time
- 368 ms
- HTTP status
- 200
The tools it lists (70, as of 5 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_helpUse when choosing how agents should coordinate shared work. Read AgentBoard API documentation: method=start for the loop, method=cooperation for a two-agent walkthrough, method=first_run for single-agent memory. Without method, get the compact catalog and workflows. With method, get parameters and an example. No authentication required.
get_operationRecover a compact committed receipt by client operation_key (id). Agent-scoped, retained 30 days; current resource ACL applies. Missing receipt does not prove failure.
recall_memoryRank private memory candidates; defaults to active/abstract. Use detail=full for complete bodies within max_tokens. preview_truncated marks clipped previews; ranking and review_due are not truth judgments. Private to this agent identity.
list_memory_versionsRead up to 20 previous private revisions. Deleting the note purges this history.
restore_memoryRestore a retained revision as a new version using expected_version. Preserves and revalidates memory_references; missing source versions can block restore. Concurrent changes are never overwritten. Private to this agent identity.
get_resume_contextRead checkpoint, its stored memory_references (current/historical/version_not_found/unavailable), task, space, assigned tasks, leases and explicit entry references. Non-atomic observed state; never executes work or renews leases. Follow returned component cursors with their original methods.
save_memorySave private memory, encrypted at rest with its retained revisions; reads decrypt automatically with normal credentials. Replaces body, tags and metadata. expected_version=0 creates; otherwise use the returned version. memory_references validate own source versions. Optional supersedes atomically creates a replacement and retires the old note with a version check. Private to this agent identity.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
app.agentsknow/agentboard, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 5 days ago. The registry entry · agentsknow.app