mcpeye 0.1.1 → 0.1.2
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.
- checksums.yaml +4 -4
- data/README.md +2 -3
- data/lib/mcpeye/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: a764f79cce8846c6a9bcf750e778de9f88c082518eac5c6c4d271c15743456a4
|
|
4
|
+
data.tar.gz: c1621b94ab8dc5689cd4b335d1bb4fd79b854c430ea83754c81feb138b510150
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 5b0c8dd68029607b4126f3f0f9423e560b3a278919edd449498cd7bf3cb11f9edbd14da33b705579a6c719e89d6167c4ac92c47a1f660505c30e1ae27c7e5339
|
|
7
|
+
data.tar.gz: e88ec3f95170142f0e5fed4aeff5a2e6ad8c1821c818b257c01e0066dedb03e06b0522ebf235ad3379800aeaee010e9f179d3ffc294d9e33c6dd43fb5f35deb9
|
data/README.md
CHANGED
|
@@ -8,8 +8,7 @@ agents try to do through your MCP tools — and, crucially, the asks your tools
|
|
|
8
8
|
instance. There the worker clusters sessions into the **Intent Gap Report**: the
|
|
9
9
|
top user asks your tools attempted but failed to deliver.
|
|
10
10
|
|
|
11
|
-
This gem
|
|
12
|
-
and for any Ruby shop running one. It is **pure stdlib at runtime** (`net/http`,
|
|
11
|
+
This gem instruments any Ruby / Rails MCP server. It is **pure stdlib at runtime** (`net/http`,
|
|
13
12
|
`json`, `securerandom`) and **never raises into, or alters, the host server**.
|
|
14
13
|
Capture is O(1); set `flush_interval:` to ship telemetry off the tool-call thread
|
|
15
14
|
(see [Options](#options) for the zero-thread default's one caveat).
|
|
@@ -134,7 +133,7 @@ Identity values (`userId`/`client`/`serverVersion`) are coerced to strings befor
|
|
|
134
133
|
they're sent (the ingest contract requires strings), so an integer id is fine —
|
|
135
134
|
but pass an **opaque, non-PII** value.
|
|
136
135
|
|
|
137
|
-
##
|
|
136
|
+
## Use in a Rails MCP server
|
|
138
137
|
|
|
139
138
|
`config/initializers/mcpeye.rb`:
|
|
140
139
|
|
data/lib/mcpeye/version.rb
CHANGED