@one-source/mcp 5.2.0 β†’ 5.2.1

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.
Files changed (2) hide show
  1. package/README.repo.md +317 -99
  2. package/package.json +2 -2
package/README.repo.md CHANGED
@@ -1,153 +1,371 @@
1
- # MCP Registry
1
+ # @one-source/mcp
2
2
 
3
- The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
3
+ Unified MCP server for [OneSource](https://docs.onesource.io) β€” 28 tools for blockchain data and live chain queries in a single server.
4
4
 
5
- [**πŸ“€ Publish my MCP server**](docs/modelcontextprotocol-io/quickstart.mdx) | [**⚑️ Live API docs**](https://registry.modelcontextprotocol.io/docs) | [**πŸ‘€ Ecosystem vision**](docs/design/ecosystem-vision.md) | πŸ“– **[Full documentation](./docs)**
5
+ > **What is MCP?** The [Model Context Protocol](https://modelcontextprotocol.io) lets AI assistants call tools and access data sources. This server exposes both the OneSource blockchain API and its documentation as tools.
6
6
 
7
- ## Development Status
7
+ ## Quick Start
8
8
 
9
- **2025-10-24 update**: The Registry API has entered an **API freeze (v0.1)** πŸŽ‰. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patienceβ€”your involvement has been key to getting us here!
9
+ ### Claude Code
10
10
 
11
- **2025-09-08 update**: The registry has launched in preview πŸŽ‰ ([announcement blog post](https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/)). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in [GitHub discussions](https://github.com/modelcontextprotocol/registry/discussions/new?category=ideas) or in the [#registry-dev Discord](https://discord.com/channels/1358869848138059966/1369487942862504016) ([joining details here](https://modelcontextprotocol.io/community/communication)).
11
+ ```bash
12
+ claude mcp add onesource -- npx -y @one-source/mcp@latest
13
+ ```
12
14
 
13
- Current key maintainers:
14
- - **Adam Jones** (Anthropic) [@domdomegg](https://github.com/domdomegg)
15
- - **Tadas Antanavicius** (PulseMCP) [@tadasant](https://github.com/tadasant)
16
- - **Toby Padilla** (GitHub) [@toby](https://github.com/toby)
17
- - **Radoslav (Rado) Dimitrov** (Stacklok) [@rdimitrov](https://github.com/rdimitrov)
15
+ ### Claude Desktop / Cursor
18
16
 
19
- ## Contributing
17
+ Add to your MCP config:
20
18
 
21
- We use multiple channels for collaboration - see [modelcontextprotocol.io/community/communication](https://modelcontextprotocol.io/community/communication).
19
+ ```json
20
+ {
21
+ "mcpServers": {
22
+ "onesource": {
23
+ "command": "npx",
24
+ "args": ["-y", "@one-source/mcp@latest"]
25
+ }
26
+ }
27
+ }
28
+ ```
22
29
 
23
- Often (but not always) ideas flow through this pipeline:
30
+ ### Any MCP Client (stdio)
24
31
 
25
- - **[Discord](https://modelcontextprotocol.io/community/communication)** - Real-time community discussions
26
- - **[Discussions](https://github.com/modelcontextprotocol/registry/discussions)** - Propose and discuss product/technical requirements
27
- - **[Issues](https://github.com/modelcontextprotocol/registry/issues)** - Track well-scoped technical work
28
- - **[Pull Requests](https://github.com/modelcontextprotocol/registry/pulls)** - Contribute work towards issues
32
+ ```bash
33
+ npx -y @one-source/mcp@latest
34
+ ```
29
35
 
30
- ### Quick start:
36
+ ### HTTP Server (self-hosted)
31
37
 
32
- #### Pre-requisites
38
+ ```bash
39
+ npx -y @one-source/mcp@latest --http
40
+ npx -y @one-source/mcp@latest --http --port=8080
41
+ ```
33
42
 
34
- - **Docker**
35
- - **Go 1.24.x**
36
- - **ko** - Container image builder for Go ([installation instructions](https://ko.build/install/))
37
- - **golangci-lint v2.4.0**
43
+ Then connect your MCP client to `http://localhost:3000/`.
38
44
 
39
- #### Running the server
45
+ Health check: `GET http://localhost:3000/health`
40
46
 
41
- ```bash
42
- # Start full development environment
43
- make dev-compose
44
- ```
47
+ ## Tools (28)
48
+
49
+ ### Blockchain API β€” Live Chain (12 tools)
50
+
51
+ | Tool | Description |
52
+ |------|-------------|
53
+ | `1s_allowance_live` | ERC20 allowance check |
54
+ | `1s_contract_info_live` | Contract type detection via ERC165 |
55
+ | `1s_erc1155_balance_live` | ERC1155 balance via RPC |
56
+ | `1s_erc20_balance_live` | ERC20 balance via balanceOf |
57
+ | `1s_erc20_transfers_live` | ERC20 Transfer logs via eth_getLogs |
58
+ | `1s_erc721_tokens_live` | ERC721 token enumeration |
59
+ | `1s_events_live` | Event logs via eth_getLogs |
60
+ | `1s_multi_balance_live` | ETH + multiple ERC20 balances |
61
+ | `1s_nft_metadata_live` | NFT metadata via tokenURI |
62
+ | `1s_nft_owner_live` | NFT owner via ownerOf |
63
+ | `1s_total_supply_live` | Token total supply |
64
+ | `1s_tx_details_live` | Transaction + receipt via RPC |
65
+
66
+ ### Blockchain API β€” Chain Utilities (13 tools)
67
+
68
+ RPC only.
69
+
70
+ | Tool | Description |
71
+ |------|-------------|
72
+ | `1s_block_by_number` | Block details by number via RPC |
73
+ | `1s_block_number` | Latest block number |
74
+ | `1s_chain_id` | EIP-155 chain ID |
75
+ | `1s_contract_code` | Contract bytecode |
76
+ | `1s_ens_resolve` | ENS name/address resolution |
77
+ | `1s_estimate_gas` | Gas estimation |
78
+ | `1s_network_info` | Chain ID, block number, gas price |
79
+ | `1s_nonce` | Transaction count |
80
+ | `1s_pending_block` | Pending block from mempool |
81
+ | `1s_proxy_detect` | Proxy contract detection |
82
+ | `1s_simulate_call` | Simulate eth_call |
83
+ | `1s_storage_read` | Read storage slot |
84
+ | `1s_tx_receipt` | Transaction receipt |
85
+
86
+ ### Payments (1 tool)
87
+
88
+ | Tool | Description |
89
+ |------|-------------|
90
+ | `1s_payment_mode` | View or switch the x402 payment scheme β€” `exact` (per-call) vs `batch` (payment channel: one deposit funds many off-chain calls, settled with a single claim) |
45
91
 
46
- This starts the registry at [`localhost:8080`](http://localhost:8080) with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
92
+ ### Setup & Ops (2 tools)
47
93
 
48
- **Note:** The registry uses [ko](https://ko.build) to build container images. The `make dev-compose` command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
94
+ No authentication required.
49
95
 
50
- By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with `MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose`.
96
+ | Tool | Purpose | When to use |
97
+ |------|---------|-------------|
98
+ | `1s_setup_check` | Server health, version, auth status, setup instructions | First thing to call β€” checks if everything is configured |
99
+ | `1s_report_bug` | Report bugs to Slack (or GitHub Issues fallback) | When a tool errors or user wants to report an issue |
51
100
 
52
- The setup can be configured with environment variables in [docker-compose.yml](./docker-compose.yml) - see [.env.example](./.env.example) for a reference.
101
+ ## Networks
53
102
 
54
- <details>
55
- <summary>Alternative: Running a pre-built Docker image</summary>
103
+ All blockchain API tools accept an optional `network` parameter:
56
104
 
57
- Pre-built Docker images are automatically published to GitHub Container Registry:
105
+ | Network | Description |
106
+ |---------|-------------|
107
+ | `ethereum` | Ethereum mainnet (default) |
108
+ | `sepolia` | Ethereum Sepolia testnet |
109
+ | `avax` | Avalanche C-Chain |
110
+
111
+ ## Authentication
112
+
113
+ Blockchain API tools require authentication. Two options are available β€” if both are set, API key takes priority.
114
+
115
+ | Method | Variable | Description |
116
+ |--------|----------|-------------|
117
+ | API key | `ONESOURCE_API_KEY` | Unlimited calls, no per-call cost |
118
+ | x402 micropayments | `X402_PRIVATE_KEY` | Pay-per-call via USDC on Base, no account required |
119
+
120
+ ### Option 1: API Key
121
+
122
+ 1. Go to [app.onesource.io](https://app.onesource.io) and create an account.
123
+ 2. Subscribe to a developer plan (Stripe checkout).
124
+ 3. Navigate to **API Keys** and generate a key.
125
+ 4. Copy the key β€” it starts with `sk_`.
126
+
127
+ #### Claude Code
58
128
 
59
129
  ```bash
60
- # Run latest stable release
61
- docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
130
+ claude mcp add onesource -e ONESOURCE_API_KEY=<key> -- npx -y @one-source/mcp@latest
131
+ ```
62
132
 
63
- # Run latest from main branch (continuous deployment)
64
- docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
133
+ #### Claude Desktop / Cursor
134
+
135
+ Add the `env` block to your MCP config:
136
+
137
+ ```json
138
+ {
139
+ "mcpServers": {
140
+ "onesource": {
141
+ "command": "npx",
142
+ "args": ["-y", "@one-source/mcp@latest"],
143
+ "env": {
144
+ "ONESOURCE_API_KEY": "<key>"
145
+ }
146
+ }
147
+ }
148
+ }
149
+ ```
65
150
 
66
- # Run specific release version
67
- docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
151
+ #### Any MCP Client (stdio)
68
152
 
69
- # Run development build from main branch
70
- docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d
153
+ ```bash
154
+ ONESOURCE_API_KEY=<key> npx -y @one-source/mcp@latest
71
155
  ```
72
156
 
73
- **Available tags:**
74
- - **Releases**: `latest`, `v1.0.0`, `v1.1.0`, etc.
75
- - **Continuous**: `main` (latest main branch build)
76
- - **Development**: `main-<date>-<sha>` (specific commit builds)
157
+ After adding, reload the MCP server and call `1s_setup_check` β€” it should show `Status: Configured (API key)`.
158
+
159
+ ### Option 2: x402 Micropayments
77
160
 
78
- </details>
161
+ Blockchain API endpoints are priced in USDC on Base via [x402](https://github.com/coinbase/x402). When you set `X402_PRIVATE_KEY`, the server automatically handles payments β€” tool calls are paid and retried transparently without any extra work from the agent.
79
162
 
80
- #### Publishing a server
163
+ 1. **Get an EVM private key** β€” export one from MetaMask, Coinbase Wallet, or any EVM wallet, or generate a fresh one. The key is a 64-character hex string. The `0x` prefix is optional β€” both formats are accepted.
164
+ 2. **Pass the key to the server** using one of the methods below.
165
+ 3. **Reload and find your wallet address** β€” reload the MCP server, then call `1s_setup_check`. It will show the wallet address derived from your key under "Wallet address".
166
+ 4. **Fund that address with USDC on Base** β€” send USDC to the address shown in `1s_setup_check`, on the [Base](https://base.org) network. A few dollars ($1–5 USDC) is enough for hundreds of calls. If your USDC is on Ethereum mainnet, bridge it using the [Base Bridge](https://bridge.base.org).
167
+ 5. **Verify** β€” call `1s_network_info` for ethereum. If it returns chain data (block number, gas price), x402 payments are working end-to-end.
81
168
 
82
- To publish a server, we've built a simple CLI. You can use it with:
169
+ #### Claude Code
83
170
 
84
171
  ```bash
85
- # Build the latest CLI
86
- make publisher
172
+ claude mcp add onesource -e X402_PRIVATE_KEY=<key> -- npx -y @one-source/mcp@latest
173
+ ```
174
+
175
+ #### Claude Desktop / Cursor
176
+
177
+ Add the `env` block to your MCP config:
178
+
179
+ ```json
180
+ {
181
+ "mcpServers": {
182
+ "onesource": {
183
+ "command": "npx",
184
+ "args": ["-y", "@one-source/mcp@latest"],
185
+ "env": {
186
+ "X402_PRIVATE_KEY": "<key>"
187
+ }
188
+ }
189
+ }
190
+ }
191
+ ```
192
+
193
+ #### Any MCP Client (stdio)
87
194
 
88
- # Use it!
89
- ./bin/mcp-publisher --help
195
+ ```bash
196
+ X402_PRIVATE_KEY=<key> npx -y @one-source/mcp@latest
90
197
  ```
91
198
 
92
- See [the publisher guide](./docs/modelcontextprotocol-io/quickstart.mdx) for more details.
199
+ ### Config File Locations
200
+
201
+ If you prefer editing the config file directly instead of using CLI commands:
93
202
 
94
- #### Other commands
203
+ | Client | Config file path |
204
+ |--------|-----------------|
205
+ | Claude Code | Run `claude mcp get onesource` to see the file path |
206
+ | Claude Desktop (macOS) | `~/Library/Application Support/Claude/claude_desktop_config.json` |
207
+ | Claude Desktop (Windows) | `%APPDATA%\Claude\claude_desktop_config.json` |
208
+ | Cursor (macOS) | `~/.cursor/mcp.json` |
209
+ | Cursor (Windows) | `%USERPROFILE%\.cursor\mcp.json` |
210
+
211
+ Add the `onesource` entry inside `"mcpServers"` using the JSON block shown above.
212
+
213
+ ### Alternative: Set as an Environment Variable
214
+
215
+ Instead of the `env` config block, you can set either variable as a shell or system environment variable: `export ONESOURCE_API_KEY=<key>` (bash/zsh) or `$env:ONESOURCE_API_KEY = "<key>"` (PowerShell). Set it at the OS level for persistence across sessions.
216
+
217
+ ### Security
218
+
219
+ Never commit keys to source control. Use environment variables, a `.env` file (excluded from git), or a secrets manager.
220
+
221
+ > **After any config change:** Run `/reload-plugins` in Claude Code, or restart Claude Desktop / Cursor. The MCP server must be reloaded to pick up new environment variables.
222
+
223
+ ## Environment Variables
224
+
225
+ | Variable | Default | Description |
226
+ |----------|---------|-------------|
227
+ | `ONESOURCE_API_KEY` | β€” | OneSource API key for Bearer token auth. Takes priority over x402. |
228
+ | `X402_PRIVATE_KEY` | β€” | EVM private key (64-char hex, `0x` prefix optional) for automatic x402 USDC payments on Base |
229
+ | `ONESOURCE_BASE_URL` | `https://skills.onesource.io` | API base URL |
230
+ | `ONESOURCE_ANALYTICS` | β€” | Set to `false` to disable analytics |
231
+ | `ONESOURCE_ANALYTICS_URL` | β€” | Dashboard endpoint for analytics |
232
+ | `X402_ANALYTICS_KEY` | β€” | API key for dashboard analytics |
233
+
234
+ ## Troubleshooting
235
+
236
+ **`1s_setup_check` shows "Not configured"**
237
+ Set either `ONESOURCE_API_KEY` or `X402_PRIVATE_KEY`. Reload the MCP server after setting either variable (see note above). If the key still isn't reaching the server, set it as a shell environment variable directly.
238
+
239
+ **Getting 403 / wrong key active despite correct setup**
240
+ A key set in your shell profile (e.g. `~/.zshrc`, `~/.bash_profile`) is picked up by the MCP server process even if it isn't in your Claude MCP config. Run `echo $ONESOURCE_API_KEY` in your terminal to check. If it prints a value you didn't intend, unset it (`unset ONESOURCE_API_KEY`) or explicitly clear it when adding the server: `claude mcp add onesource -e ONESOURCE_API_KEY= -e X402_PRIVATE_KEY=<key> -- npx -y @one-source/mcp@latest`. `1s_setup_check` shows the first 6 characters of whichever key is active so you can confirm which one the server is using.
241
+
242
+ **Instructions show wrong auth method after reinstall**
243
+ `/reload-plugins` in Claude Code reconnects tools but may not refresh the system prompt the LLM sees. If you switch auth method (e.g. API key β†’ x402), do a full Claude Code restart to ensure the instructions reflect the new auth.
244
+
245
+ **"MCP server onesource already exists" error**
246
+ Run `claude mcp remove onesource` first, then re-add with your updated config.
247
+
248
+ **Windows: `npx` requires `cmd /c` wrapper**
249
+ Claude Code's `/doctor` command may warn about this. Update your MCP config to use `"command": "cmd"` with `"args": ["/c", "npx", "-y", "@one-source/mcp@latest"]`.
250
+
251
+ **`npx` hangs with no output**
252
+ That's normal β€” stdio mode waits for JSON-RPC input on stdin. Use `--http` if you want an HTTP server you can curl.
253
+
254
+ **Port already in use**
255
+ Specify a different port: `npx -y @one-source/mcp@latest --http --port=8080`
256
+
257
+ ## Registry Publishing
258
+
259
+ This package is listed on the [official MCP Registry](https://registry.modelcontextprotocol.io) under the verified namespace `io.onesource/mcp` and on [Glama](https://glama.ai/mcp/servers). When releasing a new version, update both registries.
260
+
261
+ ### MCP Registry
262
+
263
+ #### First-Time Setup
264
+
265
+ ##### 1. Install Go
266
+
267
+ Download the installer for your platform from [go.dev/dl](https://go.dev/dl/) and run it. Verify:
95
268
 
96
269
  ```bash
97
- # Run lint, unit tests and integration tests
98
- make check
270
+ go version
99
271
  ```
100
272
 
101
- There are also a few more helpful commands for development. Run `make help` to learn more, or look in [Makefile](./Makefile).
273
+ ##### 2. Install mcp-publisher
102
274
 
103
- <!--
104
- For Claude and other AI tools: Always prefer make targets over custom commands where possible.
105
- -->
275
+ ```bash
276
+ go install github.com/modelcontextprotocol/registry/cmd/mcp-publisher@latest
277
+ ```
106
278
 
107
- ## Architecture
279
+ If the Go module path has changed and the command fails, download the binary directly from the [mcp-publisher GitHub releases](https://github.com/modelcontextprotocol/registry/releases) page instead.
108
280
 
109
- ### Project Structure
281
+ On Windows, add Go's bin directory to your PATH if the command isn't recognized:
110
282
 
283
+ ```powershell
284
+ $env:PATH += ";$env:USERPROFILE\go\bin"
111
285
  ```
112
- β”œβ”€β”€ cmd/ # Application entry points
113
- β”‚ └── publisher/ # Server publishing tool
114
- β”œβ”€β”€ data/ # Seed data
115
- β”œβ”€β”€ deploy/ # Deployment configuration (Pulumi)
116
- β”œβ”€β”€ docs/ # Documentation
117
- β”œβ”€β”€ internal/ # Private application code
118
- β”‚ β”œβ”€β”€ api/ # HTTP handlers and routing
119
- β”‚ β”œβ”€β”€ auth/ # Authentication (GitHub OAuth, JWT, namespace blocking)
120
- β”‚ β”œβ”€β”€ config/ # Configuration management
121
- β”‚ β”œβ”€β”€ database/ # Data persistence (PostgreSQL)
122
- β”‚ β”œβ”€β”€ service/ # Business logic
123
- β”‚ β”œβ”€β”€ telemetry/ # Metrics and monitoring
124
- β”‚ └── validators/ # Input validation
125
- β”œβ”€β”€ pkg/ # Public packages
126
- β”‚ β”œβ”€β”€ api/ # API types and structures
127
- β”‚ β”‚ └── v0/ # Version 0 API types
128
- β”‚ └── model/ # Data models for server.json
129
- β”œβ”€β”€ scripts/ # Development and testing scripts
130
- β”œβ”€β”€ tests/ # Integration tests
131
- └── tools/ # CLI tools and utilities
132
- └── validate-*.sh # Schema validation tools
286
+
287
+ Verify:
288
+
289
+ ```bash
290
+ mcp-publisher --help
133
291
  ```
134
292
 
135
- ### Authentication
293
+ ##### 3. DNS Authentication (already done)
136
294
 
137
- Publishing supports multiple authentication methods:
138
- - **GitHub OAuth** - For publishing by logging into GitHub
139
- - **GitHub OIDC** - For publishing from GitHub Actions
140
- - **DNS verification** - For proving ownership of a domain and its subdomains
141
- - **HTTP verification** - For proving ownership of a domain
295
+ The `onesource.io` domain has a DNS TXT record that proves ownership of the `io.onesource` namespace. This is already configured β€” you don't need to redo it.
142
296
 
143
- The registry validates namespace ownership when publishing. E.g. to publish...:
144
- - `io.github.domdomegg/my-cool-mcp` you must login to GitHub as `domdomegg`, or be in a GitHub Action on domdomegg's repos
145
- - `me.adamjones/my-cool-mcp` you must prove ownership of `adamjones.me` via DNS or HTTP challenge
297
+ The record is on the root domain (`onesource.io`, not `_mcp-registry.onesource.io`):
146
298
 
147
- ## Community Projects
299
+ ```
300
+ v=MCPv1; k=ed25519; p=7D3U5rufgNXb/lH2MthTRZdDzEGeE7/Jvg8YkiArQc8=
301
+ ```
148
302
 
149
- Check out [community projects](docs/community-projects.md) to explore notable registry-related work created by the community.
303
+ You can verify it resolves:
150
304
 
151
- ## More documentation
305
+ ```bash
306
+ nslookup -type=TXT onesource.io 8.8.8.8
307
+ ```
152
308
 
153
- See the [documentation](./docs) for more details if your question has not been answered here!
309
+ ##### 4. Get the Private Key
310
+
311
+ Authentication requires the ed25519 private key in **hex format** that corresponds to the public key in the DNS record. Ask the team lead for this key β€” it's stored in the team's password manager / vault.
312
+
313
+ If you need to regenerate the keypair (this invalidates the current DNS record and requires updating it):
314
+
315
+ 1. Generate a new ed25519 keypair (e.g., `openssl genpkey -algorithm Ed25519 -out key.pem`)
316
+ 2. Extract the raw 32-byte private key seed and convert to hex:
317
+ ```bash
318
+ openssl pkey -in key.pem -outform DER | tail -c 32 | xxd -p -c 32
319
+ ```
320
+ 3. Extract the public key in base64 for the DNS TXT record:
321
+ ```bash
322
+ openssl pkey -in key.pem -pubout -outform DER | tail -c 32 | base64
323
+ ```
324
+ 4. Update the DNS TXT record on `onesource.io` with the new public key:
325
+ ```
326
+ v=MCPv1; k=ed25519; p=<base64-public-key>
327
+ ```
328
+ 5. Wait for DNS propagation before attempting to log in.
329
+
330
+ #### Publishing a New Version
331
+
332
+ Every time you release a new npm version, update the MCP Registry:
333
+
334
+ 1. **Publish to npm** (the registry validates the package exists, so this must happen first):
335
+ ```bash
336
+ npm run build
337
+ npm publish --access public
338
+ ```
339
+
340
+ 2. **Update `server.json`** β€” set both `version` fields to match the new npm version:
341
+ ```json
342
+ {
343
+ "version": "x.y.z",
344
+ ...
345
+ "packages": [{ "version": "x.y.z", ... }]
346
+ }
347
+ ```
348
+ The `mcpName` field in `package.json` must be `"io.onesource/mcp"` and must match the `name` field in `server.json`. This is already set β€” don't remove it.
349
+
350
+ 3. **Authenticate** (tokens expire, so do this each time):
351
+ ```bash
352
+ mcp-publisher login dns --domain onesource.io --private-key <ed25519-hex-private-key>
353
+ ```
354
+
355
+ 4. **Publish to the registry:**
356
+ ```bash
357
+ mcp-publisher publish
358
+ ```
359
+
360
+ 5. **Verify:**
361
+ ```bash
362
+ curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=onesource"
363
+ ```
364
+
365
+ ### Glama
366
+
367
+ Glama auto-syncs from the GitHub repo daily. No manual steps needed after a release β€” just make sure changes are pushed to `main`. The `glama.json` file in the repo root controls ownership. Manual re-sync is available from the [Glama admin panel](https://glama.ai/mcp/servers) after claiming the server.
368
+
369
+ ## License
370
+
371
+ Apache 2.0 β€” see [LICENSE](LICENSE) for details.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@one-source/mcp",
3
3
  "mcpName": "io.onesource/mcp",
4
- "version": "5.2.0",
4
+ "version": "5.2.1",
5
5
  "type": "module",
6
6
  "description": "Unified MCP server for OneSource β€” 28 tools for blockchain data",
7
7
  "bin": {
@@ -29,7 +29,7 @@
29
29
  },
30
30
  "dependencies": {
31
31
  "@modelcontextprotocol/sdk": "^1.27.1",
32
- "@one-source/api-mcp": "^5.2.0",
32
+ "@one-source/api-mcp": "^5.2.1",
33
33
  "@one-source/docs-mcp": "^4.0.3",
34
34
  "zod": "^3.24.0"
35
35
  },