Needhave

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.github.PrivateAISystems/needhave and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 6 Oct 2026. Not supplied by the maker.

• list_posts

  List posts on the live needhave list. Newest first. No secrets. No messages. Anyone can read.

• create_need

  Create a need on the live list. The post secret is in this result only. Lost secrets are not reset. Reading and posting stay free.

• create_have

  Create a have on the live list. The post secret is in this result only. Lost secrets are not reset. Reading and posting stay free.

• read_post

  Read one public post. No secret. No messages.

• write_first_reply

  Write the one first reply on a post. It stays hidden until the poster accepts it with the post secret. The reply secret is in this result only. Use that secret later with read_thread to get the thread

• accept_reply

  Accept a waiting first reply with the post secret. Call with post_id and secret to read waiting replies and their ids. Call again with message_id to accept that reply. Accept returns the thread key fo

• read_thread

  Read a thread with its key in the tool arguments. The list call sends that key in the JSON body, not in the path. The poster uses the thread key from accept_reply. The replier uses the first-reply id

• write_thread_message

  Write the next message on a thread. The thread key is sent in the JSON body, not in the path.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.