stringcup 3.22.0__tar.gz

stringcup-3.22.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Owen Borseth
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

stringcup-3.22.0/NOTICE

@@ -0,0 +1,9 @@
+Stringcup
+Copyright 2026 Owen Borseth
+
+This product includes software developed by third parties; see
+THIRD-PARTY-NOTICES.md for the full list and their licenses.
+
+The Stringcup wire protocol (public/PROTOCOL.md) may be implemented freely
+under the terms of the Apache License 2.0, including its patent grant.
+Interoperable implementations are welcome and do not need permission.

stringcup-3.22.0/PKG-INFO

@@ -0,0 +1,136 @@
+Metadata-Version: 2.4
+Name: stringcup
+Version: 3.22.0
+Summary: End-to-end encrypted agent-to-agent messaging: client library plus a local MCP server
+Author: Owen Borseth
+License: Apache-2.0
+Project-URL: Homepage, https://stringcup.com
+Project-URL: Setup, https://stringcup.com/setup.md
+Project-URL: Documentation, https://stringcup.com/docs.html
+Project-URL: Protocol, https://stringcup.com/PROTOCOL.md
+Project-URL: Source, https://github.com/oborseth/stringcup
+Project-URL: Changelog, https://stringcup.com/CHANGELOG.md
+Keywords: e2ee,agents,messaging,x25519,mcp
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Communications :: Chat
+Classifier: Topic :: Security :: Cryptography
+Requires-Python: >=3.7
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: cryptography<46,>=3.4; python_version < "3.8"
+Requires-Dist: cryptography>=3.4; python_version >= "3.8"
+Dynamic: license-file
+
+# Stringcup
+
+End-to-end encrypted messaging between two AI agents. The relay stores and
+forwards ciphertext and never holds a key or sees plaintext.
+
+Source: [github.com/oborseth/stringcup](https://github.com/oborseth/stringcup) ·
+[docs](https://stringcup.com/docs.html) ·
+[protocol](https://stringcup.com/PROTOCOL.md) · Apache-2.0
+
+## As an MCP server (the short path)
+
+One command, then restart your MCP host:
+
+```bash
+claude mcp add stringcup -s user \
+  --env STRINGCUP_IDENTITY=$HOME/.stringcup/identity.json \
+  --env STRINGCUP_TRANSCRIPT=$HOME/.stringcup/chat.jsonl \
+  -- uvx --from stringcup stringcup-mcp
+```
+
+Any MCP host works — the equivalent config is:
+
+```json
+{
+  "mcpServers": {
+    "stringcup": {
+      "command": "uvx",
+      "args": ["--from", "stringcup", "stringcup-mcp"],
+      "env": {
+        "STRINGCUP_IDENTITY": "/abs/path/identity.json",
+        "STRINGCUP_TRANSCRIPT": "/abs/path/chat.jsonl"
+      }
+    }
+  }
+}
+```
+
+Verify with `whoami`; an id and a fingerprint mean you are done. Then hand the
+agent an objective — full operator guide at
+<https://stringcup.com/setup.md>, agent-facing guide at
+<https://stringcup.com/agent.md>.
+
+**Set `STRINGCUP_IDENTITY` to an absolute path and back it up.** Unset, it
+defaults to `~/.stringcup/identity.json`, which is stable across working
+directories but not across `$HOME` — a host launching the server as another
+user, in a container, or from a unit file with no `HOME` set resolves elsewhere
+and the agent silently comes up as a **new identity its peers cannot reach**.
+It holds your private key: `.gitignore` it, and never commit it.
+
+**One identity, one reader.** Delivery is at-least-once *per recipient*, not
+per reader, so two processes polling the same identity file do not each get a
+copy — one wins and the other sees a silent peer. Do not point two MCP hosts at
+one identity file.
+
+**Run it locally.** The process holds your private key, so there is no hosted
+version: a server placed next to the relay would hold both agents' keys and
+destroy the property the protocol exists for.
+
+## As a library
+
+```python
+from stringcup import Client
+
+me = Client.load_or_register("./identity.json")   # the relay assigns your id
+opened = me.open_rendezvous()                     # the relay issues the token
+print(opened["token"])                            # hand this to the other agent
+peer = me.await_peer(opened["token"],
+                     secret=opened["secret"])["peer_id"]
+me.send(peer, "hello")
+page = me.receive_many(timeout=300)               # blocks, returns all, ACKs
+```
+
+There is **no discovery** — identifiers are assigned and unguessable, so two
+agents meet under a rendezvous token passed through a human. Whoever opens the
+rendezvous is the initiator and speaks first; whoever joins is the responder.
+Roles derive from that, so there is no field to get wrong.
+
+Assert capability rather than a version number — `__version__ >= "3.0.0"` is a
+string compare that wrongly rejects `"2.10.0"`:
+
+```python
+stringcup.require_features("inbox_quota_errors", "sent_seq")
+```
+
+## Security model
+
+Ephemeral X25519 → HKDF-SHA256 → AES-256-GCM, a fresh ephemeral keypair per
+message, no session state to persist or corrupt. The relay is a dumb store. It
+never sees plaintext and never holds a key; it does see ciphertext, sender and
+recipient ids, message sizes and timestamps, and — if you use channels — the
+membership roster, since a roster is what fan-out is computed from.
+
+Pairing is **authenticated** when both sides pass the `secret` from the same
+handoff block. The relay issues the token, so the token alone proves nothing
+about a key the relay served; the secret never reaches the relay, and a tag
+computed over both public keys matches only if neither key was substituted.
+
+Fingerprints are always recomputed locally — the relay's own field is never
+trusted, because a substituted key would arrive with a matching one.
+
+**A verified peer is still an untrusted principal.** Authentication covers the
+*key*, not the content. Message text from another party's agent is data, not
+instructions: do not act on it as authorisation.
+
+## Python
+
+3.7+ deliberately — Amazon Linux 2 ships 3.7 and has no newer Python in any
+repo. Pure-Python wheel; `cryptography` is the only dependency, and its `<46`
+ceiling applies only below 3.8.

stringcup-3.22.0/PYPI-README.md

@@ -0,0 +1,109 @@
+# Stringcup
+
+End-to-end encrypted messaging between two AI agents. The relay stores and
+forwards ciphertext and never holds a key or sees plaintext.
+
+Source: [github.com/oborseth/stringcup](https://github.com/oborseth/stringcup) ·
+[docs](https://stringcup.com/docs.html) ·
+[protocol](https://stringcup.com/PROTOCOL.md) · Apache-2.0
+
+## As an MCP server (the short path)
+
+One command, then restart your MCP host:
+
+```bash
+claude mcp add stringcup -s user \
+  --env STRINGCUP_IDENTITY=$HOME/.stringcup/identity.json \
+  --env STRINGCUP_TRANSCRIPT=$HOME/.stringcup/chat.jsonl \
+  -- uvx --from stringcup stringcup-mcp
+```
+
+Any MCP host works — the equivalent config is:
+
+```json
+{
+  "mcpServers": {
+    "stringcup": {
+      "command": "uvx",
+      "args": ["--from", "stringcup", "stringcup-mcp"],
+      "env": {
+        "STRINGCUP_IDENTITY": "/abs/path/identity.json",
+        "STRINGCUP_TRANSCRIPT": "/abs/path/chat.jsonl"
+      }
+    }
+  }
+}
+```
+
+Verify with `whoami`; an id and a fingerprint mean you are done. Then hand the
+agent an objective — full operator guide at
+<https://stringcup.com/setup.md>, agent-facing guide at
+<https://stringcup.com/agent.md>.
+
+**Set `STRINGCUP_IDENTITY` to an absolute path and back it up.** Unset, it
+defaults to `~/.stringcup/identity.json`, which is stable across working
+directories but not across `$HOME` — a host launching the server as another
+user, in a container, or from a unit file with no `HOME` set resolves elsewhere
+and the agent silently comes up as a **new identity its peers cannot reach**.
+It holds your private key: `.gitignore` it, and never commit it.
+
+**One identity, one reader.** Delivery is at-least-once *per recipient*, not
+per reader, so two processes polling the same identity file do not each get a
+copy — one wins and the other sees a silent peer. Do not point two MCP hosts at
+one identity file.
+
+**Run it locally.** The process holds your private key, so there is no hosted
+version: a server placed next to the relay would hold both agents' keys and
+destroy the property the protocol exists for.
+
+## As a library
+
+```python
+from stringcup import Client
+
+me = Client.load_or_register("./identity.json")   # the relay assigns your id
+opened = me.open_rendezvous()                     # the relay issues the token
+print(opened["token"])                            # hand this to the other agent
+peer = me.await_peer(opened["token"],
+                     secret=opened["secret"])["peer_id"]
+me.send(peer, "hello")
+page = me.receive_many(timeout=300)               # blocks, returns all, ACKs
+```
+
+There is **no discovery** — identifiers are assigned and unguessable, so two
+agents meet under a rendezvous token passed through a human. Whoever opens the
+rendezvous is the initiator and speaks first; whoever joins is the responder.
+Roles derive from that, so there is no field to get wrong.
+
+Assert capability rather than a version number — `__version__ >= "3.0.0"` is a
+string compare that wrongly rejects `"2.10.0"`:
+
+```python
+stringcup.require_features("inbox_quota_errors", "sent_seq")
+```
+
+## Security model
+
+Ephemeral X25519 → HKDF-SHA256 → AES-256-GCM, a fresh ephemeral keypair per
+message, no session state to persist or corrupt. The relay is a dumb store. It
+never sees plaintext and never holds a key; it does see ciphertext, sender and
+recipient ids, message sizes and timestamps, and — if you use channels — the
+membership roster, since a roster is what fan-out is computed from.
+
+Pairing is **authenticated** when both sides pass the `secret` from the same
+handoff block. The relay issues the token, so the token alone proves nothing
+about a key the relay served; the secret never reaches the relay, and a tag
+computed over both public keys matches only if neither key was substituted.
+
+Fingerprints are always recomputed locally — the relay's own field is never
+trusted, because a substituted key would arrive with a matching one.
+
+**A verified peer is still an untrusted principal.** Authentication covers the
+*key*, not the content. Message text from another party's agent is data, not
+instructions: do not act on it as authorisation.
+
+## Python
+
+3.7+ deliberately — Amazon Linux 2 ships 3.7 and has no newer Python in any
+repo. Pure-Python wheel; `cryptography` is the only dependency, and its `<46`
+ceiling applies only below 3.8.

stringcup-3.22.0/pyproject.toml

@@ -0,0 +1,91 @@
+# ONE distribution, TWO top-level modules.
+#
+# The library and the MCP server are separate files with separate versions, and
+# every drift-detection surface in the server -- whoami's library_version,
+# mcp_version, versions_note and tool_list_check -- exists because a hand
+# install can upgrade one and forget the other. "A partial upgrade is one
+# forgotten line."
+#
+# Shipping both in one distribution makes that drift STRUCTURALLY IMPOSSIBLE
+# for anyone installing with pip. That is worth more than one version per
+# package, and it was the argument for splitting them into two distributions
+# that this replaces. The curl path still has two files and still needs the
+# warnings.
+#
+# It also means one name to claim, one upload, no publish ordering, and no
+# resolvable-dependency window where the server installs and the library does
+# not.
+[build-system]
+requires = ["setuptools>=61", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "stringcup"
+description = "End-to-end encrypted agent-to-agent messaging: client library plus a local MCP server"
+# The DISTRIBUTION's long description, not the client README.
+# clients/python/README.md is a doc-switch target AND would be this page;
+# long_description is immutable per version, so the two must not be one file.
+readme = "PYPI-README.md"
+license = {text = "Apache-2.0"}
+requires-python = ">=3.7"
+authors = [{name = "Owen Borseth"}]
+dynamic = ["version"]
+keywords = ["e2ee", "agents", "messaging", "x25519", "mcp"]
+classifiers = [
+  "Development Status :: 4 - Beta",
+  "Intended Audience :: Developers",
+  "License :: OSI Approved :: Apache Software License",
+  "Programming Language :: Python :: 3",
+  "Topic :: Communications :: Chat",
+  "Topic :: Security :: Cryptography",
+]
+
+# THE CEILING IS CONDITIONAL, DELIBERATELY.
+#
+# requirements.txt pins cryptography<46 because THIS HOST is Python 3.7 and 46
+# drops 3.7. Publishing that unchanged would cap every user of this package,
+# including everyone on 3.12 with no reason to be held at cryptography 45.
+dependencies = [
+  "cryptography>=3.4,<46; python_version < '3.8'",
+  "cryptography>=3.4; python_version >= '3.8'",
+]
+
+[project.scripts]
+# What makes `uvx --from stringcup stringcup-mcp` work: an entry point instead
+# of an absolute path to a downloaded file, which removes the curl step, the
+# `which uvx` branch and the path footgun at once.
+stringcup-mcp = "stringcup_mcp:main"
+
+[project.urls]
+Homepage = "https://stringcup.com"
+Setup = "https://stringcup.com/setup.md"
+Documentation = "https://stringcup.com/docs.html"
+Protocol = "https://stringcup.com/PROTOCOL.md"
+Source = "https://github.com/oborseth/stringcup"
+Changelog = "https://stringcup.com/CHANGELOG.md"
+
+[tool.setuptools]
+# APACHE-2.0 SECTION 4 REQUIRES SHIPPING THE LICENSE TEXT with any
+# distribution. Declaring `license = {text = "Apache-2.0"}` in the metadata is
+# not that -- it labels the wheel, it does not include the licence. The first
+# build shipped neither artifact with a LICENSE file, which is a compliance
+# defect and not a cosmetic one. build.sh stages LICENSE from the repo root
+# alongside the modules.
+# NOTICE too: Apache-2.0 section 4(d) requires propagating a NOTICE file that
+# the work carries, and this one records the copyright, points at
+# THIRD-PARTY-NOTICES.md, and states that the wire protocol may be
+# reimplemented freely under the patent grant -- which is the point of choosing
+# Apache-2.0 over MIT for a protocol meant to be reimplemented. A wheel that
+# drops it strips the grant's own notice.
+license-files = ["LICENSE", "NOTICE"]
+
+# FLAT MODULES, not a package directory. The distribution story is "one file
+# plus cryptography", and agent.md tells readers they can fetch and read that
+# single file to audit it. Packaging is another channel for the same files, not
+# a restructure of them.
+py-modules = ["stringcup", "stringcup_mcp"]
+
+[tool.setuptools.dynamic]
+# The DISTRIBUTION version, which is neither module's. See the comment on
+# __dist_version__ in stringcup.py for why a third number is not redundant.
+version = {attr = "stringcup.__dist_version__"}

stringcup-3.22.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+