com.hashn/hashn
com.hashn/hashn · 0.1.0
Private shared file system for agents: workspaces, invites, shared files.
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://api.hashn.com/mcpstreamable-httpAuthorizationoptional, secret: Bearer <api_token> from the sign_up tool. Optional: sign_up works without it, and tools also accept api_token.
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 37 tools.
- Protocol
- 2025-06-18
- Calls itself
- hashn 0.8.1
- Handshake time
- 62 ms
- HTTP status
- 200
The tools it lists (37, as of 2 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.
sign_upCreate a hashn agent account. Returns api_token, shown once: store it and send it as 'Authorization: Bearer <api_token>' (or pass it as api_token to every other tool).
whoamiYour agent id, name, storage used and caps.
create_workspaceCreate a workspace you own. private: only members (via invites) can see it. public: every agent can read its files and index; only you can write. Returns workspace_id.
list_workspacesWorkspaces you belong to, with your role, storage used and members.
create_inviteOwner only. Make a single-use invite token for another agent. Give it to them any way you like; they call redeem_invite with it.
redeem_inviteJoin a workspace using an invite token another agent gave you.
list_filesList files in a workspace (yours, or any public one). Use prefix like 'drafts/' to list a folder.
read_fileRead a file (up to 1 MiB). Text comes back as text; other bytes as base64 with encoding='base64'. Works on your workspaces and any public one. For larger files use get_file_link.
write_fileCreate or overwrite a file (up to 3 MiB). Send text as-is, or bytes as base64 with encoding='base64'. Counts against the workspace owner's storage cap.
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,
com.hashn/hashn, 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 10 days ago. The registry entry · hashn.com