This project has been archived by its maintainers, and is no longer receiving any updates.
mcp-relay-core
Zero-config credential relay client for Python MCP servers -- ECDH P-256 + AES-256-GCM E2E encryption.
Installation
pip install mcp-relay-core
Usage
Resolve config (env vars -> config file -> defaults -> relay)
from mcp_relay_core import resolve_config
result = resolve_config("my-server", ["api_key", "endpoint"])
if result.config:
print(f"Config loaded from {result.source}: {result.config}")
else:
# No config found -- trigger relay setup
pass
Relay session (interactive credential setup)
import asyncio
from mcp_relay_core import create_session, poll_for_result, write_config
async def setup():
session = await create_session(
"https://relay.example.com",
"my-server",
{
"fields": [
{"name": "api_key", "label": "API Key", "type": "password"},
{"name": "endpoint", "label": "Endpoint", "type": "text"},
]
},
)
print(f"Open this URL to enter credentials: {session.relay_url}")
credentials = await poll_for_result("https://relay.example.com", session)
write_config("my-server", credentials)
asyncio.run(setup())
Crypto primitives
from mcp_relay_core import (
generate_key_pair,
export_public_key,
derive_shared_secret,
derive_aes_key,
encrypt,
decrypt,
)
Documentation
See the main repository for full documentation, architecture, and security properties.
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for mcp-relay-core 1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_relay_core-1.4.0.tar.gz | 67.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_relay_core-1.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 112.2 kB
Release files / mcp_relay_core-1.4.0.tar.gz
| Download URL | mcp_relay_core-1.4.0.tar.gz |
|---|---|
| Size | 67.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cef2bad3ffff862620d6c896a6639760ffbad92ebb9345b45057e3706fb1aedb
|
|
BLAKE2b-256 checksum How to use checksums |
55e752c2c559e6edd9f73b0af715c2f3bc2c8dd0cef53c1f31af462be4254340
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.3 {"installer":{"name":"uv","version":"0.11.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / mcp_relay_core-1.4.0-py3-none-any.whl
| Download URL | mcp_relay_core-1.4.0-py3-none-any.whl |
|---|---|
| Size | 45.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed6ae8f610ee5dff48e67f42548403846f0119211687254fb8e54f638945f37d
|
|
BLAKE2b-256 checksum How to use checksums |
89bef8b284742c25b900d50aa317b055569a72fdb6402df1d5c209c29b673942
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.3 {"installer":{"name":"uv","version":"0.11.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for mcp-relay-core 1.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
