Skip to content

docs(security): clarify stdio-only claim now that HTTP transport exists#1714

Open
Thizeidler wants to merge 1 commit into
Graphify-Labs:v8from
Thizeidler:fix/security-doc-http-transport
Open

docs(security): clarify stdio-only claim now that HTTP transport exists#1714
Thizeidler wants to merge 1 commit into
Graphify-Labs:v8from
Thizeidler:fix/security-doc-http-transport

Conversation

@Thizeidler

Copy link
Copy Markdown

Summary

  • SECURITY.md states graphify "does not run a network listener" and that the MCP server "communicates over stdio only".
  • README.md documents an opt-in --transport http mode (python -m graphify.serve ... --transport http --host 0.0.0.0 --api-key ...) for sharing one graphify server across a team, which does open a real network listener.
  • This updates the claim to describe the actual default (stdio, no listener) plus the documented opt-in HTTP exception, so the security doc stays accurate.

Test plan

  • Docs-only change (single bullet in SECURITY.md); no code paths affected.
  • Confirmed the referenced HTTP transport flags (--transport, --host, --api-key) exist in README.md (lines ~443-476).

SECURITY.md said graphify never runs a network listener and only
communicates over stdio. README.md documents an opt-in --transport http
mode (with --host/--api-key flags) for sharing one server across a team,
which does open a network listener. Update the claim to describe the
default (stdio, no listener) and the documented opt-in exception.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant