@tryvira/mcp 0.1.26 → 0.1.27
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/README.md +7 -5
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# @tryvira/mcp
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
|
|
3
|
+
An MCP server for connecting MCP-compatible applications to Vira's governed AI
|
|
4
|
+
behavior and runtime APIs. The package is MIT licensed.
|
|
5
5
|
|
|
6
6
|
An npx-ready MCP server for Vira's existing scoped authority boundary.
|
|
7
7
|
|
|
@@ -40,7 +40,8 @@ execution requires the explicit `VIRA_MCP_ALLOW_EFFECTFUL=true` opt-in; producti
|
|
|
40
40
|
accepts that shortcut. Set `VIRA_MCP_BIND_PUBLIC=true` only when an authenticated reverse
|
|
41
41
|
proxy or equivalent network boundary is present.
|
|
42
42
|
|
|
43
|
-
|
|
43
|
+
Tools that change state or execute behavior are checked by Vira for credentials, scope,
|
|
44
|
+
policy, evaluation, and release eligibility. The server does not bypass those checks.
|
|
44
45
|
|
|
45
46
|
## What a client can discover
|
|
46
47
|
|
|
@@ -75,5 +76,6 @@ Never paste real credentials into a checked-in client configuration. For local-o
|
|
|
75
76
|
testing, use the local stack and its documented development credentials; the production
|
|
76
77
|
authority path does not accept the local bypass.
|
|
77
78
|
|
|
78
|
-
See [
|
|
79
|
-
|
|
79
|
+
See the [MCP guide](https://github.com/hrpering/tryvira/blob/main/docs/reference/mcp.md)
|
|
80
|
+
and [tool catalog](https://github.com/hrpering/tryvira/blob/main/docs/reference/mcp-tools.md)
|
|
81
|
+
for discovery, examples, and error behavior.
|