@sharpe-terminal/mcp-server 1.6.0 → 1.6.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.
@@ -1 +1 @@
1
- {"version":3,"file":"manifest.js","sourceRoot":"","sources":["../../src/contracts/manifest.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAsCH,sGAAsG;AACtG,MAAM,CAAC,MAAM,QAAQ,GAAkB,IAAI,CAAC,KAAK,CAAC,o56YAAo56Y,CAAkB,CAAC"}
1
+ {"version":3,"file":"manifest.js","sourceRoot":"","sources":["../../src/contracts/manifest.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAsCH,sGAAsG;AACtG,MAAM,CAAC,MAAM,QAAQ,GAAkB,IAAI,CAAC,KAAK,CAAC,ymxdAAymxd,CAAkB,CAAC"}
@@ -2,7 +2,7 @@
2
2
  * The endpoint tools, built from the agent manifest (WP-U12, design L6-D1 §3.1): one tool per contract with an agent
3
3
  * block, named, described, validated and routed by src/contracts through the synced manifest
4
4
  * (./contracts/manifest.ts, scripts/contracts/sync-packages.ts). Nothing here names an endpoint's path or re-types a
5
- * parameter; the Python server (packages/mcp-server-python/server.py) implements the same steps over the same
5
+ * parameter; the Python server (packages/mcp-server-python/sharpe_mcp/server.py) implements the same steps over the same
6
6
  * document, and scripts/contracts/parity.ts proves the two answer alike.
7
7
  *
8
8
  * A call: check the arguments against the tool's input schema, fill its defaults, pick the route (v1 with a key, the
@@ -2,7 +2,7 @@
2
2
  * The endpoint tools, built from the agent manifest (WP-U12, design L6-D1 §3.1): one tool per contract with an agent
3
3
  * block, named, described, validated and routed by src/contracts through the synced manifest
4
4
  * (./contracts/manifest.ts, scripts/contracts/sync-packages.ts). Nothing here names an endpoint's path or re-types a
5
- * parameter; the Python server (packages/mcp-server-python/server.py) implements the same steps over the same
5
+ * parameter; the Python server (packages/mcp-server-python/sharpe_mcp/server.py) implements the same steps over the same
6
6
  * document, and scripts/contracts/parity.ts proves the two answer alike.
7
7
  *
8
8
  * A call: check the arguments against the tool's input schema, fill its defaults, pick the route (v1 with a key, the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sharpe-terminal/mcp-server",
3
- "version": "1.6.0",
3
+ "version": "1.6.1",
4
4
  "description": "MCP server for Sharpe crypto derivatives and market data API",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -39,5 +39,10 @@
39
39
  "futures",
40
40
  "sharpe"
41
41
  ],
42
- "license": "MIT"
42
+ "license": "MIT",
43
+ "repository": {
44
+ "type": "git",
45
+ "url": "git+https://github.com/rishabhng/sharpe-terminal-v2.git",
46
+ "directory": "packages/mcp-server"
47
+ }
43
48
  }