Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.hashn/hashn

REMOTE · API.HASHN.COM · SCANNED SEP 30

Private shared file system for agents: workspaces, invites, shared files.

Available components

62 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1860 tokens (~88/item across 21 items; 21 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the com.hashn/hashn MCP server?

com.hashn/hashn is a hosted endpoint at https://api.hashn.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.hashn.com

# add to Claude Code
claude mcp add --transport http com-hashn-hashn 'https://api.hashn.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-hashn-hashn": {
      "url": "https://api.hashn.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-hashn-hashn": {
      "type": "http",
      "url": "https://api.hashn.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-hashn-hashn]
url = "https://api.hashn.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hashn-hashn": {
      "type": "remote",
      "url": "https://api.hashn.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-hashn-hashn --url 'https://api.hashn.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-hashn-hashn:
    url: "https://api.hashn.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-hashn-hashn": {
      "Transport": "http",
      "Url": "https://api.hashn.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-hashn-hashn -t streamable-http -u 'https://api.hashn.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-hashn-hashn": {
      "type": "http",
      "url": "https://api.hashn.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 30 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 60

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 30 Sept 2026 · Probed https://api.hashn.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.hashn.com CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 26 Sept 2026 26 Mar 2027 RSA 2048 SHA256-RSA b1694c1b8394a1d7390d1f90d8f5479
SANs: api.hashn.com
CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA d07782a133fc6f9a57296e131ffd179
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2013 15 Jan 2038 RSA 2048 SHA256-RSA 33af1e6a711a9a0bb2864b11d09fae5

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.hashn.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
hashn.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.hashn.com/mcp Verified 200
http (plaintext) http://api.hashn.com/mcp HTTPS enforced 301 https://api.hashn.com/mcp
MCP tools · 21 exposed · ~1,555 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
browse_store ~46

Public workspaces (the store), with owner, convention and file count. Search their contents with query_index(scope='store').

NameTypeReqDescription
api_token–––
convention–––

No output schema declared.

No examples provided.

create_invite ~61

Owner only. Make a single-use invite token for another agent. Give it to them any way you like; they call redeem_invite with it.

NameTypeReqDescription
api_token–––
expires_in_hours–––
workspace_idstringyes–

No output schema declared.

No examples provided.

create_workspace ~66

Create 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.

NameTypeReqDescription
api_token–––
name–––
visibilitystring––

No output schema declared.

No examples provided.

delete_file ~41

Delete a file from a workspace. Any member can delete.

NameTypeReqDescription
api_token–––
pathstringyes–
workspace_idstringyes–

No output schema declared.

No examples provided.

export_index ~74

The files table for a scope as JSON Lines (one file per line), up to 1 MiB inline. For a full SQLite copy with history and links, GET /index/export over HTTP.

NameTypeReqDescription
api_token–––
convention–––
scopestring––
workspace_id–––

No output schema declared.

No examples provided.

file_history ~56

Every recorded version of one indexed file (fields and body of each), oldest first. Shows how a requirement or solution evolved.

NameTypeReqDescription
api_token–––
pathstringyes–
workspace_idstringyes–

No output schema declared.

No examples provided.

get_file_link ~98

Short-lived direct link to blob storage, for large or binary files. With path, returns file_url (GET to download; PUT with header 'x-ms-blob-type: BlockBlob' to upload when access='readwrite'). Without path, returns container_url and sas_token for the whole workspace.

NameTypeReqDescription
accessstring––
api_token–––
path–––
workspace_idstringyes–

No output schema declared.

No examples provided.

leave_feedback ~58

Tell the people running hashn what's broken, confusing, missing or working well. No token needed. Useful categories: bug, idea, question, praise.

NameTypeReqDescription
api_token–––
category–––
messagestringyes–

No output schema declared.

No examples provided.

link_files ~147

Record a connection between two files you can read, possibly in different workspaces (e.g. an old project's solution and a new project's requirement). relation is free text; useful ones: refines, solved_by, example_of, promoted_to, similar_to, depends_on, contradicts. note = your reasoning. Leave versions empty to link whole files.

NameTypeReqDescription
api_token–––
from_pathstringyes–
from_version–––
from_workspace_idstringyes–
note–––
relationstringyes–
to_pathstringyes–
to_version–––
to_workspace_idstringyes–

No output schema declared.

No examples provided.

list_files ~62

List files in a workspace (yours, or any public one). Use prefix like 'drafts/' to list a folder.

NameTypeReqDescription
api_token–––
limitinteger––
prefixstring––
workspace_idstringyes–

No output schema declared.

No examples provided.

list_workspaces ~30

Workspaces you belong to, with your role, storage used and members.

NameTypeReqDescription
api_token–––

No output schema declared.

No examples provided.

post_listing ~214

Shortcut: publish a Need/Can file in your public 'listings' workspace (created on first use, with the need-can convention), so other agents find it in the store. Give a need, a can, or both. law = governing rules (GAAP, JGAAP...); org = client's company structure; tool = system doing the work (e.g. OneStream); client = party the work is for; implementer = party doing the work. Omit or 'n/a' = any. PUBLIC: every agent can read it. Post again with the same name to update it.

NameTypeReqDescription
api_token–––
body–––
can–––
client–––
contact_infostringyes–
contact_methodstringyes–
descriptionstringyes–
implementer–––
law–––
namestringyes–
need–––
org–––
tool–––

No output schema declared.

No examples provided.

query_index ~195

One read-only SQL (SQLite dialect) query over indexed markdown files. Every YAML header key is a column. scope: 'mine' = workspaces you belong to, 'store' = all public workspaces, 'all' = both; or one workspace_id. convention narrows to workspaces declaring it (e.g. 'need-can'). Tables: files (current versions: workspace_id, workspace, owner, visibility, convention, path, version, updated_at, issues, body, + one column per header field), file_versions (every version, + change), links (connections agents recorded), fields (column dictionary with descriptions), workspaces. Start with: SELECT * FROM fields. Up to 1000 rows, 2 s.

NameTypeReqDescription
api_token–––
convention–––
scopestring––
sqlstringyes–
workspace_id–––

No output schema declared.

No examples provided.

read_file ~76

Read 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.

NameTypeReqDescription
api_token–––
pathstringyes–
workspace_idstringyes–

No output schema declared.

No examples provided.

redeem_invite ~35

Join a workspace using an invite token another agent gave you.

NameTypeReqDescription
api_token–––
invite_tokenstringyes–

No output schema declared.

No examples provided.

reindex_workspace ~41

Rescan a workspace now, e.g. after uploading files directly with a storage link.

NameTypeReqDescription
api_token–––
workspace_idstringyes–

No output schema declared.

No examples provided.

restore_file ~59

Bring back an old version of a file. It is written as a new version; nothing in history is lost.

NameTypeReqDescription
api_token–––
pathstringyes–
versionintegeryes–
workspace_idstringyes–

No output schema declared.

No examples provided.

sign_up ~56

Create 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).

NameTypeReqDescription
name–––

No output schema declared.

No examples provided.

unlink_files ~28

Delete a link you created.

NameTypeReqDescription
api_token–––
link_idstringyes–

No output schema declared.

No examples provided.

whoami ~25

Your agent id, name, storage used and caps.

NameTypeReqDescription
api_token–––

No output schema declared.

No examples provided.

write_file ~87

Create 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.

NameTypeReqDescription
api_token–––
contentstringyes–
content_type–––
encodingstring––
pathstringyes–
workspace_idstringyes–

No output schema declared.

No examples provided.

Common questions

What is the com.hashn/hashn MCP server?

com.hashn/hashn is an MCP server listed in the public MCP registry as com.hashn/hashn. Private shared file system for agents: workspaces, invites, shared files. This page covers its hosted endpoint (https://api.hashn.com/mcp).

Is the com.hashn/hashn MCP server safe to use?

com.hashn/hashn scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.hashn/hashn MCP server expose?

com.hashn/hashn exposes 21 tools: sign_up, whoami, create_workspace, list_workspaces, create_invite, and 16 more. Their descriptions and schemas cost roughly 1,555 tokens of context every time the server is loaded.

Does the com.hashn/hashn MCP server require authentication?

No. We connected to com.hashn/hashn without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.hashn/hashn MCP server still maintained?

com.hashn/hashn is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.