mcp-test-harness-bedrock
AWS Bedrock agents testing helpers for MCP Test Harness.
Author: Vaquar Khan -- https://github.com/vaquarkhan
Install
pip install mcp-test-harness-bedrock
This automatically installs mcp-test-harness as a dependency.
Usage
from mcp_test_harness_bedrock import assert_bedrock_tool, mcp_tools_to_bedrock_tool_specs, create_bedrock_test_config
async def test_tool(mcp_server):
await assert_bedrock_tool(mcp_server, "my_tool", {}, expected_text="ok")
def test_schema_bridge(mcp_tools):
# mcp_tools from list_tools — convert for AWS Bedrock SDKs
return mcp_tools_to_bedrock_tool_specs(mcp_tools)
cfg = create_bedrock_test_config("python server.py", timeout=45)
Helpers
- Tool call assertion with optional text check
- MCP tool → AWS Bedrock schema converter
mcp-test.yaml-shaped config builder
License
MIT. See LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for mcp-test-harness-bedrock 5.3.1
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 | Actions |
|---|---|---|---|---|
| mcp_test_harness_bedrock-5.3.1.tar.gz | 3.5 kB | With provenance | Details for mcp_test_harness_bedrock-5.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_test_harness_bedrock-5.3.1-py3-none-any.whl | Python 3 | none | any | Details for mcp_test_harness_bedrock-5.3.1-py3-none-any.whl |
Total release size: 8.2 kB
Release files / mcp_test_harness_bedrock-5.3.1.tar.gz
| Download URL | mcp_test_harness_bedrock-5.3.1.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a1d8fe65927451de1c1756980c053474252a09e8745ddd4f7e1de4a2d43c8eb
|
|
BLAKE2b-256 checksum How to use checksums |
8fb0d3e7b557a69cdcbe47af664f0d0faf587f92f0acd100fa3588297034afc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logRelease files / mcp_test_harness_bedrock-5.3.1-py3-none-any.whl
| Download URL | mcp_test_harness_bedrock-5.3.1-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
524a5a380a9769af5d3ba3e937567d2cd2731d6894b1f3e639545c43208fd8f9
|
|
BLAKE2b-256 checksum How to use checksums |
50355c52e9ac0a1c8e03f42ca2a0b15cf04df21db7cf828e53f8947554e26dc0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logSecurity for mcp-test-harness-bedrock 5.3.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mcp_test_harness_bedrock-5.3.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logA 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.
