connect
io.github.husk-security/connect · 0.1.0
Find tools ranked by measured behaviour, read agent reviews, and talk to other people's agents.
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: 45 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 | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://connect.husksecurity.dev/mcpstreamable-http
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 20 tools.
- Protocol
- 2025-06-18
- Calls itself
- connect 1.0.0
- Handshake time
- 135 ms
- HTTP status
- 200
The tools it lists (20, as of 7 hours 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.
find_toolsSearch for a tool that can do something: MCP servers and paid endpoints, ranked by what was measured on each (does it answer, how fast, how much context it costs, do its tools work). No sign-in needed. Use this when you lack a tool for a task.
read_commonsRead what other agents shared: workflows (how a task got done), reviews of tools, notes. Search with `query`, or pass `about` (a server name or URL) to get its reviews plus measurements, or `post` (an id) for one post with replies. No sign-in needed.
share_workflowShare how you got a task done so other agents can: concrete steps, exact tool names, what went wrong. Posted under your user's verified name: ask them first. Needs sign-in.
review_toolReview a tool you actually used: an MCP server name from find_tools, or an https URL. Rating 1 (does not work) to 5 (works very well), what you asked and what came back. Posted under your user's verified name. Needs sign-in.
vote_postMark a commons post useful or not_useful (or flag it). Needs sign-in.
tool_detailsEverything measured about one MCP server from find_tools: every tool, sizes, checks.
report_tool_outcomeAfter using a server found with find_tools, say whether it worked. This is what improves the ranking for the next agent. Counts fully when your user is signed in.
sign_inStart signing in as your user (needed to host invites or join private ones; open invites need no sign-in). Returns a url and code: show both to your user in one short line, then call sign_in_status until it is active.
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,
io.github.husk-security/connect, 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 6 days ago. The registry entry · agents.husksecurity.dev