bsv-mcp 0.5.1 → 0.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +19 -0
- package/README.md +15 -0
- package/dist/index.js +671 -1003
- package/package.json +1 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,24 @@
|
|
|
1
1
|
# BSV MCP Server Changelog
|
|
2
2
|
|
|
3
|
+
## [0.6.0] - 2026-09-09
|
|
4
|
+
|
|
5
|
+
### Changed
|
|
6
|
+
|
|
7
|
+
- Consolidate social tools into `bsocial_read` and `bsocial_publish` in both tool
|
|
8
|
+
profiles. Replace `bsocial_readPosts`, `bsocial_createPost`, `bmap_readPosts`,
|
|
9
|
+
`bmap_readLikes`, `bmap_readFollows`, and `bap_friend`; clients must refresh tools.
|
|
10
|
+
- Add canonical social actions, replies, reactions, relationships, messages,
|
|
11
|
+
media, tags, and unsigned previews with one shared schema and signing path.
|
|
12
|
+
- Document action-specific inputs and BMAP backend configuration. Messages are
|
|
13
|
+
public records; publishing does not encrypt them.
|
|
14
|
+
|
|
15
|
+
### Fixed
|
|
16
|
+
|
|
17
|
+
- Use social API routes and retain structured indexer records without claiming
|
|
18
|
+
independent signature verification or derived relationship state.
|
|
19
|
+
- Sign legacy social records with an explicit identity key, fund with the payment
|
|
20
|
+
key, estimate unsigned transaction fees, and report broadcast failures.
|
|
21
|
+
|
|
3
22
|
## [0.5.1] - 2026-09-08
|
|
4
23
|
|
|
5
24
|
### Changed
|
package/README.md
CHANGED
|
@@ -111,6 +111,21 @@ protocol support guide](docs/mcp-client-protocol-support.md) for the per-family
|
|
|
111
111
|
operation bounds, endpoint contracts, MCP Apps compatibility, and validation
|
|
112
112
|
status.
|
|
113
113
|
|
|
114
|
+
## Social
|
|
115
|
+
|
|
116
|
+
Two tools cover social operations in both full and compact catalogs:
|
|
117
|
+
|
|
118
|
+
- `bsocial_read`: posts, replies, search, likes, friends, channels, messages, videos, and raw action history.
|
|
119
|
+
- `bsocial_publish`: posts/replies, reposts, likes/unlikes, follows/unfollows, friend/unfriend records, messages, and video records. Tags and attachments use separate, independently signed outputs.
|
|
120
|
+
|
|
121
|
+
```json
|
|
122
|
+
{"action":{"type":"post","content":"Hello Bitcoin","tags":["bitcoin"]},"preview":true}
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
Preview returns unsigned outputs without using keys or spending. Remove `preview` to publish through the selected identity wallet's existing permissions. Messages are public unless their content was encrypted beforehand; a recipient context does not encrypt them. Friend records advertise a communication public key from an established key-agreement workflow.
|
|
126
|
+
|
|
127
|
+
See the [social guide](https://bsvmcp.com/docs#social) for examples and migration from the old tool names. `PUBLIC_BMAP_URL` is the indexer server root (with `/social` and `/q` routes), not a wallet or identity API. Raw follow/unfollow records are event history, not a claim about current relationship state.
|
|
128
|
+
|
|
114
129
|
## Local wallet modes
|
|
115
130
|
|
|
116
131
|
External mode connects to an existing BRC-100 signer. The signer keeps the
|