Server data from the Official MCP Registry
Learn and adopt the Capability Host Protocol — the agentic web's open evidence layer.
Learn and adopt the Capability Host Protocol — the agentic web's open evidence layer.
Remote endpoints: streamable-http: https://capabilityhostprotocol.com/api/mcp
This is a capability host protocol implementation with several moderate security concerns. The code makes subprocess calls without adequate input sanitization in key areas, stores API keys in environment variables and keychain with limited validation, and includes network calls that could expose credentials. The mesh management features involve credential handling that could be improved. While the code quality is generally reasonable and the protocol itself is well-intentioned, these issues warrant attention before production use. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 1 high severity).
4 files analyzed · 14 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
CHP is an open protocol for making agent, tool, and system execution visible, replayable, and ready for governance.
The first launch goal is simple:
See what your agents and tools actually did.
CHP is not another agent framework, tool protocol, or workflow engine. It is an execution evidence layer at the capability boundary.
Install the Python reference host from this checkout:
python -m pip install -e packages/python
Run the agent/tool observability demo:
python examples/agent-operations-demo/demo.py
Run a served capability host endpoint demo:
chp demo endpoint
Run conformance:
python conformance/runner.py
Record development work as CHP evidence:
chp work run \
--intent "Verify CHP tests." \
--correlation-id chp-dev-001 \
--test-run unit \
-- python -m unittest discover -s packages/python/tests
chp work summary chp-dev-001
Validate the served-host demo as evidence:
chp work validate-demo endpoint --correlation-id chp-demo-validation
chp work replay chp-demo-validation
Check v0.1 protocol alignment:
chp work check-alignment --correlation-id chp-alignment
Check launch messaging:
chp work check-messaging --correlation-id chp-messaging
from chp_core import LocalCapabilityHost, capability
host = LocalCapabilityHost("example-host")
@capability(
id="math.add",
version="1.0.0",
description="Add two numbers.",
)
def add(a: int, b: int):
return {"sum": a + b}
host.register(add)
result = host.invoke(
"math.add",
{"a": 2, "b": 3},
correlation_id="demo-correlation",
)
events = host.replay("demo-correlation")
The host emits execution_started and execution_completed evidence for the invocation. If execution fails, it emits execution_failed. If the host denies invocation, it emits execution_denied.
spec/chp-v0.1.md: minimal CHP v0.1 specificationschemas/: JSON Schemas for protocol objectspackages/python/chp_core/: reference local hostexamples/capability-host-endpoint-demo/: HTTP-served host demoexamples/agent-operations-demo/: agent/tool observability demoexamples/codex-self-observation-demo/: Codex dogfooding demoexamples/mcp-bridge-demo/: experimental MCP-style bridge prototypeconformance/: conformance runnerdocs/comparisons/chp-vs-mcp.md: precise MCP comparisondocs/comparisons/chp-and-opentelemetry.md: OpenTelemetry alignment notedocs/comparisons/landscape.md: adjacent framework comparisondocs/design/codex-self-observation.md: Codex dogfooding patterndocs/design/public-v0.1-internal-legacy-boundary.md: public/internal boundarydocs/design/evidence-integrity-v0.2.md: future evidence integrity proposaldocs/security/threat-model-v0.1.md: v0.1 threat modeldocs/release-checklist-v0.1.md: release-readiness checklistdocs/packaging-v0.1.md: packaging and versioning planMCP exposes tools and context to AI applications. CHP governs and evidences execution of capabilities.
They fit together. MCP can be a source of capability invocation, and CHP can add correlation, replay, evidence, denial semantics, and future governance at the execution boundary.
Read more: docs/comparisons/chp-vs-mcp.md.
Open source should include local visibility:
Commercial value can remain around production trust:
Guiding rule:
Local visibility should be free. Production trust should be paid.
MIT. See LICENSE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.